Thomas Maurer

Cloud and Datacenter Blog focusing on Microsoft Azure

Subscribe
, , , ,

SCVMM 2012 SP1 Error: Windows network virtualization is not enabled on a host NIC available for placement

Thomas Maurer
1–2 minutes
3 comments on SCVMM 2012 SP1 Error: Windows network virtualization is not enabled on a host NIC available for placement

System Center Logo

If you are running Windows Server 2012 Hyper-V hosts and you are managing them with System Center Virtual Machine Manager 2012 SP1 and you are running VM Networks with Network Virtualization you can get the following error when you try to deploy a new Virtual Machine to the Hyper-V host.

“Windows network virtualization is not enabled on a host NIC available for placement”

Windows network virtualization is not enabled on a host NIC available for placement

This happens if:

  • You create a Logical Network with Network Virtualization enabled
  • You add the Logical Network to a Host Adapter or a Logical Switch on the Hyper-V host
  • You create a Isolated VM Network
  • Deploy a new Virtual Machine with the VM Network.

Resolution:

  • Enable the Windows Network Virtualization Filter driver on the Hyper-V host
Windows Network Virtualization Filter driver
Windows Network Virtualization Filter driver

If you are running this on a Team you have to enable the Windows Network Virtualization Filter driver on the Network Adapter Team.

Tags, , , , , , , , , , , , , , ,
Thomas Maurer
Thomas is the EMEA Global Black Belt (GBB) for Sovereign Cloud at Microsoft, helping organizations across the region harness Microsoft’s sovereign, hybrid, multicloud, and edge solutions. He works directly with C-level leaders and technical teams to remove roadblocks, accelerate digital transformation, and shape long-term cloud strategies that meet business and regulatory needs. With over 15 years of experience in cloud and datacenter, including his previous role as Principal Program Manager and Chief Evangelist for Azure Hybrid, he combines deep technical expertise with a passion for customer success. He specializes in creating scalable architectures, solution accelerators, and thought leadership that drive adoption and innovation on Azure. Thomas is a passionate community advocate and frequently speaks at industry events such as Microsoft Ignite and Microsoft TechDays. He shares his expertise through his Cloud and Datacenter Blog at www.thomasmaurer.ch and on LinkedIn and X.com www.twitter.com/thomasmaurer.

Related articles

3 responses

  1. Gill Avatar
    Gill

    Easy to do through the GUI, now how to enable this setting on a server core machine?

    Reply
  2. Morne Avatar
    Morne

    Hi

    I’m currently testing 2012. I’ve created a Windows based team (2 Physical-NICs) and created a Virtual Switch on the Team. (Can only create one per interface)

    Then I’ve created vEthernet Cards on top of the Virtual Switch, each with their own weight and VLAN assigned (Done everything via PowerShell).

    Everything works perfectly, except when the Dynamic IP address leasing from VMM 2012 SP1 comes into the picture. I cannot get VMM to lease an IP address to the Windows machine with this type of configuration.

    Can it be that I need more than one Virtual Switch in order to get this working?

    Any help would be appreciated.

    Thanks.

    Reply
  3. JD Avatar
    JD

    @ Gill

    $sw = Get-VMSwitch –Name […]

    or

    $sw = Get-VMSwitch -SwitchType External

    Then

    Enable-NetAdapterBinding -InterfaceDescription $sw.NetAdapterInterfaceDescription -ComponentID “ms_netwnv”

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.