SCOM Trick 41 – the Default MP

SCOM, SCOM Tricks Send feedback »

One of the questions often asked is what the default management pack is for. Especially when you tell somebody they should not save overrides and stuff in there, while it is always right there as the first selected management pack to save something to! Quite logical that this confuses people and that is likely that there will be overrides/groups and other items in there after some time. One of the problems is that with every override you create more and more dependencies on the default mp, so in order to delete any mp you will probably run into SCOM complaining about the dependencies. Also it creates a lot of clutter and you will not have an overview anymore of what is where.

The first tip would be to rename the default management pack. In the SCOM console go to Administration pane and find the Management Packs entry in the left of the screen. Next find the Default Management Pack. Double click it to get the properties. In the Name field you can change the name there. Usually I add something like (DO NOT SAVE HERE!!) either before or after the name. At least it is a visual reminder you/they should not save stuff there.

For sure it will happen that stuff gets saved there so here is an article from Kevin Holman explaining more about this MP and how to clean it again:

Also a very nice one is a custom mp from Jonathan Almquist that monitors the default mp for changes:

Keep your default mp clean.

Back to the SCOM Tricks general list

SCOM Trick 40 – SNMP

SCOM, SCOM Tricks Send feedback »

As this is a short article I cannot touch upon everything there is to say about SNMP as it is a broad subject. However it is something you almost certainly will touch upon. I prefer agent based monitoring whenever possible, but there are devices which do not run a SCOM agent of course, so you would need another way of monitoring them. In most cases network attached devices are able to talk SNMP. In many cases you can connect to them with an SNMP read string and check if they are up. I have touched upon this already in trick 30 for network devices and trick 31 server hardware. However there is a lot more. For instance storage, tape libraries, UPS, operating systems, server hardware and many more.

So if you want to get cracking with this I would suggest first taking a look at a few posts in the community about the subject to get up to speed.

Pete Zerger SNMP Series:

Francois Dufour on SNMP trap monitoring:

SNMP probe based monitors David Allen

SNMP monitors and numeric data workaround by Raphael Burri

Watch Kristopher Bash as he builds the xSNMP mp for Cisco:

I am sure these will bring you up to speed. Happy monitoring!

Back to the SCOM Tricks general list

SCOM Trick 39 – RMS reconnect to SQL feature (post CU4)

SCOM, SCOM Tricks Send feedback »

In the past when the SQL server for SCOM had been down for whatever reason (installing updates, downtime and so on) the RMS would have trouble re-connecting to the database and thus having trouble to start running again. Actually I have only seen this happen in the larger SCOM setups and with a bit more downtime than just a cluster failover on the SQL side. But when it does happen you might want to use an optional feature that was introduced in SCOM 2007 R2 CU4.

Kevin Holman explains the feature and how to enable it, but the procedure is pasted below for your convenience:

To enable this feature - On the RMS – create two new registry entries:
Under the “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\DAL” key, create two new DWORD values, as below:
DALInitiateClearPool should be set to Decimal value “1” to enable it.
DALInitiateClearPoolSeconds should be set to Decimal value “60” to represent 60 second retry interval.

You can refer to Kevin’s post for the whole story:

Back to the SCOM Tricks general list

SCOM Trick 38 – Gateway

SCOM, SCOM Tricks Send feedback »

Using a SCOM gateway server (SCOM GW) can be very helpful. Mostly a reason to use a gateway is because you want to monitor a domain which has no Kerberos trust with the domain where your management servers are located. In this case you can just setup a certificate trust between the SCOM MS and the SCOM GW and have the gateway talk to the other agents in his domain. Of course there are some other advantages as well, such as compression of data between the gateway and the management server, you only need to open 1 firewall port for one server if you find the need to cross firewalls, you can have the gateway add a site name which you can use to separate agents and alerts coming from that location. I think Satya Vel had a very good post about the ten reasons to use a gateway at

All information on how to setup a gateway is in the documentation as mentioned in trick 1.

Marnix Wolf has a very nice article on when to use a dedicated gateway server

There is a nice article on how to use multiple gateways by Anders Bengtsson:

And yet another good article from Marnix about some of the advantages of a gateway:

Back to the SCOM Tricks general list

SCOM Trick 37 – Backup RMS encryption key

SCOM, SCOM Tricks Send feedback »

