You are currently reviewing an older revision of this page.
Go to current version
This article starts from personal experience. Please, continue to add to it with more information for various upgrade scenarios.

Table of Contents

Single Hyper-V Server Running Windows Server 2008 R2 with GUI In Place Upgrade to Windows Server 2012 with GUI

The upgrade worked, but there are several things to be aware of before you start:

  1. No one else must be logged on to the computer when you begin the upgrade, except one user a member of local Administrators.
  2. All virtual machines much be in the Off state. Saved virtual machines will be identified as a reason the upgrade cannot proceed.
  3. Do not try an in place upgrade by starting booting from the DVD, you will be told to run from inside the operating system.
  4. You will not lose your virtual machine snap-shots, but you are told that once you revert to a snap-shot, you lose all the older snap-shots. Effectively, you lose the use of your snap-shots, but you don't lose the actual snap-shots. You just have to pick the snap-shot that you want to start from - then you effectively lose the rest.

Please add more experiences and scenarios to this article as you have them.

Additional References

Migrate Hyper-V to Windows Server 2012

Revert to this revision