You add a Windows Server 2008 R2 server with the Hyper-V role installed to an existing
Hyper-V failover cluster. After you move a virtual machine (VM) to the new cluster node,
Microsoft System Center Virtual Machine Manager (VMM) 2008 R2 reports the status of the
VM as Unsupported Cluster Configuration. You need to be able to manage the VM by using
VMM. What should you do?

A.
Disable TCP Chimney Offload on the new cluster nodes network adapters

B.
Disable the TCP/IP Offload Engine (TOE) on the new cluster nodes network adapters.

C.
Move the VM configuration file to a local storage device, and update the pointer to the file.

D.
Update the virtual networking configuration of the new cluster node to match the virtual
networking configuration of the original cluster nodes.

Explanation:
One or more virtual network adapters on the virtual machine are not connected to a highly
available virtual network.
If the virtual networks on all hosts in the host cluster do not have the same name and the
same case (virtual network names are case-sensitive), a highly available virtual machine
might lose connectivity when it is migrated or fails over to another cluster node. To find out

the common virtual networks for the cluster, in the VMM Administrator Console, view the
Networks tab in the host cluster properties. To configure virtual networks on the hosts, use
the Networking tab in host properties. For a VN to be marked as HA, The location and tag of
the VN in all nodes must be the same. For each VN in the cluster:
The NICs to which the VN is attached in each node have the same location
The Tag in the VN in each node is the same
The VN Name is the same
After you commit changes, refresh the cluster so ensure that the VN is detected as HA.
To check that the VNs are properly detected as HA:
In the admin console, select the cluster, right click and select properties
Go to the Virtual Networks and check that the VNs are displayed.
If a VN is not displayed, it means that location, tag or name is not consistent across the
cluster nodes Lastly, if the VM has a DVD image attached, ensure that the .iso file resides in
the shared storage and not in a local volume of the Host.
Go to the VM properties and in the hardware tab select the DVD driver.
Check the path to the .iso file points to a share resource.
On Windows Server 2008 R2 the difference between Balanced and High Performance is
minimal:
Balanced Settings (default):
– Hard disk –> Turn off hard disk after –> 0 minutes
– Sleep –> Allow wake timers –> Enable
– USB settings –> USB selective suspend setting –> Enabled
– Power buttons and lid –> Power button action –> Shut down
– PCI Express –> Link State Power Management –> –> Moderate power savings
– Processor power management – System cooling policy –> Active
– Display –> Turn off display after –> 10 Minutes
High Performance:
– Hard disk –> Turn off hard disk after –> 0 minutes
– Sleep –> Allow wake timers –> Enable
– USB settings –> USB selective suspend setting –> Enabled
– Power buttons and lid –> Power button action –> Shut down
– PCI Express –> Link State Power Management –> –> Off
– Processor power management – System cooling policy –> Active
– Display –> Turn off display after –> 15 Minutes
Note: Differences indicated in bold.
If Hyper-V switch driver installation has gone corrupt.
You could either:
1. Remove/re-add the Hyper-V role
2. Uninstall and re-install the switch driver (instructions below)
For 2:
1. Close Hyper-V manager
2. close ncpa.cpl
3. “net stop nvspwmi” (from an elevated prompt)
4. “netcfg.exe -u VMS_PP” (from an elevated prompt)
5. “netcfg.exe -c p -i VMS_PP” (from an elevated prompt)
6. Reboot
In case Switch driver installation issue is still suspected then check the setupapi logs.
1. Change
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\LogLevel to
0x2000ffff
2. Reboot

3. Try it again
4. check \windows\inf\setupapi.app.log and \windows\inf\setupapi.dev.log