Notes about Orchestrator If Orchestrator is part of your environment, then Orchestrator will be the first component that you upgrade. Note If you are going to add the new component Service Management Automation to your environment, you must install that now before upgrading Orchestrator. You need to be that any System Center component integration packs (IP) that you installed on System Center 2012 SP1 will not function with System Center 2012 R2 components. When upgrading Orchestrator, you will do so leaving the System Center 2012 SP1 IPs in place so that current functionality continues until the other components are upgraded. When you upgrade subsequent components, for example Service Manager 2010 SP1, you will uninstall the System Center 2012 SP1 IP. After your component has been upgraded, go back to the Orchestrator computer and install the R2 version of the IP. This sequence is detailed both in this guide and in the Upgrade Guide for Orchestrator. Note When you install an upgrade of an integration pack, you must first uninstall any earlier version of the integration pack from all Runbook servers and Runbook Designers. You then register and deploy the upgrade of the integration pack. If you do not uninstall the previous version of the integration pack prior to registering and deploying the upgrade version, the upgrade version will fail. Notes about Configuration Manager Configuration Manager shares connectors with Operations Manager, has an integration pack with Orchestrator, and has a management pack with Operations Manager. Configuration Manager must be upgraded after Orchestrator, Operations Manager, and Service Manager to ensure continued operations with the connections it shares with other components. Configuration Manager agents for System Center 2012 do not support managing Windows Server 2012 operating systems so Configuration Manager will need to be upgraded before Virtual Machine Manager since Virtual Machine Manager has a mandatory requirement on Windows Server 2012. For example, if you were to upgrade Configuration Manager before Service Manager, the connectors for Service Manager would fail and you would lose that connector functionality until Service Manager is upgraded to System Center 2012 R2. As another example, if you were to upgrade Virtual Machine Manager to System Center 2012 R2 before Configuration Manager you not be able to manage the VMM management server as the Configuration Manager for System Center 2012 does not support Windows Server 2012.
Notes about Orchestrator If Orchestrator is part of your environment, then Orchestrator will be the first component that you upgrade. Note If you are going to add the new component Service Management Automation to your environment, you must install that now before upgrading Orchestrator. You need to be that any System Center component integration packs (IP) that you installed on System Center 2012 SP1 will not function with System Center 2012 R2 components. When upgrading Orchestrator, you will do so leaving the System Center 2012 SP1 IPs in place so that current functionality continues until the other components are upgraded. When you upgrade subsequent components, for example Service Manager 2010 SP1, you will uninstall the System Center 2012 SP1 IP. After your component has been upgraded, go back to the Orchestrator computer and install the R2 version of the IP. This sequence is detailed both in this guide and in the Upgrade Guide for Orchestrator. Note When you install an upgrade of an integration pack, you must first uninstall any earlier version of the integration pack from all Runbook servers and Runbook Designers. You then register and deploy the upgrade of the integration pack. If you do not uninstall the previous version of the integration pack prior to registering and deploying the upgrade version, the upgrade version will fail. Notes about Configuration Manager Configuration Manager shares connectors with Operations Manager, has an integration pack with Orchestrator, and has a management pack with Operations Manager. Configuration Manager must be upgraded after Orchestrator, Operations Manager, and Service Manager to ensure continued operations with the connections it shares with other components. Configuration Manager agents for System Center 2012 do not support managing Windows Server 2012 operating systems so Configuration Manager will need to be upgraded before Virtual Machine Manager since Virtual Machine Manager has a mandatory requirement on Windows Server 2012. For example, if you were to upgrade Configuration Manager before Service Manager, the connectors for Service Manager would fail and you would lose that connector functionality until Service Manager is upgraded to System Center 2012 R2. As another example, if you were to upgrade Virtual Machine Manager to System Center 2012 R2 before Configuration Manager you not be able to manage the VMM management server as the Configuration Manager for System Center 2012 does not support Windows Server 2012.
SC2012R2_UpgradeSeq.docx