A customer requested to have a capability to get an overview of the effective configured settings for rules / monitors and its values for Windows Computer objects. For some administrators browsing through the SCOM console is just too time consuming and / or too complicated. There are not many ways of providing a simple solution to satisfy this requirement, unless you know PowerShell – of course.
In PowerShell we have an interesting cmdlet called Export-SCOMEffectiveMonitoringConfiguration. This cmdlet let’s you calculate and export the current effective configuration for a monitored object. This sounds great, but there is a not so cool downside. The export file is a CSV separated by the “|” (pipe) delimiter which makes it a bit hard to handle it with certain cmdlets in PowerShell. As far I have seen, there is no way of changing the default delimiter nor the behavior of the cmdlet.
If you follow the syntax and export the CSV file from Export-SCOMEffectiveMonitoringConfiguration, the file looks like this JBOFHTRD (Just a Bunch OF Hard To Read Data)…
Of course you could use Excel to import the CSV and run some filter on the table, which is not my preferred choice of handling this kind of data. There must be a sexier way of doing it 🙂 . Ok, let’s code…
The first thing we do is, declaring two parameters like target computer name and the SCOM management server we would like to query. Then declare the path and array variable and if the path does not exist we will create the folder…
Next, we are going to connect to the SCOM management group, get the instance of the System.Computer class, which we specified as parameter. Since we have the computer instance, we need to fire off the Export-SCOMEffectiveMonitoringConfiguration cmdlet and retrieve the configuration for all objects of the specified instance and save it into a file…
Now, the core part of the script gets all the content from the previous generated file, then it iterates through each line, splitting the lines by the “|” (pipe) delimiter and adds the values to a PowerShell custom object. After each iteration, the object will be added to the defined array…
Note: The source configuration CSV output file contains about 90 columns, which are mostly empty. If you need to add more columns, because you have a lot of configured values for your monitor or rule, just extend the object with more properties. The next property would be like this…
Finally we are dumping the array to the Grid View….
In action, it looks like this…
Then, the magic moment happens. All the effective configuration for the server object server03.bigfirm.com will be shown in an easy, readable format…
The cool part just starts here. You are able to filter each column e.g. I just want to see which monitors or rules are enabled, click Add Criteria and select the column Enabled contains True…
You are even capable of searching any term and it will filter the view accordingly…
That’s the real way of getting the effective configuration for a monitored computer. The requirements for the script are simple, you just need to have PowerShell and the OperationsManager PowerShell module installed on your client.
There is famous song from Frank Sinatra “I did it my (PowerShell) way”…
Download the script from TechNet Gallery
Hello Stefan, thanks for posting very useful
Can you tell me please does his cmdlet (I am still on SCOM 2007 R2) also get the values once any overrides have been taken into account? as this was always a bit of an issue
for example I have a monitor that when created has a default alert severity of warning. The MP in deployed and at some future date this monitor is overridden for one of the computer and the severity is set to critical. If I run the above will it show the value for the above as warning (e.g. the setting from the original MP configuration or will it show critical to reflect that is the live setting for this on the agent?
I would be grateful if you could let me know the answer this this please 🙂
Jo
Hi Jo
It will show the effective setting of critical for the monitor. Be aware that the script uses a cmdlet for SCOM 2012. You will also see if e.g. a monitor was disabled in the “original” MP and it was enabled at a later point in time, the Setting will show up as enabled.
Cheers,
Stefan
Hi Stefan,
Thanks for the script, this is a great post :))
There is custom configuration for rule/monitor the name doesn’t look friendly, for example “MomUIGeneratedRule6d9a17bc90ef492…”. Is that possible to grab the friendly name of the rule/monitor?
Numerous problems with Export-SCOMEffectiveMonitoringConfiguration. First were the sql errors due to duplicate writeactions in the cluster MP.
http://scom.dnfconsulting.net/export-scomeffecticemonitoringconfiguration/
that took me many days to find and i ended up fixing it by excluding certain IDs for win 2008 since we use 2008 R2 and i know this woul dnot hurt my data. If i just added top1 as recommended the exported config would be incomplete. Now that its all working w/out error I just get incomplete data from Export-SCOMEffectiveMonitoringConfiguration. For example i run that off a group of web servers. One of them will produce a file half the size as the rest whihc is missing most all monitors. If i check manually via the console gui, neither have failed workflows and they both show same things monitored.
Thanks for posting Stefan, very helpful 🙂
JR, the cmdlet is buggy and I have good reason to believe that it will be fixed with the next release/update. Until then, try this: http://blogs.msdn.com/b/tysonpaul/archive/2014/07/24/scom-powershell-export-scomeffectivemonitoringconfiguration-cmdlet-doesn-t-output-complete-data.aspx
~Tyson
Hi Tyson
Thanks for your update and sharing! I know that there are / were cases where this cmdlet doesn’t work right and I really really hope Microsoft will manage to fix this.
Cheers,
Stefan
Thanks Stefan for this amazing post 🙂 I would like to know how to run this script on a multiple agents or group of servers simultaneously. Is that possible? Please reply.
Yes.
http://blogs.msdn.com/b/tysonpaul/archive/2014/07/24/scom-powershell-export-scomeffectivemonitoringconfiguration-cmdlet-doesn-t-output-complete-data.aspx
-Tyson
Thanks for this post. Could you please suggest if it is possible to list the ‘management packs’ for hosts ? I would like to see how many management packs downloaded on each host.
Hi
I am not sure what you mean, could you give an example?
cheers,
Stefan
sorry..I’m re-phrasing the question. In health explorer, I can see the list of monitors and rules linked to the host, along with that the management pack name as well (in monitor/rule propeties). Using powershell query, Can I get the management pack list for an agent which are actually applied on the host ?
Satheesh,
First, you aren’t seeing any Rules in Health Explorer, only Monitors.
Second, I think this may be what you are looking for (thanks to Stefan for aiding in this http://stefanroth.net/2014/02/13/scom-2012-effective-configuration-viewer-the-powershell-way/ ):
http://blogs.msdn.com/b/tysonpaul/archive/2014/07/24/scom-powershell-export-scomeffectivemonitoringconfiguration-cmdlet-doesn-t-output-complete-data.aspx
Hi
Well, the MP’s are downloaded to the machine / agent itself, you can find the directory here \server01c$Program FilesMicrosoft Monitoring AgentAgentHealth Service StateManagement Packs (http://stefanroth.net/2014/01/03/scom-2012-r2-powershell-to-determine-agent-required-disk-space/).
Cheers,
Stefan
Hi..thanks for the answer. When I checked the list of management packs ‘effective’ on a host, it is very few in number. (Checked it from Healthexplorer->Monitor->Properties->MP name). List for a sample server is given below.
————————————————————–
operation Manager APM infrasturture
Windows server 2012 operating system(monitoring)
Microsoft audit collection service
Microsoft System Center Advisor Internal
system center core monitoring
Exchange server 2010
Network Management – core monitoring
Microsoft Forefront Endpoint Protection Application
system center core monitoring
Windows core library
Windows server operating system library
Health Library
—————————————————————–
But when I check the list of MPs downloaded on the host (from \serverc$Program FilesMicrosoft Monitoring AgentAgentHealth Service StateManagement Packs) list is huge and I can’t find many in health explorer as effective monitoring configuration.
‘Export-SCOMEffectiveMonitoringConfiguration’ cmdlet shows the list of monitors/rules and details along with description, but management pack name corresponding to these monitors/ruls is missing in report.
So what I’m looking here is to get the list of ‘effective’ management pack names which are configured on hosts.Since this information is needed for some analysis on 100s of servers, checking if any powershell queries are available. Suggestions in this matter will be helpful. Many thanks.
Hi
You might wanna try this http://stefanroth.net/2015/06/19/scom-2012-what-workflows-mps-and-objects-run-on-a-scom-agent/
Cheers,
Stefan
Hi Stefan,
Really glad to see your new article on this with helpful suggestions. Thanks a ton for the effort.
Regards,
Satheesh
Hi Santheesh
No Problem :).
Cheers,
Stefan
Satheesh,
Not all management packs contain monitors and/or rules so the list of MPs won’t be directly proportional to the number of monitors that you might see in Health Explorer. So… keep that in mind.
Hi Stefan,
This is a great script, I haven’t found anything else that will show me all the rules, monitors AND overrides applied to a computer in a single view.
I have the same problem as Amy though – I have a lot of custom rules and monitors that are displayed as “MomUIGeneratedRule6d9a17bc90ef492…”. Is it possible to display the friendly name of the rule/monitor? I know it’s possible with Get-SCOMRule | where {$_.Name -eq “MomUIGeneratedRule6d9a17bc90ef492…}
First I want to say, Great script Stefan, as always! I learn something new every time I visit your site.
Lee,
I modified Stefan’s script a bit to add the display name of the rules/monitors. The lines I added are all commented below
$count = 0 # Add a counter so we can get a header column for Display Name
ForEach ($line in $lines) {
ForEach ($field in $line)
{
$Values = $field.Split(‘|’)
if ($Values[7] -eq ‘Rule’) { # This is a rule, not a monitor, so we need to run Get-ScomRule to find the DisplayName
if ($Values[2] -ne $null) # Sometimes we hit a row that doesn’t have a rule name (like the headers) – skip it
{
$ObjectDisplayName = (Get-SCOMRule -Name $Values[2]).DisplayName # Use the Get-SCOMRule cmdlet, pass the name from the line above, and return the .DisplayName property
}
} else { # This is a monitor, do the needful
if ($Values[2] -ne $null) # Sometimes we hit a row that doesn’t have a monitor name (like the headers) – skip it
{
$ObjectDisplayName = (Get-SCOMMonitor -Name $Values[2]).DisplayName # Use the Get-SCOMMonitor cmdlet, pass the name from the line above, and return the .DisplayName property
}
}
$object = New-Object –TypeName PSObject
$object | Add-Member –MemberType NoteProperty –Name Class –Value $Values[0].Replace(‘”‘,”)
$object | Add-Member –MemberType NoteProperty –Name InstanceName –Value $Values[1]
$object | Add-Member –MemberType NoteProperty –Name RuleMonitor –Value $Values[2]
if ($count -eq 0) # $count is 0, so this must be the header row – add a ‘Display Name’ header column
{
$object | Add-Member –MemberType NoteProperty –Name DisplayName –Value ‘Display Name’
} else {
if ($ObjectDisplayName -ne $null) { # If the query from lines 45 or 50 returned a blank, we’ll bypass the next command
$object | Add-Member –MemberType NoteProperty –Name DisplayName –Value $ObjectDisplayName # We got a display name! Add it to the object, so it can go to the array
}
}
$object | Add-Member –MemberType NoteProperty –Name Enabled –Value $Values[3]
$object | Add-Member –MemberType NoteProperty –Name GeneratesAlert –Value $Values[4]
$object | Add-Member –MemberType NoteProperty –Name AlertSeverity –Value $Values[5]
$object | Add-Member –MemberType NoteProperty –Name AlertPriority –Value $Values[6]
$object | Add-Member –MemberType NoteProperty –Name AlertType –Value $Values[7]
$object | Add-Member –MemberType NoteProperty –Name AlertDescription –Value $Values[8]
$object | Add-Member –MemberType NoteProperty –Name Overriden –Value $Values[9]
$object | Add-Member –MemberType NoteProperty –Name Parameter1 –Value $Values[10]
$object | Add-Member –MemberType NoteProperty –Name DefaultValue1 –Value $Values[11]
$object | Add-Member –MemberType NoteProperty –Name EffectiveValue1 –Value $Values[12]
$object | Add-Member –MemberType NoteProperty –Name Parameter2 –Value $Values[13]
$object | Add-Member –MemberType NoteProperty –Name DefaultValue2 –Value $Values[14]
$object | Add-Member –MemberType NoteProperty –Name EffectiveValue2 –Value $Values[15]
$object | Add-Member –MemberType NoteProperty –Name Parameter3 –Value $Values[16]
$object | Add-Member –MemberType NoteProperty –Name DefaultValue3 –Value $Values[17]
$object | Add-Member –MemberType NoteProperty –Name EffectiveValue3 –Value $Values[18]
$object | Add-Member –MemberType NoteProperty –Name Parameter4 –Value $Values[19]
$object | Add-Member –MemberType NoteProperty –Name DefaultValue4 –Value $Values[20]
$object | Add-Member –MemberType NoteProperty –Name EffectiveValue4 –Value $Values[21]
$array.Add($object)
$count++
}
}
Hope this helps. If anyone has any suggestions for improvement, please speak up.
Also, Stefan, have you tested this with an ArrayList for the $array variable? I’m curious if there could be performance gains.
Cheers,
Ron
The script doesn’t give all the filesystems which are getting monitored, it just displays the first FS when we pull the effective configuration..any suggestions on how can we fix this..
Thanks,
Kushagra
@Kushagra,
https://blogs.msdn.microsoft.com/tysonpaul/2014/07/24/scom-powershell-export-scomeffectivemonitoringconfiguration-cmdlet-doesnt-output-complete-data/
computer:
scom:
what need to fill here, i’m getting error while executing. kindly suggest
Hi
Thanks for the script. Is it still worth trying in 2019/2022 environment? Second, does it cover the overrides too?