SCOM: Export Effective Monitoring Configuration with PowerShell

The script accepts a group name, computer name, or object ID. It "recurses" all related monitoring objects, outputs each configuration set to a separate file, then merges all of the files together to create one complete .CSV. Finally, it outputs the complete dataset to GridView.

4 Star
755 times
Add to favorites
System Center
E-mail Twitter Digg Facebook
  • The script able to export the alert name?
    2 Posts | Last post December 01, 2018
    • The script able to export the alert name too?
    • Hi,
         No. However, there is another cmdlet in the SCOMHelper PowerShell module that you can use to export detailed alert information to a report (html or csv) which contains the workflow names (monitor and rule). I'll look into adding the alert name (for applicable workflows) to the export. Thanks for bringing this to my attention. 
  • Linux effective configuration
    2 Posts | Last post December 01, 2018
    • Hi, when I try run it against linux (Red Hat 7) server, I received error message:
      Unable to get class instance for DisplayName: []
      At line:1 char:1
      + .\ExportEffectiveMonitoringConfiguration.ps1
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
          + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,ExportEffectiveMonitoringConfiguration
    • Hi, I would encourage you to use the SCOMHelper PowerShell module instead. This script has been baked into the module and will be maintained there instead. That being said, the best way to get "nix" computer info (as of today) is to use the -SCOMGroupName parameter and specify a group which contains one or more nix computer objects. At some point I will update the cmdlet in the module to accept both Windows and Nix computer objects with the -ComputerName parameter. (As of today -ComputerName is only effective for Windows computer objects. SCOMHelper v1.1)