SCOM 2012 - Installing Service Pack 1 RTM (Part 2)

In Part 1 of this three part series, I detailed the pre-upgrade tasks that need to be carried out to prepare your SCOM/OpsMgr 2012 environment for upgrading to Service Pack 1 (SP1). This post will walk through the upgrade deployment process of a Distributed SCOM 2012 Management Group.

Some important notes taken from the 'OM12SP1_Upgrade' guide before we continue though:

Note 1
Between the time that you upgrade the management servers and upgrade the agents, you might experience Application Platform Monitoring (APM)-related event log entries on the agent-managed servers. These event log entries might occur on agent-managed servers that are not APM-enabled. These event log entries will be resolved when you complete the upgrade of the agents. You might have to restart the health service after the agent is upgraded in order to clear the events

Note 2
When upgrading multiple management servers in a distributed management group, sequence the upgrades in a manner that best suits your business needs. Upgrade all management servers in the distributed management group as soon as possible to verify that your upgraded environment is healthy

Upgrade Management Servers

To begin the SP1 upgrade, logon to your SCOM 2012 Management Server with an administrative account and then browse to the location that you have mounted or extracted your SCOM 2012 SP1 RTM media to. Now right-mouse click on 'Setup' and choose the 'Run As Administrator' option as shown below

From the Operations Manager Service Pack 1 splash screen, choose the Install option to begin.

The Operations Manager Setup dialog box will open up and will present you with a list of all the components that are installed on the server to be upgraded. Click Next to continue

Read the license agreement and terms, click on the Radio box to agree and then click Next

Confirm the installation location and then click Next to begin the prerequisite check. You can check out all of the prerequisites needed for SCOM 2012 SP1 from here.

If all prerequisites have been met, you will be presented with the screen below. If some are missing, then you will be prompted to install these at this point. When ready, click Next to continue

In the Configuration dialog box, enter the username and password of your System Center Configuration Service and System Center Data Access Service account (aka SDK account) as shown below, then click Next

Now confirm that you are happy with all of your settings and then click Upgrade to start the installation process.

After a short while, the upgrade should complete successfully and you will be presented with the screen below. Click Close to finish this part of the SP1 upgrade process.

When you've updated your Management Server, browse to the SCOM 2012 installation folder - normally located at C:\Program Files\System Center Operations Manager 2012\Server. Once here, add a column view for 'File Version' and then sort the column by file version and locate the 'HealthService.dll' file. This should now be upgraded with a new version level of 7.0.9538 as the screen below shows

If you don't see the product version updated as above to your files, then your server hasn't updated properly and you will need to revisit the installation to see if you've missed something. If the files have upgraded successfully and there were no issues with your first management server upgrade, then you can repeat this process on any additional management servers in your distributed management group.

When you have upgraded your management servers to SP1, you need to be aware that there are still a number of steps to work through before you are finished.

Upgrade ACS Collectors

If you have deployed Audit Collection Services (ACS) in your environment, then the next step in this process is to upgrade any ACS collectors to SP1. As I haven't (yet) deployed ACS 2012 into my lab, I'll point you to the following TechNet article to work through to get ACS upgraded:

http://technet.microsoft.com/en-us/library/jj899846.aspx


Upgrade Gateway Servers

Once you have upgraded your management servers and ACS collectors, you can then go ahead and perform the upgrade on your Gateway servers using the following steps:

To begin the SP1 upgrade, logon to your SCOM 2012 Gateway Server with an account that has the Operations Manager Administrators role permission in your SCOM 2012 management group and then browse to the location that you have mounted or extracted your SCOM 2012 SP1 RTM media to. Now right-mouse click on 'Setup' and choose the 'Run As Administrator' option as shown below

From the Operations Manager Service Pack 1 splash screen, and in the Optional Installations area, choose the Gateway management server option as shown below

On the Welcome to the System Center 2012 - Operations Manager Gateway Upgrade Wizard dialog box, click Next.

From the next screen, click the Upgrade button to begin the upgrade process.

Once the Gateway upgrade has completed successfully, click Finish to close the window.

Upgrade Consoles

When you have upgraded your management servers, ACS and Gateway servers, you then need to upgrade any stand-alone SCOM 2012 consoles that you are using in your environment.

Note: You do not need to carry out this step on any management servers that have already been upgraded using the earlier steps in this post as the console on these servers will be automatically upgraded to SP1 as part of the management server upgrade.

Log on to the computer that hosts the stand-alone SCOM 2012 Operations console with an Operations Manager Administrators role account for your SCOM 2012 management group.

To begin the SP1 upgrade, logon to your SCOM 2012 Gateway Server with an account that has the Operations Manager Administrators role permission in your SCOM 2012 management group and then browse to the location that you have mounted or extracted your SCOM 2012 SP1 RTM media to. Now right-mouse click on 'Setup' and choose the 'Run As Administrator' option as shown below

From the Operations Manager Service Pack 1 splash screen, choose the Install option to begin.

The Operations Manager Setup dialog box will open up and will present you with a list of all the components that are installed on the server to be upgraded. Click Next to continue

On the Getting Started, Select installation location page, accept the default value of C:\Program Files\System Center 2012\Operations Manager, or type in a new location or browse to one. Then click Next.

Read the license agreement and terms, click on the Radio box to agree and then click Next

On the Prerequisites page, review and address any warnings or errors that are returned by the Prerequisites checker, and then click Verify Prerequisites Again to recheck the system.

If all prerequisites have been met, you will be presented with the screen below. If some are missing, then you will be prompted to install these at this point. When ready, click Next to continue

On the Configuration, Ready To Upgrade page, click Upgrade.

When the upgrade is finished, the Upgrade complete page appears. Click Close.

Note: You can verify the Operations Console upgrade has completed successfully by checking the following registry key (as always ensure you backup your registry before you work on it):
 
Browse to HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup.
If the value of the UIVersion entry is 9538 the Operations console was upgraded successfully

Conclusion Part 2

In this penultimate post, we have upgraded our SCOM 2012 management servers, ACS collectors and Gateway servers along with any stand-alone consoles in our environment. In Part 3 of this series we'll upgrade the agents, Web console and the Reporting role (if separate from the management server role). We will then finish off with any post-upgrade tasks that need to be carried out.