.png)
Checklist: Single-Server Upgrade (Complex)
Updated: January 15, 2013
Applies To: 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 single-server management group that does not meet the supported configuration requirements for System Center 2012 – Operations Manager, and requires new hardware. For more information, see Supported Configurations for System Center 2012 – Operations Manager.
If your single-server management group already meets the minimum supported configurations for System Center 2012 – Operations Manager, or if you have a distributed 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 distributed management group already meets the minimum supported configurations for System Center 2012 – Operations Manager. |
|
|
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 single-server management group if it does 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 Single-Server Upgrade (Complex) |
| Task | References | |
|---|---|---|
|
Add a secondary management server and install System Center Operations Manager 2007 R2. |
How to Add an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade) |
|
|
Move agents that report to the root management (RMS) server to the secondary management server. |
|
|
|
If 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. |
|
|
|
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 server. |
How to Upgrade a Secondary Management 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 of Free Space |
|
|
Back up the databases. |
|
|
|
Restore the encryption key on secondary management server. |
Restore the Encryption Key on the Secondary Management Server |
|
|
Run management group upgrade on the secondary management server. |
How to Upgrade a Management Group from an Operations Manager 2007 R2 Secondary Management Server |
|
|
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. |
See Also
Concepts
Upgrade Path Checklists for Operations ManagerOther Resources
Single-Server Upgrade (Complex)-----
For additional resources, see Information and Support for System Center 2012.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
