The following post will help SCOM admin to setup:
Overrides play a key role in SCOM for fine-tuning monitoring to reduce alerts, change thresholds and monitor behavior.
Refer to link for how to create bulk overrides: http://social.technet.microsoft.com/wiki/contents/articles/30714.scom-2012-bulk-override-creation-for-monitors-and-rules-using-powershell.aspx
SCOM provides multiple options to create overrides below.
Refer to below links for more information on SCOM override creation process:
Most of the time we change threshold, monitoring/rule alert property for a set of servers by creating a group. The group is populated by the explicit membership.
Refer to below links for how to create a group:
Issues with Explicit Group Membership is when you create a group with explicit membership. Discovery rule will populate a group with GUID of an object but not with its name. This GUID is dynamically generated by SCOM server and this is very specific to a management group.
The overrides will not be effective when it is moved to different MG as object GUID is not present in new MG.
Delete explicit group population and create dynamic memberships with appropriate property names.
If you want to apply overrides to a monitor targeted to “windows server” class, follow below steps.
Note: You can use OR group if multiple objects.
Once overrides MP is updated with dynamic group population, you can deploy override MP to any MG. These overrides will be effective as it is based on Name but not on GUID.
You can use below script to pull a list of objects into a group from any group with display names.
Import-Module oprtationsmanager$Group=Get-SCOMGroup -DisplayName “<< GRoupName>>”$Group.GetRelatedMonitoringObjects()
Import-Module oprtationsmanager
$Group=Get-SCOMGroup -DisplayName “<<
GRoupName
>>”
$Group.GetRelatedMonitoringObjects()