Test Layout

I regularly get Hyper-V VMs for use developing course materials. Our environment is pretty standardized, so, there are seldom any issues. However, today when running our import script, I got the following error for several of the VMs in a new course: Import-VM : Unable to import virtual machine due to configuration errors. Please use Compare-VM to repair the virtual machine. So, I ran Compare-VM and placed the output in a variable for easier viewing: $report=Compare-VM -Path .\ GUID .xml The mystery was solved when I looked at the incompatibilities property in the output: $report.incompatibilities The incompatibilities showed that a a virtual network was missing: Message: Could not find Ethernet switch 'Cluster Network'. MessageID: 33012 Source: Microsoft.HyperV.PowerShell.VMNetworkAdapter When I took a look at my virtual networks, I saw that the script I ran to create the virtual networks created Cluster_Network instead of "Cluster Network". After I renamed the netwo...

We work with Dell servers and they come with Broadcom network cards. In general they work well, but they have an issue when being used as Hyper-V hosts. Virtual machine queues which in theory improve performance end up bogging down networking. Symptoms we've seen: Slow file copying to/from VMs over the network. Dropped network connection for entire host that is fixed by reboot. In both cases the fix is to disable virtual machine queues (VMQ). We had been doing it in the properties of the physical network on the Hyper-V host. However, we were recently having issues with a host and that option wasn't in the interface provided by the driver. Some blogs were referring to using registry edits to disable it. However, a faster and easier way in Windows Server 2012 R2 (maybe also Windows Server 2012, but I haven't verified) is by using Windows PowerShell. To view the VMQ status of your network adapters: Get-NetAdapterVmq To disable VMQ for all adapters: Get-NetAdapterVmq | Disable-...

As part of a project I'm working on, I need to remote control a Hyper-V guest using Hyper-V Manager installed on a Vista computer that is not part of the domain. Basically, I don't want to put my regular workstation into my test domain. After a bit of pain, the simplest solution I found is this: Create an account in the domain running Hyper-V that has the exact same logon name and password as the account being used on the Vista computer. Configure COM on the Vista computer to allow anonymous remote connections. Then BOOM! It works. And you can do your screen recordings remotely. For click-by-click instructions on the configuring COM, see step 7 in this blog: http://blogs.technet.com/jhoward/archive/2008/03/28/part-2-hyper-v-remote-management-you-do-not-have-the-requested-permission-to-complete-this-task-contact-the-administrator-of-the-authorization-policy-for-the-computer-computername.aspx