In this article

Upgrading System Center Operations Manager

In this article

This section of the Deployment Guide provides information about how to upgrade to System Center 2016 - Operations Manager or version 1801 from an older supported version.

It is assumed in this guide that you are performing an upgrade to System Center 2016 - Operations Manager or version 1801. For information about installing Operations Manager on a computer where no previous version of Operations Manager exists, see Deploying System Center Operations Manager.

Note

If your Operations Manager 2012 R2 or Operations Manager 2016 management group is integrated with Microsoft Azure Log Analytics (Formerly referred to as Microsoft Operations Management Suite (OMS)), its configuration will be retained and continue to function normally after the upgrade is complete.

Warning

If you are upgrading two or more System Center components, you should review the upgrade process for each component.

The order in which you perform component upgrades is important. Failure to follow the correct upgrade sequence might result in component failure for which no recovery options exist. The following list are the affected System Center components integrated with Operations Manager and the recommended upgrade sequence:

Orchestrator - if you have the Operations Manager integration pack installed to support runbooks that perform automation against your Operations Manager management group.

Service Manager - if you configured the connectors to import alert and configuration item data of objects discovered and monitored from Operations Manager.

Virtual Machine Manager - if you have configured integration with Operations Manager to monitor the health of your VMM components, the virtual machines and virtual machine hosts.

Before you upgrade to System Center Operations Manager, you must first determine whether all servers in your Operations Manager management group meet the minimum supported configurations. For more information, see System Requirements: System Center Operations Manager.

There are several options for upgrade:

If you run upgrade on a single-server management group, you only need to run upgrade one time since all features are installed on a single server. The Operations Manager Upgrade wizard performs system prerequisite checks and provides resolution steps for any issues. Installation will not continue until you resolve all issues.

If you are upgrading a distributed management group, you must upgrade certain features before others. For example, you upgrade the management servers first, followed by the gateways, operations consoles, and then agents. Next, you can upgrade any remaining features, such as the web console, reporting and Audit Collection Services (ACS). You must also perform a number of pre-upgrade and post-upgrade tasks.

If you want to maintain your Operations Manager 2012 R2 or System Center 2016 - Operations Manager environment, you can install version 1801 in parallel, upgrade your agents and multi-home them between both management groups.

If you want to maintain your Operations Manager 2012 R2 environment you can install System Center 2016 - Operations Manager in parallel, upgrade your agents and multi-home them between both management groups.

Supported coexistence

The following table lists the scenarios in which coexistence between Operations Manager 2016 and earlier versions of Operations Manager is supported.

Version

Management Group Coexistence

Operations Manager 2012 R2

Yes

The following table lists the scenarios in which coexistence between Operations Manager 1801 and earlier versions of Operations Manager is supported.

Version

Management Group Coexistence

Operations Manager 2016 RTM to the latest update rollup

Yes

Operations Manager 2012 R2 to the latest update rollup

Yes

In-place upgrade

System Center 2016 - Operations Manager supports an in-place upgrade from the following versions:

System Center 2016 Technical Preview 5 - Operations Manager

System Center 2012 R2 Operations Manager with Update Rollup 12

System Center Operations Manager 1801 supports an in-place upgrade from the following versions:

System Center 2012 R2 UR12 to the latest update rollup

System Center 2016 RTM to the latest update rollup

High level overview of upgrade steps for a distributed management group

The following steps outline the process for upgrading a distributed management group:

*Steps 4 through 8 can be performed in parallel after all management servers have been upgraded.

High level overview of upgrading agents and running two environments

The following upgrade path supports customers in an Operations Manager scenario with parallel environments, sharing agents, so that the original System Center 2012 R2 Operations Manager or Operations Manager 2016 environment is left intact. Agents that have been upgraded to System Center 2016 Operations Manager or version 1801 depending on your upgrade path, are fully capable of working with native System Center 2012 R2 Operations Manager or Operations Manager 2016 functionality.

Agents can be upgraded before the new Operations Manager management group is deployed and then configured to multi-home between the original management group and the new management group using your existing automation solution or they can be upgraded after by discovering and performing a push-install from the new Operations Manager management group. For further information, see How to Upgrade Agents in a Parallel Deployment.