Fixing Network Compliance in VMM

Share this:

Using VMM 2012 R2 to validate the Network Compliance status, and fix eventual Non compliant when the physical adapter is no longer in use.


Using Network Virtualization in Hyper-V helps the administrator in several areas, one of the most important is the operational costs of supporting the environment. However, when some issues arises due a change on the network components directly on the server (out of band)  or anything that it was not defined in the VMM, then a Non compliant may show up on the console.

First of all, to check your hosts, click on Fabric, then Logical Networks, and finally click on Hosts icon on the top bar. A list of all physical adapters, virtual switches and Virtual Nics will be listed, and the Network Compliance status of each one of them.


In this scenario, we have  a Hyper-V cluster where we use only two physical adapters (although the host has several physical adapters) and on top of those two, several vNIC cards were created to support the workloads (Management, Cluster, Live, iSCSI, production network and so forth). During the initial analys we noticed that some physical adapters are showing as Non Compliant and some of them as Fully Compliant. We can get a hint of the issue by selecting one adapter and the Compliance errors section will provide some basic information.


In this scenario, the problem was that the physical adapters were not connectedc to the network, so the best solution is to right-click on the affected adapters, and then click on Properties.


In the example below, the adapter #39 has a Failed status and it is not connected on the network, the solution is to uncheck the option Available for placement, repeat the same step for any physical adapter that is not being in used in the infrastructure.


After making the changes, the same adapter #39 shows up as Fully compliant, as show in the image below.



In this Tutorial we worked on fixing unused physical adapter to be Fully Compliant in Virtual Machine Manager. It is always good to keep the environment without errors and clean as possible, and following the steps provide here you will clean up the environment.

Written by Anderson Patricio

Anderson Patricio is a Canadian Exchange Server MVP and MCSM (Solutions Master) and he contributes to the Microsoft Community with articles, tutorials, blog posts, forums and book reviews. He is a regular contributor at, and (Portuguese).