SCOM 2012 RC – Side-by-Side Migration Phase 3 – Installing sealed Management Packs

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.

Table of Contents
– Intro
– Listing sealed Management Packs and checking which ones are missing in the new environment
– Management Packs needing extra treatment
Installing Sealed Management Packs using the catalog
Installing Sealed Management Packs from disk
Installing the Exchange 2010 Management Pack
Installing the SharePoint 2010 Management Pack
– Installing the HP ProLiant/Blade 1.40 Management Packs

Intro
SCOM 2012 RC – Side-by-Side Migration Phase 1 – Preparations
SCOM 2012 RC – Side-by-Side Migration Phase 2 – Setting up a new Management Group
Getting all sealed Management Packs up and running first in my new environment ensures that I don’t run into missing Management Pack references later on.
I didn’t have much trouble here, except for me not liking it when there are strings attached to Management Packs, like the Correlation engine for Exchange or the Admin task and its config file for SharePoint. HP didn’t make me happy either since they are importing the Management Packs during setup instead of just giving me the files.

The scripts mentioned in this blog post are attached in a zip file.

 

Listing sealed Management Packs and checking which ones are missing in the new environment
Getting a list of all sealed Management Packs
I want to get a list of all sealed Management Packs including their version level. I then will process that list to check if all sealed Management Packs are installed in the 2012 environment with the same/higher version.
2007 R2 Shell – CreateMPList.ps1
$MPStrings = @()
$ManagementPacks = Get-ManagementPack | ?{$_.Sealed} | sort Name
$ManagementPacks | foreach-object { $MPString = $_.Name + “;” + $_.Version; write-host $MPString; $MPStrings += $MPString}
# And I want to export that list to a file
$MPList = New-Item -ItemType File -Path “C:\temp\mplist.txt”
Set-Content -Path $MPList -Value $MPStrings

 

Comparing the list with installed Management Packs in 2012
Now I copy the list over to my 2012 RC Server under c:\temp\mplist.txt
The script then gets each Management Pack in the list, checks if it is installed and if the version is the same or higher.
Management Packs listed red or yellow need to be installed/updated.
2012 RC Shell – VerifyMPList.ps1
write-host “—————————-“
write-host “Management Packs marked red are not installed.”
write-host “Management Packs marked blue are installed but have a higher version.”
write-host “Management Packs marked green are installed and have the same version.”
write-host “Management Packs marked yellow are installed but have a lower version.”
write-host “—————————-“

$MPStrings = Get-Content “C:\temp\mplist.txt”
$ManagementPacks = Get-SCOMManagementPack | ?{$_.Sealed} | sort Name

foreach ($MPString in $MPStrings)
{
   $InstalledMP = $ManagementPacks | where {$_.Name –eq $MPString.Split(“;”)[0]}
   if ($InstalledMP –eq $null) { write-host $MPString –backgroundColor “DarkRed” }
   else
   {
      $Version = new-object System.Version($MPString.Split(“;”)[1])
      if ($InstalledMP.Version –eq $Version) { write-host $MPString –backgroundcolor “DarkGreen” }
      elseif ($InstalledMP.Version –lt $Version) { write-host $MPString –backgroundcolor “DarkYellow” }
      else { write-host $MPString –backgroundcolor “DarkBlue” }
   }
}

Now I have a good overview on which Management Packs are missing
image

 

Management Packs needing extra treatment
In my environment I have some Management Packs that need extra treatment:
Exchange Server 2010 – has the correlation engine
Microsoft SharePoint Foundation – has some installation scripts
HP Management Packs – doesn’t give you the Management Packs directly

Installing Sealed Management Packs using the catalog
I first want to install the Management Packs that are available in the catalog as it’s quite convenient.

In the Operations Console: Administration\Management Packs\Import Management Pack…
image

Add –> Add from catalog …
image

Search for the appropriate Management Packs and add them
image

I might receive a warning pointing out that the MP has dependencies that aren’t installed but that they are available in the catalog.
image

Click on Resolve, a window pops up that lists the Management Packs that need to be additionally installed.
Click Resolve again.
image

And now we are ready to go:
image

Rinse and repeat until all Management Packs are installed that can be installed using the catalog.

 

Installing Sealed Management Packs from the disk
Some Management Packs might not be available in the catalog. They must be downloaded and installed separately.

In the Operations Console: Administration\Management Packs\Import Management Pack…
image

Add –> Add from disk …
image

Yes, I want to search the online catalog for dependencies
image

Locate and select the Management Pack(s)
image

Verify that all dependencies are available and hit Install
image

Rinse and repeat until all Management Packs are installed that can be installed from disk.

 

Installing the Exchange 2010 Management Pack
The Exchange 2010 Management Pack including documentation can be found here: http://www.microsoft.com/download/en/details.aspx?id=692

Top Level Steps:
– Run Exchange 2010 Management Pack setup on a Management Server
– Stop the Microsoft Exchange Monitoring Correlation service
– Import the Management Packs
– Change the Management Server in the config file
– Changing the Service Account
– Start the Microsoft Exchange Monitoring Correlation service

