With the RTM release of Hyper-V just around the corner, I thought it would be a good idea to re-visit some of the top things we have seen customers encounter when installing and configuring Hyper-V for the first time and give pointers to resources we have available to eliminate those when you start rolling this out in production for the first time. I have taken the liberty of linking many of these questions/issues to blogs written by our program managers on the virtualization team. We did a previous post on their sites but I thought this would serve as a quick reference and a pointer to them at the same time.
1. You don’t have mouse functionality in your VM. One of the most commonly asked questions during the beta, internally and externally had to do with lack of mouse support in a guest when its running. One of the main reasons we saw this happening was that people were remoted into the parent and then controlling the guest from there, that wont work in Hyper-V. More information about best practices can be found here:
2. Hyper-V wont install. Another common question had to do with Hyper-V not installing at all. People would add the role and either would get errors post installation, prior to installation, etc. So, to revisit the core requirements for the Hyper-V role to be installed and functional on your machine, see the release notes once we RTM. Top issues here though were folks not enabling Virtualization and DEP in their system BIOS, not shutting down the parent completely at the end of installation but rebooting the parent instead, and not adding the proper entries to the BCD store on a Core installation (hint: rebooting twice takes care of this in Core).