SCOM 2012 RC – Side-by-Side Migration Phase 2 – Setting up a new Management Group

Important Note! 2012 RC is not supported in a production environment unless you are in the Microsoft TAP program for Operations Manager.
This blog post is to be considered an experience report, and not an official guideline.

Phase 1 – http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/92025/Default.aspx

 

Table of contents
– Rant
– Preparations
– Installing the first Management Server
– Fixing Post-Setup Errors
– Installing the second Management Server

Rant
There already are tons of blog posts about setting up 2012 RC, this blog post is therefore quite redundant and will give you no new insight, however – it is part of my side-by-side Migration and thus I want to cover it.
The interesting part will be in the upcoming blog posts when I go for migrating the Management Packs, especially Overrides, as well as user roles.

After setup is finished, my environment looks like this:
image

 

Preparations
Reading the documentations:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27974

What I really need:
Release Notes
Supported Configurations
Deployment Guide – Distributed Deployment of Operations Manager

 

Installing the first Management Server
Documentation can be found here: http://technet.microsoft.com/en-us/library/hh301922.aspx

Installing the Prerequisites:
.net 4.0
Report Viewer (Console Requirement)

The documentation also suggests to install .net 3.5 SP1 and some hotfix for it – this is not applicable in case you have .net 4.0 installed already.

The 2012 RC Setup is pretty straight forward and, at least according to my experience so far, way more solid than the 2007 R2 Setup.

Launch Setup as Admin and hit Install
image

Select the components, I want the Management Server and Console component.
image
image

The Prerequisites Checker often gives a warning that a reboot is pending.
Now, after you reboot and try to run setup again you will most likely get this Error here pointing out that the WinRM service is not running.
image

Reason: It’s startup type is “Automatic (Delayed)”
Solution: Wait some time or start the service manually, then run the Prerequisite Checker again.
image

Specify a Management Group name.
image

Carefully read the license agreement.
image

Provide the configuration for the Operations DB.
image

Provide the configuration for the Data Warehouse DB.
image

Configure your Service Accounts.
image
image
image

And then, watch the Setup proceeding.
image

If everything worked out fine, this is what it looks like
image

 

Fixing Post-Setup Errors
Your best source of information in this regard is the Operations Manager log.
After setup is finished you will find a few errors – the ones I worry about are the recurring ones.

Event Id 26371 – The System Center Data Access service failed to register an SPN
The server I used once was a Management Server, therefore the SPN entries for the HealthService were already created. But since in 2012 every Management Server runs the Config and SDK Service too, you need to add the SPNs for them as well.

The error should tell you which ones are missing. In my case:
A domain admin needs to add MSOMSdkSvc/SERVERNAME and MSOMSdkSvc/SERVERNAME.domain.com to the servicePrincipalName of CN=SERVERNAME,OU=Management Server,DC=DOMAIN,DC=com

In case the entries are missing, we create them with the following command:
setspn –A MSOMSdkSvc/SERVERNAME SERVERNAME
setspn –A MSOMSdkSvc/SERVERNAME.domain.com SERVERNAME

And verify that the entries were created properly
setspn –l SERVERNAME

Afterwards I recommend restarting the SDK service to see if it still throws errors.

 

Aside from that I had some errors and warnings which seemed like setup noise
Event Id 27000 – The System Center Data Access service client threw an unknown exception while processing a type cache refresh notification.
Event Id 6001 – Performance data from the Health Service could not be collected since required registry keys could not be read
Event Id 21028 – Performance data from the OpsMgr connector could not be collected since required registry keys could not be read
Event Id 10103 – Several performance rules can’t find their counters. Common warning.
Event Id 34509 – OperationsManager Data Warehouse DB doesn’t contain objects that are subject for creation by APM data set

Any Alerts?
None on my side.

 

Setting up a secondary Management Server
Documentation can be found here: http://technet.microsoft.com/en-us/library/hh284673.aspx

Installing the Prerequisites:
.net 4.0
Report Viewer (Console Requirement)

 

The 2012 RC Setup is pretty straight forward and, at least according to my experience so far, way more solid than the 2007 R2 Setup.

Hit Install
image

Select the components, I want the Management Server and Console component.
image
image
image

And we are going to add the MS to an existing Management Group.
image

Provide the Operations DB information
image

The rest of the setup is the same as for the first MS.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.