SCOM
Disabling SQL Express Instance Discoveries
Our SQL Team doesn’t want to manage SQL Express installations. Typically SQL Express is used for Dev/Test and they don’t want to be alerted on these databases.
Turns out there is a nice override to disable discovery of these in the “SQL 200x Database Engines (Windows Server)” discovery.
All you need to do is find the SQL 200x Database Engines (Windows Server) discovery. Create an override “For all objects of type: Windows Server”
Then choose the Parameter Name “Exclude List” and type in “SQLEXPRESS”.
[…] https://www.scom2k7.com/disabling-sql-express-instance-discoveries/ […]
Any other way to distinguish SQL Server versions besides the instance name? Seems MS has decided that it’s a bug for the Instance Name for SQL Server 2008 Express Edition to be SQLEXPRESS.
[…] https://www.scom2k7.com/disabling-sql-express-instance-discoveries/ […]
[…] Several other good blogs posts have also covered this, but I keep seeing this issue at customer sites, so I want to re-blog and to give it some more coverage. Tim McFadden has a good post on the topic here: https://www.scom2k7.com/disabling-sql-express-instance-discoveries/ […]
[…] As described by Tim McFadden here https://www.scom2k7.com//disabling-sql-express-instance-discoveries/ […]
How to disable express SQL servers from agnostic MP using override ?