When provisioning a new Hyper-V hosting into SCVMM I have a situation occur that causes loss of management to the server, which really should not be happening. When I add a new host, I set the 'Virtual Switch' adding a new 'Logical Switch' as well as a 'Virtual Network Adapter' for the management OS traffic.
The first NIC in the team is active and configured with correct static IP information, which is allowing VMM access to the server to perform these steps. The 'Virtual Network Adapter' has a checkbox in the 'This virtual network adapter inherits settings from the physical management adapter.' option box.
From my understanding what should happen is when the virtual adapter is created on the host the IP information should move to the virtual adapter from the physical adapter that is now part of the NIC Team. What is actually happening is the NIC Team seems to create OK, but it picks up a DHCP IP address instead of assuming the first physical NIC's IP information. I tried this with only one NIC as well as both NICs in the team to see what happens. Either case the same problem presents.
To get around this, what I did was sit on the console after I started the provisioning process. As soon as I saw Teamed NIC create I applied the static IP address via PowerShell manually to that Teamed NIC virtual adapter and then VMM just continued along normally. It then moving the IP from the NIC Team adapter to the Hyper-V virtual adapter properly. I did get a warning back from the creation (below) which hints me to the problem.
The Error code details as 2147942465 which is a "Network Access Denied" code followed by "Error while applying physical adapter network settings to teamed adapter". So, this is telling me there was a permission issue of some sort during the step of adding the original physical NIC IP settings to the virtual NIC.
The VMM Run As user 'HVAdmin' is a Local Administrator on the Hyper-V host, this has been verified. It has also been temporarily granted Administrator access on the domain to see if it helps. No go.
Searching around the net has now revealed this problem so far, has anyone else seen this? It makes provisioning a bit of a chore because I have to be at the Hyper-V console and on VMM at the exact same time to add a new host.