Upgrading to VMM 2008 R2 from VMM 2008
Updated: January 28, 2010
Applies To: Virtual Machine Manager 2008 R2
This topic provides step-by-step instructions for upgrading to System Center Virtual Machine Manager (VMM) 2008 R2 from VMM 2008 while retaining your previous VMM data. If you do not want to retain your existing data, uninstall VMM 2008, selecting the Remove data option on the Uninstallation Options page, and then perform a clean installation of VMM 2008 R2. For more information, see New Installation of VMM.
Before you start an upgrade to VMM 2008 R2, carefully review Supported Operating Systems for VMM Components (http://go.microsoft.com/fwlink/?LinkID=163851). Note especially the following requirements:
For information about migrating from a pre-release version of VMM 2008 R2 to VMM 2008 R2, see Migrating to VMM 2008 R2 from VMM 2008 R2 RC.
Upgrading to VMM 2008 R2 from VMM 2007 is not supported. To migrate to VMM 2008 R2 from VMM 2007, you must first migrate from VMM 2007 to VMM 2008 and then upgrade to VMM 2008 R2. For information about migrating from VMM 2007 to VMM 2008, see Migrating to VMM 2008 from VMM 2007 (http://go.microsoft.com/fwlink/?LinkID=142430).
|To avoid any loss of important data, before you upgrade VMM, it is highly recommended that you perform a full backup on your VMM database.|
|After upgrading VMM, all jobs that were run prior to the upgrade will appear in the job history; however, those jobs cannot be restarted after the upgrade. It is recommended that you allow all jobs to complete before upgrading the VMM server. Jobs that are canceled during the upgrade cannot be restarted after the upgrade is completed.|
Use the following procedure to upgrade from VMM 2008 to VMM 2008 R2. To perform this procedure, you must have administrator permissions on the computer.
To upgrade from Virtual Machine Manager 2008
Log on to the computer on which your VMM 2008 server is installed.
On the product media or network share, right-click setup.exe, and the click Run as administrator.
Important If you set up a network share to install VMM components, you should apply the appropriate security to the share to ensure that no unauthorized or unauthenticated users can access or alter the contents of the share.
On the Setup menu, click VMM Server to open the Upgrade System Center Virtual Machine Manager 2008 Wizard.
On the Confirmation page, verify the list of VMM components that are already installed on this computer, and then to upgrade all installed VMM components, click Upgrade.
Note If you want to move one or more of the installed VMM 2008 components to a different computer for your VMM 2008 R2 implementation, click Cancel, uninstall those VMM components from this computer, and then run setup.exe again.
On the SQL Server Settings page, provide credentials that have permission to access and update the VMM database by doing one of the following:
To use the same credentials that you are logged on with, click Next.
To provide a different set of credentials, select the Use the following credentials check box, and then type the credentials.
Important If any jobs are running when you started the upgrade, you will receive a warning message. You can do one of the following:
Click Cancel to cancel the wizard, wait for the jobs to complete, and then run the upgrade wizard again.
Click OK to ignore the warning and continue the upgrade. VMM will cancel the jobs that are running.
- Click Cancel to cancel the wizard, wait for the jobs to complete, and then run the upgrade wizard again.
- To use the same credentials that you are logged on with, click Next.
On the Completion page, click Close.
Important You also must run the Upgrade System Center Virtual Machine Manager 2008 Wizard to upgrade any VMM 2008 components that are installed on other computers, including the VMM Administrator Console and the VMM Self-Service Portal. In the following steps, you upgrade the VMM agents on managed computers by using the VMM 2008 R2 Administrator Console. If you have integrated System Center Operations Manager 2007 with VMM, you need to update that separately. For more information, see Updating Operations Manager Integration After Upgrading to VMM 2008 R2 (http://go.microsoft.com/fwlink/?LinkID=147710).
After upgrading VMM, all hosts and library servers must be refreshed to show the correct status. To run an on-demand host refresh, in the VMM 2008 R2 Administrator Console, in Hosts view, select one or more hosts, and then, in the Actions pane, click Refresh.
You can check the status of the host refresh in Jobs view.
After a host has been refreshed, it will have a status of Needs Attention, except for the VMM server if it is also serving as a host. This is because the stand-alone hosts still have the previous version of the VMM agent installed. These hosts are fully functional, so you do not have to immediately update the agents on all VMM 2008 hosts.
Note So that performance is not adversely affected, it is recommended that you update hosts in batches of 10 to 25.
To update the hosts, in the VMM Administrator Console, in Hosts view, select one or more hosts with a status of Needs Attention, and then in the Actions pane, click Update Agent.
You can check the status of the agent update in Jobs view. When the refresh is complete, the host status will be OK.
After the next periodic library refresh, in the VMM Administrator Console, navigate to Administration view, and then click Managed Computers. The default library refresh interval is 1 hour. You can check the status of library refreshes in Jobs view. You cannot manually refresh a library server.
Select one or more computers that have a role of Library and an agent status of Upgrade Available, and then, in the Actions pane, click Update Agent.
When the update is complete, all stand-alone library servers will have a version status of Up-to-date. For a highly available library server, the version status of each cluster node is updated after the next library refresh.
After upgrading VMM, update Operations Manager integration, if necessary. For more information, see Updating Operations Manager Integration After Upgrading to VMM 2008 R2. (http://go.microsoft.com/fwlink/?LinkID=147710).