Creating Overrides in SCOM

As mentioned in the documentation for importing MPs, there's 2 kinds of MPs. Sealed and Unsealed. Examples of sealed MPs would be the majority of those available from Microsoft. Examples of unsealed MPs would be the MPs you make for a custom monitor. With an unsealed MP, you can get in there, root around, change things, etc. With a sealed MP, you cannot. The way to change the behavior of monitors and rules in sealed MPs are to create overrides. Overrides basically step in to tell OpsMgr “Look, I know what the Management Pack said but we're going to do it this way, kapeesh?”

You can start creating overrides in the Authoring section of the Operations Console by simply finding the monitor you wish to create overrides for, right-clicking, selecting “Overrides”, and then choosing what items you want the override applied to a group, objects of a specific class, specific objects of a class or objects of another class. For this example, I'm showing how to create an override for objects of the Application Data Source.

(NOTE: You can also create overrides from active alerts in the Monitoring section of the Operations Console. The process for creating the overrides are the same regardless of where you start from.)



You'll see that you can change several parameters such as the alert priority, whether the monitor generates an alert, whether the monitor autoresolves the alert, or even whether or not the alert is even enabled at all.



Once you tick the box to override a certain parameter, you can change the override value. Before you can apply the overrides, you'll have to save them to an MP. In my example, I've created an override to disable this monitor for all Application Data Source objects and saved them to my DPM 2012 SP1 overrides MP.



And that's it. You've just made an override in OpsMgr.

Comments

Popular posts from this blog

Installing CentOS 7 on a Raspberry Pi 3

Modifying the Zebra F-701 & F-402 pens

How to fix DPM Auto-Protection failures of SQL servers