So I’ve set up a Hyper-V environment in my lab and installed Windows Server 2008 on one of my guest VMs, and it works great! However, one little thing annoyed me a little bit. Using RDP to the parent OS (where the Hyper-V role is installed) didn’t let me use the mouse inside the guest VM during the install. This is due to Microsoft’s Integration Services, the counterpart to VMWare Tools.
While VMWare has managed to let you use both mouse and keyboard when using the console via RDP, Microsoft requires you to install the Integration Services, and this must be applied after the OS is completely installed. This means you have to use your keyboard to TAB through the installation. Not a big problem, but a little annoying. The workaround is of course to go directly to the console of your Hyper-V server, but in my experience people familiar with installing VMs use some sort of management interface to install OSes (ie. VMWare Infrastructure Client or VMWare Console). If you use PE to install your OSes, you can also bundle the Integration Services with your PE Image so that you don’t get this problem.