• Article

Operations Manager

 

Updated: May 13, 2016

Applies To: System Center 2012 R2

System Center 2012 R2 Operations Manager is the fourth component to be upgraded. If applicable, install Service Management Automation, upgrade Orchestrator, upgrade Service Manager, and then upgrade System Center 2012 R2 Data Protection Manager before you upgrade System Center 2012 R2 Operations Manager.

Operations Manager Upgrade Sequence

  1. If present, the VMM-to-Operations Manager connection should be removed, either from the VMM console or by using the Remove-SCOpsMgrConnection cmdlet.

    Note

    VMM will not be monitored during the upgrade.

  2. Remove the System Center 2012 SP1 version of the Operations Manager console from all Virtual Machine Manager and Orchestrator servers.

  3. On the computer hosting the Orchestrator Deployment Manager, uninstall the IP for System Center 2012 SP1 version of Operations Manager.

  4. Upgrade the following Operations Manager parts in the order listed using the procedures outlined in the Upgrade Guide for Operations Manager. The Operations Manager Database and Data Warehouse will be upgraded when the first management server is upgraded.

    • At least one Operations Manager management server.

    • Any remaining Operations Manager management servers.

    • Any Operations Manager gateways

    • Any Operations Manager consoles.

    • Any Operations Manager agents.

Post–Operations Manager Upgrade

  1. On the computer hosting the Orchestrator Deployment Manager, install the IP for the System Center 2012 R2 version of Operations Manager.

  2. Install the System Center 2012 R2 version of the Operations Manager console on Orchestrator and VMM.

  3. Re-establish connectivity between System Center 2012 SP1 version of VMM and System Center 2012 R2 Operations Manager.

  4. Register the Operations Manager integration packs on System Center 2012 R2 Orchestrator.

  5. Make sure that the Configuration Manager agent continues to function.

  6. Make sure that the following connections with Virtual Machine Manager continue to function:

    • Management pack

    • Integration using the Operations Manager console (for IP communication)

  7. Make sure that the following connections with Service Manager continue to function:

    • Connectors (2)

    • Management pack

    • Agentless monitoring

  8. Make sure that the following connections with DPM continue to function:

    • Management pack

    • Central Console Server components

  9. Make sure that the following connections with Orchestrator continue to function:

    • Management pack

    • Integration Pack (Operations Manager console (SDK) connection required for IP)

  10. Make sure that the management pack continues to function with App Controller.