SCOM 2007 R2 Inside Disable and Override functions

The purpose of this article is to focus on SCOM 2007 R2’s ability to disable or override objects in SCOM.  With that said, rules will be used as an example.

There is a concept known as noise. This is produced when an action such as a rule runs and sends the data it has collected to SCOM for processing.

So, every once in a while, you may be tasked to modify or disable a rule. This can sound like a formidable task until you realize that the functionality to perform these tasks are built into SCOM.

You can disable a rule, re-enable it and change the rule’s settings. There are four options for each action and offer the same functionality for each primary action.

DISABLE FUNCTIONS:

·         For all objects of Class: Windows Server 2008 Operating System

·         For a  Group

·         For a specific object of Class:  Windows Server 2008 Operating System

·         For all objects of another Class.

OVERRIDE FUNCTIONS:

·         For all objects of Class: Windows Server 2008 Operating System

·         For a  Group

·         For a specific object of Class:  Windows Server 2008 Operating System

·         For all objects of another Class.

Okay, so what is an object? Simply put the object is the target of the Class being discovered. It could be a role, a group, or the computer.

In the case of the first option for both disable and override, it is all the objects the class targets.  Meaning every machine where the class is being discovered will be affected.

In the case of the second, the group of computers would be affected.

In the case of the third option for both disable and override, it is a single machine the class targets.

The last implies that another ManagementPack may have a similar rule.  That is, a rule that needs to be disabled or overridden because the intention here is to shut all rules that perform the same function off.