How to do it...

Carry out the following steps to check if your environment meets the system requirements, and to perform the initial steps for an in-place upgrade to a newer VMM:

1. Remove the integration of SCOM with VMM.
2. Remove the integration of VMM with VMware vCenter.
3. Wait for the completion of all jobs running in VMM.
4. Close the VMM console and the VMM command shell. If you have VMM up to 2012 and Self-Service portal installed, close the portal as well.

1. Perform a full backup of the VMM database.
2. The following is applicable for VMM 2012 SP1 and later: if the current VMM database is configured with AlwaysOn Availability Groups, remove it and then initiate a failover to the SQL Server machine on which the VMM database is installed; see the Upgrading VMM with configured AlwaysOn Availability Groups section of the Upgrading to VMM 2016 recipe.
3. If your VMM library is running on another machine, make sure that the OS version meets the minimum requirements. Upgrade the OS if necessary.
4. Update the server by running Windows Update or by implementing the latest update rollup (manually).
5. Verify that there are no pending restarts on the server. Restart the server
   if necessary.