How it works...
If your VMM 2008 R2 does not have the SP1 update applied to it, start by applying it in order for it to be supported for the upgrade to VMM 2012. If you are planning to do an in-place upgrade to VMM 2012 SP1, and if you are running Windows Server 2008 R2, you need to carry it out in two phases and then consider upgrading to VMM 2012 R2 and so on:
- Upgrade from VMM 2008 R2 SP1 to VMM 2012: Carry out a VMM database backup, remove VMM 2008 R2 SP1 (choosing to retain data), and then during the VMM 2012 installation, provide the previously-saved database. VMM 2012 will upgrade the database during the installation.
- Upgrade from VMM 2012 to VMM 2012 SP1: As VMM 2012 SP1 requires Windows Server 2012, you first need to run an in-place upgrade of the OS to Windows Server 2012 , install the prerequisites, and then carry out the upgrade from VMM 2012 to VMM 2012 SP1.
- Upgrade from VMM 2012 SP1 to VMM 2012 R2: As it is recommended Windows 2012 R2 for VMM 2012 R2, you first need to run an in-place upgrade of the OS to Windows Server 2012 R2, install the prerequisites, and then carry out the upgrade from VMM 2012 SP1 to VMM 2012 R2.
- Upgrade from VMM 2012 R2 to VMM 2016: VMM 2016 can be running only on Windows Server 2016. So, you need to complete the OS upgrade, install the VMM prerequisites, and then carry out the upgrade to 2016.
During the upgrade process, if you did not install the command-line utilities for SQL
Server beforehand, a warning will be shown in the prerequisites check phase. Although
you can proceed without installing these utilities, it is not recommended as they are
required to perform some management tasks (see the SQL Server Connectivity Feature
Pack Components section under the Installing VMM dependencies recipe in Chapter 3,
Installing VMM 2016).