Best practices for configuring overrides in Operations Manager
This article contains a list of best practices to use when you configure overrides in Microsoft System Center Operations Manager.
Original product version: System Center 2012 Operations Manager
Original KB number: 943239
Store overrides in a separate management pack
For each management pack that you use in Operations Manager, create an additional management pack in which to store overrides. For example, after you import the Active Directory management pack, create an Active Directory Override management pack. Then, store any overrides that you configure for the Active Directory management pack objects in the Active Directory Override management pack.
Don't use the Disable command to disable a management pack object
When you want to disable a management pack object, don't use the Disable the ObjectName command on the Overrides menu. Instead, select the Override option to override the object. Then, follow these steps:
- In the Override Properties dialog box, select the Override check box that corresponds to the Enabled parameter.
- In the Override Setting column, select False.
- In the Select destination management pack list, select the appropriate management pack in which to store the override.
This method lets you specify a management pack in which to create the override.
Set an overridden parameter for every rule and monitor that uses the parameter
When you override a parameter, make sure that the parameter is configured for each rule that uses the parameter and for each monitor that uses the parameter. There may be more than one rule or monitor that uses the particular parameter.
For example, the following rules and monitors use the Intersite Expected Max Latency parameter:
- AD Replication Monitoring
- AD Replication Performance Collection - Metric Replication Latency
- AD Replication Performance Collection - Metric Replication Latency: Maximum
- AD Replication Performance Collection - Metric Replication Latency: Minimum
- AD Replication Performance Collection - Metric Replication Latency: Average
Configure overrides for groups instead of for specific instances
We recommend that you configure an override for a group instead of using an override to target a specific instance. Configuring overrides for groups allows for better manageability than what is available if you target a specific instance. To configure an override for a group, follow these steps:
Create a group that has the following characteristics:
- Create the group in the appropriate overrides management pack.
- Configure the group to contain the particular instances or formulas that target the instances that you want to override.
For example, create a group that's named AD DC 2003 Role. Then, manually put instances of the AD Domain Controller 2003 Role objects into the AD DC 2003 Role group.
Select the For a group command on the submenu of the Overrides menu.
In the Select Object dialog box that appears, select the new group that you created.
Test overrides in a test environment
You can test overrides in one environment and then apply the overrides to another environment. For example, you can test an override in a test environment and then implement the override in a production environment. To do this, follow these steps:
- Create the test groups in the appropriate override management pack.
- Add the appropriate instances from the test environment to the test groups. You can explicitly specify the instances. Or, you can use a formula to specify the instances.
- Perform sufficient testing to validate the override.
- Export the particular management pack from the test environment.
- Import the override management pack into the production environment.
- Populate the groups that are contained in the override management pack by using the appropriate instances from the production environment.