Checklist: Distributed Upgrade (Simple)
Updated: May 13, 2016
Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager
This checklist walks you through an upgrade of a System Center Operations Manager 2007 R2 distributed management group that meets the supported configuration requirements for System Center 2012 – Operations Manager. For more information, see Supported Configurations for System Center 2012 – Operations Manager.
If your distributed management group does not yet meet the minimum supported configurations for System Center 2012 – Operations Manager, or if you have a single-server management group, see the following checklists.
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 has one or more servers that do not meet the minimum supported configurations for System Center 2012 – Operations Manager and might require new hardware. |
Checklist
Use the following checklist to upgrade your distributed management group if it already meets 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 Single-Server and Distributed Updated (Simple).
Note
In this checklist, we recommend that you move agents that report to the root management server (RMS) to a secondary management server before upgrading the agents. However, if you do not mind experiencing downtime, you can upgrade the agents after you upgrade the management group instead of moving them to a secondary management server.
Task |
References |
|
|---|---|---|
.jpeg "Checklist box")
|
Import the Upgrade Helper management pack. |
|
|
|
Move agents that report to the RMS to a secondary management server. |
|
|
|
Back up the encryption key. |
|
|
|
Review the Operations Manager 2007 R2 event logs. |
|
|
|
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 gateways, if present. |
How to Upgrade a Gateway Server from Operations Manager 2007 R2 |
|
|
Upgrade the push-installed agents. |
|
|
|
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 enough free space. |
Verify that the Operational Database Has More Than 50 Percent Free Space |
|
|
Back up the databases. |
|
|
|
Restore the encryption key on secondary management server. |
Restore the RMS Encryption Key on the Secondary Management Server |
|
|
Run management group upgrade on the root management server. |
How to Upgrade a Management Group from an Operations Manager 2007 R2 RMS |
|
|
Upgrade or install the optional features, such as the web consoles and Reporting server. |
|
|
|
Re-enable notification subscriptions. |
|
|
|
Restart or re-enable the service for any connectors that are installed. |
|
|
|
Update overrides. |
|
|
|
Verify the success of the upgrade. |