Performing Post-Upgrade Tasks in VMM
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Virtual Machine Manager
After completing the Virtual Machine Manager (VMM) upgrade, you may need to make additional configuration changes to your VMM environment.
Reassociating Hosts and Library Servers
In some upgrade scenarios, you will need to reassociate virtual machine hosts and VMM library servers with the VMM management server after the upgrade. For example, you will need to reassociate hosts and library servers if you performed the upgrade on a server other than where System Center 2012 – Virtual Machine Manager was installed. To reassociate a host or library server, see How to Reassociate a Host or Library Server.
Updating VMM Agents
After upgrading, you will need to update the VMM agent on your Hyper-V hosts and VMM library servers. You do not have to immediately update the VMM agents on Hyper-V hosts and library servers. The older version of the VMM agent that comes with System Center 2012 – Virtual Machine Manager (VMM) is supported by System Center 2012 SP1, but it does not provide all of the functionality that the VMM agent that comes with System Center 2012 SP1 has. To take advantage of all the new functionality, update your VMM agents on your Hyper-V hosts and library servers. To update the VMM agent, see How to Update the VMM Agent.
Updating Virtual Machine Templates
Virtual machine template settings that specify which virtual hard drive contains the operating system are not preserved during the upgrade process. After upgrading, for all virtual machine templates that were upgraded, you will need to update the virtual machine template to specify which virtual hard disk contains the operating system.
To update a virtual machine template, in the VMM console, open the Library workspace, expand Templates, and then click VM Templates. In the Templates pane, right-click the virtual machine template that you want to update, click Properties, and then go to the Hardware Configuration page.
Updating Driver Packages
After upgrading, any driver packages that were previously added to the VMM library must be removed and added again to be correctly discovered. For more information about adding driver packages to the VMM library, see How to Add Driver Files to the VMM Library.
Relocating the VMM Library
After upgrading to a highly available VMM management server, we recommend that you relocate your VMM library to a highly available file server. For more information about VMM libraries, see Configuring the VMM Library.
After you have created a new VMM library, you will want to move the resources from the previous VMM library to the new VMM library. Here is the recommended method for moving various types of library resources:
To move file-based resources, such as International Organization for Standardization (ISO) images, scripts, and virtual hard disks (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.
Operating system and hardware profiles cannot be moved. These profiles will need to be recreated.
Installing Additional VMM Consoles
After upgrading VMM, you can install additional VMM consoles on stand-alone servers. To connect to a VMM management server that is running System Center 2012 SP1, you must use the version of the VMM console that comes with System Center 2012 SP1.
For information about how to install the VMM console that comes with System Center 2012 SP1, see Installing and Opening the VMM Console.