上QQ阅读APP看书，第一时间看更新
Upgrading VMM on a different computer
Sometimes, you may not be able to do an in-place upgrade to VMM 2012, or even to later VMM versions. In this case, it is recommended that you use the following instructions that are suitable for later VMM versions as well:
- Uninstall the current VMM, retaining the database, and then restore the database on a supported version of SQL Server.
- Next, on a new server (or on the same server, as long it meets the hardware and OS requirements), install the VMM server prerequisites.
- Finally, install the new VMM, providing the retained database information on the Database configuration dialog and the VMM setup will upgrade the database. When the install process finishes, upgrade the Hyper-V hosts with the latest VMM agents.
When performing an upgrade from VMM 2008 R2 SP1 with a local VMM database to a different server, the encrypted data will not be preserved as the encryption keys are stored locally. The same rule applies when upgrading from VMM 2012 or VMM 2012 R2 to VMM 2016 and not using Distributed Key Management ( DKM).