Management Pack Documentation

I’ve always find it challenging to say the least to answer questions like “What does SCOM monitor on my servers”, “What can we monitor with SCOM”, “What is the disk free space thresholds being monitored”. I’ve investigate a HUGE amount of time in developing a solution that loads all the management pack contents into a SQL database. The end result of the work is below

mprulestop

mprules

 

Monitor details

monitorstop

Information available

1. Knowledgebase article as included in the sealed management packs

2. Event Ids, Source Name, Log Name of event collection rules

3. Perfmon information, as well as interval, direction, number of samples etc etc

The difference between my solution and that of MPWiki or event MPViewer is that all the monitor/rule/discovery configuration information, including the VBScripts,  the thresholds, event ids etc etc etc etc are all imported into my SQL database, with this information in a SQL database I extract the information using SSRS, all together in one report.

The next step will be to import the overrides for the different Rules and Monitors for all my clients and show like a deviation report from the standard setup per client.

I import all the .MP files using the SCOM SDK , this includes DataSources, Write Actions etc etc contained in the different management packs – One word “AWESOME”

More to come.

SCOM 2007 R2 and SCOM 2012 R2 console on same/single machine

During one of my clients migration from SCOM 2007 R2 to SCOM 2012 R2 there is a requirement from the users of both systems to have both consoles installed and working on a single workstation/laptop

Steps

1. First install the SCOM 2007 R2 console on the laptop using the normal setup methods.

2. Install the SCOM 2012 R2 console running the OMConsole setup package from either the i386 or AMD64 folders on the setup media.

3. When you  try to launch the SCOM 2012 R2 console most of the time you will get an exception error message, this is because the prerequisites for the console is not installed

4. Install the SQL 2012 CLR Types for either the 32 bit or 64 bit laptop

5. Install the reportview for SQL 2012 on the laptop

6. The SCOM 2012 R2 console will now succesfully open.

7. Close the console and update the shortcut of the SCOM 2012 R2 console icon and add /Server:<management server> in the target field.

Adding the /Server: allows the SCOM 2012 R2 console to directly connect to the SCOM 2012 R2 management servers

8. Launch the SCOM 2007 console, you will probably receive a incompatibility error message, click ok and then select/type in the RMS server name of the SCOM 2007 environment.

That’s it, now you can have both consoles running on a single workstation/server/laptop.

3