1. Deploy your standard Windows Server 2012 R2 template. Mine happened to be fully patched, and included the spring “update” which gave us back a semi-functional start button. I also used customizations specifications to automatically rename the VM, install license key, change the SID, etc. Nothing earth shattering here. I also used vHW v8, versus the newer v10 VM.
2. Power off your freshly deployed WS2012 R2 VM, and unregister it from vCenter.
3. Download the corresponding .VMX file to your computer and open it in Wordpad.
4. Somewhere in the VMX file add the two following lines:
vhv.enable = “TRUE”
hypervisor.cpuid.v0 = “FALSE”
5. If you have upgraded your VM to vHW 10 then you can follow William Lam’s tip and set the guestOS to use to be “windowsHyperVGuest”. If you are using vHW v8 then I just left it to the default “windows8svr-64″.
6. Save the VMX file and re-upload it to the datastore, overwriting the old file.
7. Right click on the VMX file and register the VM.
8. Now I didn’t need to do this, but saw some other users that had to configure this setting. In vCenter open the properties of the VM and change the CPU/MMU virtualization option. Select the bottom option.
9. Power on your VM, then login to Windows.
10. Install the Hyper-V role, and you shouldn’t get any warnings. Reboot after the roll is installed, and now you are ready to rock and roll with Hyper-V 2012 R2.
