Answered by:
discovery of ALL servers related to MP in the environment

Question
-
can I isolate the discovery to just just the specific group of servers I want? Example: if I want to discover only specific SQL servers, but I have the SCOM agent installed on ALL SQL servers in the environment, can I just target my group only?
Or say OS or IIS MPs, if I have the agent installed on all IIS servers, but want to target just a specific group, can I do this with Run As Profiles? Want to make sure.
Tnx
Wednesday, January 16, 2013 7:59 PM
Answers
-
In theory yes. In practice it is more difficult.
Once you import the SQL MP, it will automatically discover all SQL servers. You can't stop it because you can't override the discovery until the discovery exists (has been imported) and once it is imported it is already discoverying.
You can undiscover objects .. what you can do is look at the target of the discovery (it isn't always a server object). Then create a group of those objects. Then override the discovery. This isn't enough in itself ... you then need to run a different PShell command depending on the version of SCOM:
SCOM 2007 R2 - http://blogs.technet.com/b/jonathanalmquist/archive/2008/09/14/remove-disabledmonitoringobject.aspx
SCOM 2012 - http://om2012.wordpress.com/2011/12/21/om-12-rc-powershell-cmdlet-remove-scomdisabledclassinstance/
It is also possible to create an overrides MP that disables all the discoveries and import that at the same time as you import the base monitoring MP. Alexey did post something like this for SQL some time ago.
Cheers
Graham
Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/- Marked as answer by Graham Davies Thursday, January 17, 2013 6:38 AM
Wednesday, January 16, 2013 8:57 PM
All replies
-
In theory yes. In practice it is more difficult.
Once you import the SQL MP, it will automatically discover all SQL servers. You can't stop it because you can't override the discovery until the discovery exists (has been imported) and once it is imported it is already discoverying.
You can undiscover objects .. what you can do is look at the target of the discovery (it isn't always a server object). Then create a group of those objects. Then override the discovery. This isn't enough in itself ... you then need to run a different PShell command depending on the version of SCOM:
SCOM 2007 R2 - http://blogs.technet.com/b/jonathanalmquist/archive/2008/09/14/remove-disabledmonitoringobject.aspx
SCOM 2012 - http://om2012.wordpress.com/2011/12/21/om-12-rc-powershell-cmdlet-remove-scomdisabledclassinstance/
It is also possible to create an overrides MP that disables all the discoveries and import that at the same time as you import the base monitoring MP. Alexey did post something like this for SQL some time ago.
Cheers
Graham
Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/- Marked as answer by Graham Davies Thursday, January 17, 2013 6:38 AM
Wednesday, January 16, 2013 8:57 PM -
Thanks for your speedy reply Graham, and yes it makes sense.
Wednesday, January 16, 2013 10:07 PM -
No problem - feel free to re-open the thread if you have any more questions around this.
Regards
Graham
Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/Thursday, January 17, 2013 6:39 AM