Checklist: Distributed Upgrade (Complex)
Updated: May 13, 2016
Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager
To upgrade a distributed System Center Operations Manager 2007 R2 management group to System Center 2012 – Operations Manager, you use a phased approach, starting with the management servers, then the gateway servers, and then the management group. The order in which you upgrade the agents depends on how they were deployed (manually installed or push-installed), and whether your root management server (RMS) meets the supported configuration requirements for System Center 2012 – Operations Manager. For example, a clustered RMS is not supported in System Center 2012 – Operations Manager. You also must perform a number of pre-upgrade and post-upgrade tasks, and might perform some optional upgrade tasks.
If any of the servers in your distributed management group do not meet the supported configuration requirements for System Center 2012 – Operations Manager, and require the installation of a new server, you should follow this checklist. For more information, see Supported Configurations for System Center 2012 – Operations Manager. Some of the servers might meet these requirements, and therefore, you might not have to perform the steps in every section. For example, if the server that hosts your RMS meets the supported configuration requirements, you can run the final upgrade from the RMS and skip the section on running the final upgrade from a secondary management server.
If your distributed management group already meets the minimum supported configurations for System Center 2012 – Operations Manager, or if you have a single-server management group, see the following topics.
Upgrade Path Checklist |
Condition |
|---|---|
Your Operations Manager 2007 R2 single-server management group already meets the minimum supported configurations for System Center 2012 – Operations Manager. |
|
Your Operations Manager 2007 R2 single-server management group does not meet the minimum supported configurations for System Center 2012 – Operations Manager and requires new hardware. |
|
Your Operations Manager 2007 R2 distributed management group already meets the minimum supported configurations for System Center 2012 – Operations Manager. |
Checklist
Use the following checklist to upgrade your distributed management group if any of the servers do not yet meet the supported configuration requirements for System Center 2012 – Operations Manager.
Tip
You can also view a process flow diagram that links to the relevant topics. For more information, see Distributed Upgrade (Complex).
This checklist contains multiple paths and you will not have to follow each step consecutively. For example, you will upgrade the management group from either the RMS or the secondary management server, depending on your current configuration. You should follow the steps in each as needed.
Section |
Description |
|---|---|
Import the Upgrade Helper Management Pack |
Use these procedures to import and use the Upgrade Helper management pack. |
Replacing Secondary Management Servers |
Use these procedures if your secondary management servers do not meet the minimum system requirements for System Center 2012 – Operations Manager. If your secondary management servers have a 32-bit operating system, you must replace each server. For each 32-bit secondary management server, you must add a new 64-bit server and move the agents from the old management server to the new management server. You must ensure that all management servers meet all of the minimum system requirements for System Center 2012 – Operations Manager. |
Replacing Gateways |
Use these procedures if your gateway servers do not meet the minimum system requirements for System Center 2012 – Operations Manager. If your gateways have a 32-bit operating system, you must replace each gateway server with a new gateway server that meets the requirements. You must ensure that all gateway servers meet the minimum system requirements for System Center 2012 – Operations Manager. |
Secondary Management Server Upgrade |
Use these procedures to upgrade the secondary management servers, any gateway servers, and agents. |
Management Group Upgrade from RMS |
Use these procedures only if your RMS meets the minimum system requirements for System Center 2012 – Operations Manager. |
Management Group Upgrade from Secondary Management Server |
Use these procedures only if your RMS does not meet the minimum system requirements for System Center 2012 – Operations Manager. |
Import the Upgrade Helper Management Pack
The Upgrade Helper management pack helps to guide you through the upgrade process. You should import this management pack before you start the upgrade process for a distributed management group that does not meet the supported configuration requirements for System Center 2012 – Operations Manager.
Task |
References |
|
|---|---|---|
.jpeg "Checklist box")
|
Import the Upgrade Helper Management Pack |
Replacing Secondary Management Servers
If your secondary management server already meets the minimum system requirements, go to the Replacing Gateways section of this checklist. Otherwise, use the following procedures for each secondary management server in your management group.
Note
You only have to add new secondary management servers if your current servers have a 32-bit operating system, which do not meet the supported configuration requirements for System Center 2012 – Operations Manager. Otherwise, just ensure that your secondary management servers meet the remaining supported configuration requirements.
Task |
References |
|
|---|---|---|
|
|
If operating system is 32-bit, add a secondary management server. |
How to Add an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade) |
|
|
Move the Operations Manager 2007 R2 agents to a secondary management server, and remove the old secondary management server. |
|
|
|
Ensure that the secondary management server meets the supported configuration requirements for System Center 2012 – Operations Manager. |
Supported Configurations for System Center 2012 - Operations Manager |
Replacing Gateways
If you do not have gateway servers, or you have gateways that meet the minimum system requirements, go to the Secondary Management Server Upgrade section of this checklist. Otherwise, use the following procedures for each gateway in your management group.
Note
You only have to add new gateway servers if your current servers are 32-bit, which do not meet the supported configuration requirements for System Center 2012 – Operations Manager. Otherwise, just ensure that your gateway servers meet the remaining supported configuration requirements.
Task |
References |
|
|---|---|---|
|
|
If gateway server does not have a 64-bit operating system, build a new gateway server. |
|
|
|
Remove the old gateway server. |
How to Remove an Operations Manager 2007 R2 Gateway (Operations Manager Upgrade) |
|
|
Ensure that the gateway server meets the supported configuration requirements for System Center 2012 – Operations Manager. |
Supported Configurations for System Center 2012 - Operations Manager |
Secondary Management Server Upgrade
Use the following procedures to upgrade your secondary management servers, gateway servers, and agents. Before you upgrade the secondary management server, you must ensure that your root management service (RMS) meets the supported configuration requirements for System Center 2012 – Operations Manager. For more information, see Supported Configurations for System Center 2012 - Operations Manager. If the RMS does not meet these configuration requirements, you must move agents that report to the RMS to the secondary management server before you upgrade the second management server. You should also ensure that SQL Server meets the supported configuration requirements.
Task |
References |
|
|---|---|---|
|
|
If RMS does not meet supported configuration requirements for System Center 2012 – Operations Manager, move agents that report to root management server to the secondary management server. |
|
|
|
If Microsoft SQL Server does not meet the supported configuration requirements, upgrade SQL Server. |
|
|
|
Back up the encryption key. |
|
|
|
Review the Operations Manager 2007 R2 event logs. |
|
|
|
Check if any gateway servers report to an unsupported RMS. |
|
|
|
Remove agents from Pending Management. |
|
|
|
Verify that you have a supported SQL Server collation on all databases and instances of databases. |
|
|
|
Upgrade the manually installed agents. |
|
|
|
Upgrade the secondary management servers. |
How to Upgrade a Secondary Management Server from Operations Manager 2007 R2 |
|
|
Upgrade gateway servers, if present. |
How to Upgrade a Gateway Server from Operations Manager 2007 R2 |
|
|
Upgrade the push-installed agents. |
Management Group Upgrade from RMS
If your RMS does not meet the minimum supported configurations for System Center 2012 – Operations Manager, go to the Management Group Upgrade from Secondary Management Server section of this checklist. Otherwise, use the following procedures to upgrade your management group from the root management server.
Note
A clustered RMS does not meet the supported configuration requirements for System Center 2012 – Operations Manager.
Task |
References |
|
|---|---|---|
|
|
Check for any active, connected consoles to the root management server. |
Check the Operations Manager 2007 R2 RMS for Active Connected Consoles |
|
|
Disable all notification subscriptions. |
|
|
|
Stop services or disable any connectors that are installed. |
|
|
|
Verify that your operational database has sufficient free space. |
Verify that the Operational Database Has More Than 50 Percent Free Space |
|
|
Back up all databases. |
|
|
|
Run management group upgrade on the root management server. |
How to Upgrade a Management Group from an Operations Manager 2007 R2 RMS |
|
|
Upgrade optional features. |
|
|
|
Re-enable the notification subscriptions. |
|
|
|
Restart or re-enable the service for any connectors that are installed. |
|
|
|
Update overrides. |
|
|
|
Verify the success of the upgrade. |
Management Group Upgrade from Secondary Management Server
If your root management server meets the minimum supported configurations for System Center 2012 – Operations Manager, go to the Management Group Upgrade from RMS section of this checklist. Otherwise, use the following procedures to upgrade your management group from a secondary management server.
Note
A clustered RMS does not meet the supported configuration requirements for System Center 2012 – Operations Manager.
Task |
References |
|
|---|---|---|
|
|
Check for any active, connected consoles to the root management server. |
Check the Operations Manager 2007 R2 RMS for Active Connected Consoles |
|
|
Disable all notification subscriptions. |
|
|
|
Stop services or disable any connectors that are installed. |
|
|
|
Verify that your operational database has sufficient free space. |
Verify that the Operational Database Has More Than 50 Percent Free Space |
|
|
Back up all databases. |
|
|
|
Restore the encryption key. |
Restore the RMS Encryption Key on the Secondary Management Server |
|
|
Run the management group upgrade on the secondary management server. |
How to Upgrade a Management Group from an Operations Manager 2007 R2 Secondary Management Server |
|
|
If required, install the optional features, such as the consoles and Reporting. |
|
|
|
Re-enable the notification subscriptions. |
|
|
|
Restart or re-enable the service for any connectors that are installed. |
|
|
|
Uninstall the old root management server. |
|
|
|
Update overrides. |
|
|
|
Verify the success of the upgrade. |