Hi, We have sql installed on Exchange boxes (SQL EXPRESS) and we dont want it to be monitored now. but the server`s are already discovered and monitored. I override the SQL discovery for excluding "SQL EXPRESS" and also for all "Exchange 2007 computer group" and the discovery interval to 300 seconds. I beleive it should undiscovered and should not list the exchange boxes under SQL group in monitoring view. But the servers are still showing up in server state of sql server. I also used "effective configuration viewer" tool to verify, It still shows that the sql is still moniotred in the exchange server. Any help on this is much appreciated. Thanks, SaravThanks, Sarav

Hi Sarav. You need to start up your Operations Manager Shell and run the command Remove-DisabledMonitoringObject http://www.opsmode.com/2010/10/server-still-monitored-after-a-discovery-has-been-disabled/mats.w | www.opsmode.com

Hi Sarav How did you override the SQL discovery for excluding SQL Express? Was it this way? http://blogs.technet.com/b/kevinholman/archive/2010/02/13/stop-monitoring-sql-express-and-windows-internal-database.aspx If you use the exclude option on the discovery then they should be removed automatically. If you have set an override (enable = false) on the discovery then you will need to use the cmdlet that Mats mentions. Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Thanks, It works now..but the issue is before the exclude discovery runs am getting alert from the original management packs... Is there anyway to stop the alert being fired before all the discvoery complete? After the discovery complete for excluding the alert goes off. We have created auto ticketing so the tickets are generated before SCOM auto closes the alert. Thanks, Sarav

Hi, Any help on this is much appreciated. Thanks, SaravThanks, Sarav

Hi Sarav How have you gone about disabling the discovery? Did you use the method that Mat suggested or the one that I suggested? Could you be specific about exactly what is happening - are you still installing agents onto exchange servers that have SQL Express installed and it is the new servers that are causing the false alert? Or is the existing Exchange servers with SQL Express installed that are firing alerts. Cheers Graham View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Yes I overridden the discovrey rule to the exchange group and execute the remove-disabled monitoring object command. , This is happening for only for new agent installation.Thanks, Sarav

Hi If you use this solution then the object won't be discovered in the first place and hence shouldn't fire off the alert: http://blogs.technet.com/b/kevinholman/archive/2010/02/13/stop-monitoring-sql-express-and-windows-internal-database.aspx Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/