Things NOT to do!

Things NOT to do when using SCOM 2007 R2

Below are 4 things which are commonly seen in SCOM environments which are not best practice.


The Default management pack that ships with OpsMgr 2007 is used to store very specific information for the management group.  It is a widely known best practice to NOT write any custom rules, monitors, groups, views, or overrides to this MP. If this is done it will create a dependency for this MP on any MP it references and therefore you won’t be able to delete those Management Packs . Always store overrides in a separate unsealed MP that you have created. Also if you create an override in the Default MP that is targeted at something every agent has (i.e. Windows Computer) every agent that has at least one instance of that type will request a new copy of the Default MP instead of just the targeted machines that you will use in your unsealed MP created for your customisations.


DO NOT use the agent repair function from the console if you are using AD Integration as this will remove the AD Integrated functionality from the monitored machine. If you are not using AD Integration then this is fine.

OVERRIDES:-Disable/Enable function

DO NOT use the Disable  command in the Overrides menu to create an override to disable monitors, rules, or object discoveries. This will automatically use the Default MP!

CLOSING ALERTS triggered by a Monitor

DO NOT close an alert in the console that has been triggered by a Monitor.

Suppose you have an Alert triggered by a Monitor. A Monitor is a like a traffic light (also referred to as a State Machine). When it is red (Critical), it can’t go red again. First it has to jump to green (Healthy) before it can turn red again. Even when the Alert triggered by the very same monitor has been closed. So next time – when a new issue arises which should trigger an Alert – that Monitor will not raise a new Alert since it is still in a Critical condition.

I know, there are many ‘self-healing’ monitors out there. But some aren’t. Or some monitors take time to go ‘green’ again.

Best practice is to use Health Explorer to reset the state of the  monitor to healthy before closing the alert.

This entry was posted in Misc Stuff. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s