In SCOM 2007 the root management server (RMS) uses an encryption key to be able to decrypt secure data in the SCOM database. When you first install SCOM at the end of the step to install the first management server (RMS) you will get the option to backup the encryption key. This is a good start to make a backup of it and you will provide a password. But there is also a way to create a backup of the encryption key after the installation. In most cases I would use the same password as the SDK/config/dataaccess account is using. Just something that works for me as I can remember that I use this most of the times and most of the times I know the SDK account. You will need to have this backup of the encryption key when you need to restore your RMS or when you need to promote another management server to RMS. One more reason why it is a good idea to also store the key backup on another location (for instance on the second management server), as you will use it when your RMS is dead most of the times.

So how to backup the key:

Of course it is also nice to list how to restore it:

In a few cases we have seen somebody get an error like this:
could not load file or assembly ', Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.
In that case copy securestoragebackup.exe to the program files directory for scom where lives and run backup from there from an elevated command prompt.

Back to the SCOM Tricks general list

SCOM Trick 36 – Capacity planning

SCOM, SCOM Tricks Send feedback »

When starting out with a new SCOM deployment or sometimes after running some time you might find yourself asking for an estimation of what resources are needed to run SCOM.

To start with I would suggest using the SCOM design guide:

Next check out the Operations Manager 2007 R2 sizing helper:

These will help in giving an idea of what you will be up against for SCOM deployments of different sizes. I would suggest always using some margin with this. Reason is because you might find yourself adding more and more to the monitoring. For instance cross platform monitoring, network monitoring, hardware and storage and so on can give a performance hit on the SCOM servers and increase the size of the databases.

Back to the SCOM Tricks general list

SCOM Trick 35 – SCOM Licensing

SCOM, SCOM Tricks Send feedback »

One of the things that is most often unclear with Microsoft software is licensing. There are people who have studied it for years. So, what options are there for SCOM and System Center? I hope these will point you in the right direction.

Here is one page from Microsoft with some resources:

Malcolm Bullock on System Center licensing:

Graham Davies using the back of a napkin for the SCOM licenses:

Posts from Ian Blyth:

Back to the SCOM Tricks general list

SCOM Trick 34 – Move SCOM databases

SCOM, SCOM Tricks 1 feedback »

At some point you might run into the need to move one of the databases related to SCOM to another server. In case you do you can start your migration plan with reading some of these posts.

Let’s start with the TechNet pages related to the subject:
How to move the operations manager database:

How to move the operationsmanagerdw database:

How to move the operationsmanagerac database:

How to move the report server:

Now for some posts from our favorite Microsoft PFE’s (although Kevin is now a TSP):

Back to the SCOM Tricks general list

SCOM Trick 33 – Service Level Dashboard

SCOM, SCOM Tricks Send feedback »

One of the solution accelerators Microsoft released is the Service Level Dashboard. What it does is create a dashboard on top of Windows SharePoint Services which shows service level objectives you have set.

There are a few very good resources out there and I will link them here.

The TechNet page:

Posts by Jonathan Almquist:

A post by Marnix Wolf:

Back to the SCOM Tricks general list

SCOM Trick 32 – Monitor Oracle

SCOM, SCOM Tricks Send feedback »

After monitoring operating systems there might also be a wish to monitor Oracle. Of course Oracle has a bit more to offer than a database server. I will list a few links and products here that monitor the database and some that monitor other components.

First of all I want to mention the first Oracle that I was asked to monitor. It turned out to be Oracle Linux operating system. We found that this OS actually made itself known as RedHat Linux and that the SCOM discovery wizard also saw it that way. So we can pick it up as a Linux server with cross plat monitoring.

Next here are a few links to monitoring solutions for Oracle:

NiCE has a great management pack for monitoring Oracle NiCE website. They have been building on this pack continually. Feel free to request information or a trial.

Bridgeways has a management pack for Oracle Database:
There is also a beta version for Weblogic there. However it has been in beta for some time now, not sure when they are going to release it.

ComTrade has an Oracle Siebel management pack:

Quest has a management pack for Oracle Database:
And a connector to link Oracle Enterprise Manager to SCOM

Monitor an Oracle database with a SCOM OleDB watcher

Kristopher Bash has also been working on a management pack:

Back to the SCOM Tricks general list

Contact / Help. ©2016 by Bob Cornelissen. blog software.
Design & icons by N.Design Studio. Skin by Tender Feelings / Evo Factory.