A cautionary note for those of you performing an in-place upgrade of a machine running Windows Server 2008 with the Hyper-V role enabled, to Windows Server 2008 R2 Release Candidate.
During the installation, you will see the following compatibility report message stating that you should turn off the Hyper-V role:
This warning is incorrect, and you should not do this as the virtual machines will not be present, and virtual network configuration will be lost once the role is re-enabled.
You will see a similar message if you have virtual machines running at the time of upgrade, but it is a “hard block” (in other words, you cannot proceed further). In the case where you hit the hard block, running VMs should be cleanly shut down prior to upgrade. However, I re-iterate, you should not remove the role itself.
One other point to note is if you have online snapshots or virtual machines in a saved state. Saved states are not compatible between Hyper-V in Windows Server 2008 and Windows Server 2008 R2 RC build, so you should ensure you cleanly shut down VMs and delete online snapshots prior to upgrading to avoid the following message after the upgrade is complete:
Rajshekhar - you're welcome :) And thanks!
John - to confirm your last note - your team was not able to fix the hang on reboot for any 2008 to 2008 R2 upgrades running HV? I was trying to in-place upgrade my Hyper-V to R2 and it hung on reboot - black screen with a mouse - but nothing. I had all VM's off - but had snapshots - so I am removing all of them now and will try again. But if you say thsi will not work w/o removing the role - then I won't be doing this quite yet.
i am keen follower of your blog and i always find very educating. i have been running Server 2008 with the the hyper-V role enabled for some time now.
i have 3 VMs running on the host.
i am in the process of upgrading the Hyper-V role to the R2 version, is this possible?
if yes, what are the necessary precautions to take for a smooth upgrade experience?
thanks for your anticipated help.
Abiodun - assuming you follow the gotch above, the only other thing you should look to do is to cleanly shutdown VMs before the in-place upgrade and merge online snapshots. Otherwise, it should work just fine.
Ron - the hang described above was on one particular system. It strongly implies a problem with the hardware (BIOS most likely), and I iterate it's not a supported platform for running Hyper-V (Windows Server Catalog lists supported systems). Are you using the same hardware? Have you attempted to upgrade the BIOS to verify?
Hi everyone. This paper is really helpful, but in my case is not working. I already done all the steps. I got the next message from Hyper-V manager tool in my laptop ""cannot connect to the RPC service". My HYPER-V server has TMG, but I already discard firewall, because I stopped the service and the problem is still happening. The client is a workgroup and the TMG is domain server. I have checked everything on the web and I didn't find anything. My client is Windows 7 x64 enterprise and my Hyper-V server is Windows 2008 enterprise R2 with all recent updates. any help it will be appreciated.
Anderson - Did remote management work before the upgrade to R2? (ie it's not an issue with TMG, even if the service is disabled).
If it's a remote management connectivity issue, your best bet to diagnose is hvremote from http://code.msdn.microsoft.com/hvremote. I suspect that it if you did an inplace upgrade and had non-admin users added before, the ACLs on the WMI namespaces have not been preserved across upgrade. hvremote /show /target:otherboxname on both boxes will reveal all.
well on the other side of the note how do you actually correct this issue if you have did as the instructions asked and deleted hyper v and then installed 2008 R2 then reinstalled hyperV. because now i get event id 3040 and 3080 since i did this upgrade