Setup
While the Exchange 2010 MP can be installed from the catalog, it doesn’t work unless you install the Correlation Engine that ships with it.

Download the Management Pack and run it on one of your 2012 Management Servers:
image
image

Once you click Extract it will install the Microsoft Exchange Monitoring Correlation service, and it will put the Management Packs to the path provided for Management Pack Folder.
The Correlation Engine will insert Errors in the Event Log pointing out that the Management Pack is missing.

Stop the Service
Stop the Microsoft Exchange Monitoring Correlation service, otherwise it will spam your Application log.

 

Importing the MP
In the Operations Console\Administration\Management Packs\Import Management Packs\Add from disk
Locate and select the Exchange Management Packs. Hit Install
Note: The security warning can be ignored. It’s the only Pack I’ve seen so far that gives me a warning.
image

 

Setting the RMS Emulator
I’m not perfectly sure how SDK Events are handled in 2012 but taking the secure route, I want to redirect the Correlation Engine to the RMS Emulator.
By default the Correlation Engine will connect to localhost – in case you installed the engine on the RMS Emulator, no need to make any changes.
UPDATE: I got confirmation from Microsoft that you have to make the correlation engine connect to the RMS Emulator!

What’s an RMS Emulator? Basically, there is no RMS in 2012, but for compatibility reasons one server can be defined as the RMS Emulator which you need for rules and monitors targeting the Root Management Server class.

Which server is the RMS Emulator? Usually the first Management Server in the Management Group, but let’s go back and double check.
2012 Shell:
Get-SCOMRMSEmulator

Note down the name:
image

By default the installation path of the service is C:\Program Files\Microsoft\Exchange Server\v14\Bin
In there, open the file Microsoft.Exchange.Monitoring.CorrelationEngine.exe.config with notepad or some other Text editor.

Change the value for OpsMgrRootManagementServer to the servername of your RMS Emulator.
image

Save & Close.

 

Setting the Service Account
The documentation for the Exchange MP doesn’t mention anything about the required User Role for the Correlation Engine. Apparently, the user seemingly needs to be part of the Operations Manager Administrators User Role.

On the server where you have the Correlation Engine installed, open Services.msc, locate the Microsoft Exchange Monitoring Correlation service and open its properties.
Switch to the Log On tab, change from Local System account to This account and enter the information.
image

Apply, OK.

 

Start the Service
Start the Microsoft Exchange Monitoring Correlation service.

Verify that the service functions properly by looking for events from MSExchangeMonitoringCorrelation
image

You might find a warning event from source Bid with Event Id 1:
C:\Program Files\Microsoft\Exchange Server\v14\Bin\Microsoft.Exchange.Monitoring.CorrelationEngine.exe
5364

Microsoft.EnterpriseManagement.OperationsManager, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

System.DllNotFoundException: Unable to load DLL ‘MOMBIDldr.dll’: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
   at Bid.internalInitialize()

Just copy the file from C:\Program Files\System Center Operations Manager 2012\Server to C:\Program Files\Microsoft\Exchange Server\v14\Bin
I tried it with the 2007 R2 assembly and with the 2012 RC assembly, both seem to work – at least it doesn’t throw any events anymore.

In the services.msc start the Microsoft Exchange Monitoring Correlation service.

Installing the SharePoint 2010 Products Management Pack
The SharePoint 2010 Products Management Pack including documentation can be found here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=4419
For 2012 you additionally need to download an additional Management Pack including an installation task that is compatible with 2012 from Connect: https://connect.microsoft.com/site799/Downloads/DownloadDetails.aspx?DownloadID=37367

Top Level Steps:
– Install Microsoft SharePoint Foundation 2010 Management Pack
– Import Management Packs
– Create a Service Account for the Discovery
– Adjust the config file
– Run the Admin task
– Adjust the account distribution list
– Wait for the discovery to run

 

Installing the Management Pack
Where to install the Management Pack? In SCOM 2007 R2 that answer would be easy – the task targets the group, therefore when you run it, it will run on the RMS. In 2012 however, the task still targets a group and it will run on any Management Server.

Download the setup package here and start it on a Management Server.

Run Setup
image

Don’t change the target folder, but set installation to “Everyone”
Note: It should install it in C:\Program Files (x86) as Management Servers all have to be x64. In case you choose to install the Management Pack somewhere else, adjust the folders accordingly.
Note: It’s uncertain to me if this option affects all users or just non-Admins but I tend to set it to Everyone to be on the safe side
image

Hit Install
image

Additionally download the 2012 compatibility pack here and unzip it to C:\Program Files (x86)\System Center Management Packs\Microsoft SharePoint 2010 Products OpsMgr 2007 MP en-us

 

Import the Management Packs
Operations Console\Administration\Management Packs\Import Management Pack

Add from disk, navigate to C:\Program Files (x86)\System Center Management Packs\Microsoft SharePoint 2010 Products OpsMgr 2007 MP en-us
Select all 3 Management Packs – Open – Install
image

Create a Service Account for the Discovery
#1 Creating the actual Account
I love it when they are so specific with documenting the permissions required for a certain account. The documentation points out that the account needs to be SharePoint Farm Administrator – fine. And it should be a “member of the Administrators group on the database server hosting the SharePoint farm databases”, also fine, “and access to all SharePoint databases”. What kind of access?

