How to Add an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade)
Updated: May 13, 2016
Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager
When you want to upgrade to System Center 2012 – Operations Manager but have a management server in your System Center Operations Manager 2007 R2 environment that does not meet the minimum supported configurations for System Center 2012 – Operations Manager, you must add a new server to replace the old one. You should install an Operations Manager 2007 R2 secondary management server, and then join it to your existing management group. Afterwards, you can move the agents from the old server to the new server. For more information, see How to Move Agents to an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade).
To ensure that your new server hardware and software meet the minimum supported configurations for System Center 2012 – Operations Manager, see Supported Configurations for System Center 2012 - Operations Manager.
To install a secondary management server
-
On a server that meets the supported configuration requirements for System Center 2012 – Operations Manager, install Operations Manager 2007 R2 by using the instructions in Deploying Stand-Alone Management Servers on Windows Server 2008.
Note
It can take up to five minutes for the System Center Management Service on the new management server to establish secure communications with the root management (RMS) server, and during that time it appears as not monitored. When communications are established, its Health state changes to Healthy.
The next step is to move the agents that reported to the old management server or RMS to the new secondary management server. For more information, see How to Move Agents to an Operations Manager 2007 R2 Secondary Management Server (Operations Manager Upgrade).