Performing Post-Upgrade Tasks in VMM

Updated: May 13, 2016

Applies To: System Center 2012 R2 Virtual Machine Manager

After you complete the Virtual Machine Manager (VMM) upgrade, you may need to make additional configuration changes to your VMM environment. For example, you may need to make the following changes:

In some upgrade scenarios, you need to reassociate virtual machine hosts and VMM library servers with the VMM management server after the upgrade. For example, you need to reassociate hosts and library servers if you performed the upgrade on a server other than where VMM in System Center 2012 SP1 was installed.

For more information, see How to Reassociate a Host or Library Server.

After the upgrade, you need to update the VMM agents on your Hyper-V hosts and in your VMM library servers. You do not have to immediately update the VMM agents on Hyper-V hosts and library servers. The version of the VMM agent that comes with System Center 2012 SP1 is supported in System Center 2012 R2, but it does not provide all of the functionality of the VMM agent in System Center 2012 R2. To take advantage of the new functionality, update your VMM agents on your Hyper-V hosts and library servers.

For more information, see How to Update the VMM Agent.

If you upgraded a database that was configured with AlwaysOn Availability Groups, you need to complete a few tasks to ensure that the upgraded database is properly configured with AlwaysOn Availability Groups. For more information, see How to Complete the Configuration of AlwaysOn Availability Groups for the Database.

If Windows Azure Hyper-V Recovery Manager is implemented in the VMM environment, then you need to perform a few steps to restore the Windows Azure Hyper-V Recovery Manager Provider.

For more information, see How to Restore Windows Azure Hyper-V Recovery Manager Provider.

All virtual machine templates that were upgraded need to correctly specify the virtual hard disk that contains the operating system.

Driver packages that were previously added to the VMM library must be removed and added again to be correctly discovered.

For more information, see How to Add Driver Files to the VMM Library.

If you upgraded to a high availability VMM management server, we recommend that you relocate your VMM library to a high availability file server.

For more information, see Configuring the VMM Library.

After you create a new VMM library, you will want to move the resources from the previous VMM library to the new VMM library.

• To move file-based resources (such as ISO images, scripts, and VHDs), see How to Import and Export Physical Resources To and From the VMM Library.

• To move virtual machine templates, see Exporting and Importing Service Templates in VMM.

• To preserve the custom fields and properties of saved virtual machines in the previous VMM library, deploy the saved virtual machines to a host and then save the virtual machines to the new VMM library.

You can install additional VMM consoles on stand-alone servers. To connect to a VMM management server that is running System Center 2012 R2, you must use the version of the VMM console that comes with System Center 2012 R2.

For more information , see Installing and Opening the VMM Console.