Viewing Effective Configuration of the monitoring objects in a SCOM environment has always been a bit of a challenge.
There is tools available including powershell commands to perform the extract for you, there is even a SCOM dashboard view that will show you the effective configuration of the object/class.
I’ve created a .Net application front-end where the user can select the Classes in his SCOM environment, the utility then displays all the objects for the chosen class.
The user can then select the specific objects for which the Effective Configuration export is needed.
Screen shot of the application
Explanation of some the fields
“File Name: “ This is the directory where the csv files for each object in the class or objects selected will be placed
“Waiting Time: “ This is the milliseconds the utility will wait between batches.
“Simultaneous Process: “ This is the number of objects targeted in parallel to export their effective configuration.
15 Simultaneous process will be kicked off and the utility will then wait for 300,000 seconds (5 minutes), after the 5 minutes the utility will launch additional process to get to 15 total again.
When you run the utility you can change the values above for your specific environment, and I would advise you do that, each thread uses considerable memory, CPU resources on the server where you run the utility. Each thread is also a separate connection to your SCOM environment.
Example of the output csv file
Expansion of the configuration items for the D: disk in above screenshot for the M: Logical Disk Free Space monitor (R: is for SCOM rules and M: is for SCOM monitors)
Directory contents for all the csv files:
The file name of the csv file is the SCOM object FullName with underscores “_” replacing all other characters for example “;” and “”.
If you choose an object (For example and object of “Microsoft.Windows.Server.Computer” class) that has related/child objects, the utility exports all related/child objects and corresponding monitors and rules as well.
Screenshot showing the tree-like structure of the output csv file.
So there you have it, a csv file per object containing the effective configuration for the rules and monitors.
I’ve timed this utility on a huge SCOM environment exporting 4432 “Microsoft.Windows.Server.Computer” class objects, the utility ran for 11 Hours and 25 minutes.