Hi

I have read blog about how to remove monitoring objects. http://blogs.technet.com/b/jonathanalmquist/archive/2008/09/14/remove-disabledmonitoringobject.aspx

But In my case, it does not seems to be applicable.

I have a monitoring case where 2 SQL engines are on the same box. If I disable the discovery on Target SQL Installation seed class, then Remove-SCOMDisabledClassInstance command removes both of the database engines. I want to stop monitoring for only one instance not on both.

Kindly 

You can use the method explained on this blog to not monitor a specific SQL instance : http://blogs.technet.com/b/kevinholman/archive/2010/02/13/stop-monitoring-sql-express-and-windows-internal-database.aspx

• Proposed as answer by Graham DaviesMicrosoft employee, Moderator 19 hours 40 minutes ago

You can use the method explained on this blog to not monitor a specific SQL instance : http://blogs.technet.com/b/kevinholman/archive/2010/02/13/stop-monitoring-sql-express-and-windows-internal-database.aspx

• Proposed as answer by Graham DaviesMicrosoft employee, Moderator Monday, September 07, 2015 11:28 AM

You can use the method explained on this blog to not monitor a specific SQL instance : http://blogs.technet.com/b/kevinholman/archive/2010/02/13/stop-monitoring-sql-express-and-windows-internal-database.aspx

• Proposed as answer by Graham DaviesMicrosoft employee, Moderator Monday, September 07, 2015 11:28 AM

Hi CyrAz,

Thanks for the input, that solved my problem.

Exclude list parameter helped me, but there can be other scenario where a single discovery returning multiple object of same class(Like multiple logical disks object). In that case, disabling discovery and running remove-scomDisabledClassInstance command will remove all the logical disk present on that machine. how to remove only D drive whereas C & E drive still under monitoring?

In this case, you can create a group of disks that you don't want to monitor and just override the monitor.

Regards

Graham

Given how a discovery work, if there is no "Exclude" parameter specifically designed for this purpose, I don't think this is possible.

I guess you would have to let these instances be discovered and then disable the monitoring for them..