Upgrade Distributed Management Group to Operations Manager 2012 SP1


In this post I want to share my experience in upgrading a distributed Operations Manager 2012 environment with SP1.
I must say that installing SP1 isn’t something you must take lightly. The process will actually uninstall components and reinstall them. If at some point something fails it is possible you’re left without a component because it was previously uninstalled. A bit like the upgrade process 2007 R2 to 2012.

It is certainly recommended to read all technet resources covering this topic.
http://technet.microsoft.com/en-us/library/jj656651.aspx (Release Notes for Operations Manager in System Center 2012 SP1)
http://technet.microsoft.com/en-us/library/jj628203.aspx (Upgrade Sequencing for System Center 2012 SP1)
In an environment that includes two or more components of Microsoft System Center 2012, the order in which you upgrade those components to System Center 2012 Service Pack 1 (SP1) is very important.
http://technet.microsoft.com/en-us/library/jj899854.aspx (Upgrading System Center 2012 – Operations Manager to System Center 2012 SP1)Describes the steps to follow.

 

To start with Upgrading a Distributed Management Group 

Accomplish Pre-Upgrade Tasks (http://technet.microsoft.com/en-us/library/jj899852.aspx)

Upgrade Management Servers (each management server must be upgraded)
If you are running your webconsole on a Management Server, it might be better to upgrade this one last. I didn’t do this and my webconsole upgrade failed. The uninstall however did succeed 🙂 I installed the webconsole as my last step.

You can see that this setup includes SP1.
 
All installed components are detected and setup will upgrade them. No option to select the components you want to upgrade. This was on my first Management server. 
 
Just go and install the feature. Verify Prerequisites Again. 
 

 

 

As you can see my web console upgrade failed. Not a real problem, I’ll install it later on. 

Now what happens behind the scenes of this progress screen. You can follow all steps in the log files.
Go to %TEMP% and move back a few directories (AppData\Local\SCOM\LOGS) OpsMgrSetupWizard.log

In the step… Initial Configuration:
Previous server uninstall.log
OM12ConsoleUninstall.log
OM12WebConsoleUninstall.log

In the step… Operational Database Configuration
OpsMgrSetupWizard.log
Import management packs
Db stuff

In the step… Management Server
OMServer.log
Installation of the Management Server with SP1

In the step… Dataware House Configuration

OpsMgrSetupWizard.log
Import management packs
Db stuff

In the step… Operations Console
OMConsole.log
Installation of the Operations Console with SP1

In the step…Web console
Probably creation of the WebConsole.log?

Now upgrade your other Management Servers.
 

Open a console and check your MS version it should be 7.0.9538.0


Next step is Upgrade ACS (because the ACS server must be on same machine as a management server, we recommend you perform this step along with the upgrade of the management server on which ACS resides.).
I didn’t have ACS enabled.

Upgrade Gateway(s)

 

In the Optional Installations area, click Gateway management server



Click Upgrade and check the version in your scom console.

 

Upgrade Console(s)
Same thing here, just run your setup.exe.

Push Install to Agent(s) / Upgrading Manually Installed Agents
Yes all agents must be upgraded, but even SCOM 2012 agents report to your SCOM 2012 SP1. 😉

Upgrade Web Console

NOTE: When you upgrade the web console, any customizations that were made to the web.config file after the web console was installed will be reset. So make a copy of your file to be safe.
If you made changes after you set up your web console to either enable or disable Secure Sockets Layer (SSL), the SSL settings will be reset during upgrade. To resolve the issue, you must make changes to the registry key before you upgrade the web console. (http://technet.microsoft.com/en-us/library/jj899843.aspx)

After installing my webconsole i got an error:

After enabling the details of the error it turned out that a dll was missing in the web console bin directory. Another possible cuase could be this http://blogs.technet.com/b/kevinholman/archive/2013/01/11/opsmgr-2012-web-console-issue-immediately-after-upgrade-to-sp1.aspx

Upgrade Reporting Server
 

Accomplish Post-Upgrade Tasks
Re-enable the Notification Subscriptions.
Restart or Re-enable the Connector Services (if needed)
Re-enable Audit Collection Services (ACS) on agents that were upgraded
Verify That the Upgrade Was Successful

Hope this post is helpful to those who are planning the upgrade.

Samuel.

 
 

Advertisements

One Response to Upgrade Distributed Management Group to Operations Manager 2012 SP1

  1. C.Champlin says:

    This was a handy overview… Thanks! I had only one interesting problem. When my gateway server was updated, I had to use the MOMCertImport import tool again to install the certificate.

    Errors in the Operations Manager Event log were easy to recognize and point me to the problem with the cert. Event ID 20070, complaining about “agent is not authorized to communicate with the server” when it tried to connect to the managment servers.

    Thanks again for your summary of the SP1 Upgrade procedure!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s