This article explains a simple process to disable a specified set (SQL, IIS, OS, etc.) of monitoring from given MP on a given set of servers.

Microsoft and vendor-specific MP’s provide auto-discovery of an application using script or reg key or event id. Once an application is discovered, all enabled monitors and rules will be effective and thus generate alerts.

There may be a server where monitoring one of the applications is critical and other applications and monitoring are required. In this case, a SCOM admin can disable any non-critical rules and monitors for the given server to avoid unnecessary reporting. To do this you can follow this process:

Pre-configuration information required:

1)    Set of servers where application is to be disabled.

2)    Application which need to be disabled.

3)    Basic knowledge on seed authoring.

Process:  to disable SQL monitoring for a set of servers:

1)    Create a computer group and add requested SQL servers as static or dynamic objects.

Refer below link how to create a group.

https://technet.microsoft.com/en-in/library/hh298605.aspx

http://blogs.technet.com/b/kevinholman/archive/2009/06/10/creating-custom-dynamic-computer-groups-based-on-registry-keys-on-agents.aspx

2)    Go to authoring pan> Management pack objects > Object discoveries




3)    Click scope > type SQL in lookfor > click select all

5)    Most of the modern MP come with seed base discovery targeting broad set of objects class. Example for Windows Server application targets windows server class.

More information on seed base discovery is provided here.

If there is no seed class, you need to create a override for all discovery’s for application MP

For SQL MP identify seed class as below targeting windows server  



6)    Right-click seed discovery > select Override the Object Discovery > for a group > select group created above.

       

7)    Check override for Enable and set override value to false > click OK

8)    Open SCOM PowerShell command prompt on MS and run

Remove-SCOMDisabledClassInstance this command deletes class instances for which you previously disabled discovery. The cmdlet also deletes all relationships that involve these class instances.



Note:

         1) Running this command can cause significant activity in the operational database may take long time to complete.

         2) For any addition of new server to group need to run the command.