SCOM 2012 - Pre and Post SP1 Upgrade Sequence Tasks

If you're upgrading your SCOM 2012 RTM deployment to Service Pack 1 (SP1), then there are a few tasks that need to be carried out in sequence both before and after the service pack upgrade.

You will also need to take a look over the sequence in which the other System Center 2012 products have to be upgraded as this will play a major role in ensuring a successful upgrade of your environment. I recently posted about this product upgrade sequence and would recommend taking a look at it first here:

System Center 2012 Service Pack 1 Upgrade Sequencing

If you are happy enough with your product upgrade sequence and are now ready to start the SCOM 2012 RTM upgrade to Service Pack 1, then this blog post will detail the pre and post SP1 upgrade tasks that you need to consider. The focus for these tasks are mainly around  SCOM 2012 integrating with Virtual Machine Manager (VMM), Data Protection Manager (DPM), Orchestrator (SCORCH) and Service Manager (SM).

SCOM 2012 SP1 Pre-Upgrade Sequence Tasks

1. If configured and it exists, remove the VMM-to-Operations Manager Integration Pack. (This will disable monitoring of your VMM environment temporarily).
2. Remove the System Center 2012 RTM version of the Operations Manager console from all VMM and Orchestrator servers.
3. On the computer hosting the Orchestrator Deployment Manager, uninstall the IP for System Center 2012 – Operations Manager.
4. Follow my other blog posts on SCOM 2012 - Installing Service Pack 1 RTM to upgrade the Operations Manager components

SCOM 2012 SP1 Post-Upgrade Sequence Tasks

1. On the computer hosting the Orchestrator Deployment Manager, install the IP for System Center 2012 – Operations Manager.
2. Install the System Center 2012 SP1 version of the Operations Manager console on Orchestrator and VMM.
3. Re-establish connectivity between System Center 2012 – Virtual Machine Manager (VMM) and System Center 2012 – Operations Manager SP1.
4. Register the Operations Manager SP1 integration packs on System Center 2012 - Orchestrator SP1.
5. Make sure that the Configuration Manager agent continues to function.
6. Make sure that the management pack continues to function with App Controller.

Confirm Integrated Connections

Make sure that the following connections with VMM continue to function:

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

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

• Connectors (2)
• Management pack
• Agentless monitoring

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

• Management pack
• Central Console Server components

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

• Management pack
• Integration Pack (Operations Manger console (SDK) connection required for IP)

If you've followed all of the above tasks and ensure that SP1 has been deployed to each System Center 2012 product in the correct sequence, then you should be good to go with your new deployments!