After some googling around I found a blog post by J.C. Hornbeck pointing out the same, and he also has a list on the required permissions – http://blogs.technet.com/b/operationsmgr/archive/2011/03/10/tips-on-using-the-sharepoint-2010-management-pack-for-opsmgr-2007.aspx

– SharePoint Farm Administrator
– Local Admin on the SharePoint Front End and Application servers
– Local Admin on the SQL Servers that host the SharePoint Databases
– DB Owner on the SharePoint Databases

#2 Creating the Account in SCOM
Operations Console\Administration\Accounts\Create Run As Account…
image
image

Type: Windows
Display Name: SharePoint Discovery/Monitoring Account
You can change the name to something else but you have to adjust the account name in the config file later on.
image

Provide the credentials
image

Change to More Secure and click Create.
Note: If you select More secure you have to adjust the distribution list manually later on, the admin task doesn’t do that.
image

 

Adjust the config file
On the server where you have installed the SharePoint MP, navigate to C:\Program Files (x86)\System Center Management Packs\Microsoft SharePoint 2010 Products OpsMgr 2007 MP en-us
Open the SharePointMP.config file with notepad or some other text editor.

We are interested in this section here:
SharePoint Discovery/Monitoring Account” Type=”Agent”>
  SERVERNAME” />

#1 Account
In case you created the RunAs account with a different name than suggested by the documentation you have to edit the “Association Account” value to the name of your account.

#2 Machine Name
Here you can either create a list of server names or you work with regular expressions. Assuming we have a naming convention where our SharePoint servers all have a substring MOSS in their name we could use a regular expression:
Tool to check regular expressions: http://regexpal.com/
. = any character
* = preceding expression can occur zero or more times
() = a group
| = or

Finished Expression = .*(moss|MOSS).*
And my config looks like this:
SharePoint Discovery/Monitoring Account” Type=”Agent”>
 

Once done, save and close the file.

 

Run the Admin Task
Important Note: The task targets a group, this means that any Management Server might catch the task. Therefore the config file has to be available on all Management Servers the directory you provide in Working Directory

In the Operations Console\Monitoring\Sharepoint 2010 Products\Administration
Select the Microsoft Sharepoint 2010 Farm Group and launch the task “Configure Sharepoint Management Pack (SCOM 2012)”
Note: The one without the (SCOM 2012) is the one written for 2007, it won’t work on 2012.

image

Click Override and change the Working Directory to: C:\Program Files (x86)\System Center Management Packs\Microsoft SharePoint 2010 Products OpsMgr 2007 MP en-us
Note: That’s the default directory of the installation

 

Adjust the account distribution list
In case you configured your RunAs Account to be More Secure, you have to manually add all the SharePoint Servers to its distribution list.
In the Operations Console\Administration\Accounts – Open the properties for Sharepoint Discovery/Monitoring Account, switch to Distribution tab.

Click Add…
image

Search and add your Servers, click OK.
image

 

Wait for the discovery to run
Afterwards, wait for the discoveries to run, this can take several hours.

In case you run into trouble, consult the troubleshooting section of the official guideline.

 

Installing the HP ProLiant and Blade 1.40 Management Packs
I actually feared that this might not work not work as HP wrapped an installer around the Management Packs that then directly imports them instead of just giving you the MP files.
But, it worked just fine – you have to run the Setup from a Management Server though.

I’m not interested in the tools and console tasks that ships with it though.

Top Level Steps:
Download the Management Packs here  and unzip them to your disk drive.
– Launch the ProLiant Setup
– Launch the Blade Setup

 

Launch the ProLiant Setup
image
image
image

I don’t want to install the console extensions, therefore I pick custom.
image

Just the Packs and the Documents please.
image

If you are unsure, consult your HP Insight Manager Administrator.
image

Hit Install.
image

Wait for the Import to be finished.
image
image

 

Launch the Blade Setup
image
image

Custom.
image

Just the Packs and the Documents.
image
image
image
image

And that’s it.

0 thoughts on “SCOM 2012 RC – Side-by-Side Migration Phase 3 – Installing sealed Management Packs

  1. Mario78

    How did you get the HP Blade MP to work without the HP Blade Enclosure Monitor Service? Or did you install it on another Server?
    My problem is that it relies on the Windows SNMP Trap Service running and SCOM 2012 brings it’s own SNMP Listener and therefor disables the Windows SNMP Service.

  2. Andreas Zuckerhut Post author

    Hi, sorry for not covering that but I only install the Management Packs, the HP Agent/Service installation and management is done by a different team and they just told me they don’t use that service.
    Either way, the discovery of the Monitor Service runs against all Windows Computers, therefore you don’t have to install it on a Management Server, it can be any agent-managed machine.

  3. Andreas Zuckerhut Post author

    Update: Microsoft confirmed that you have to make the correlation engine connect to the RMS Emulator
    Update: Regarding he Blade Enclosure Monitor Server, it can be installed on any Agent-Managed Computer

Leave a Reply

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