Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

OpsMgr 2012: Override enhancements

OpsMgr 2012: Override enhancements

  • Comments 1
  • Likes

A new change in OM 2012 is how overrides are handled from the console.  In the past – if you ever got an alert, decided you wanted to disable that rule, you could NOT just choose to “disable” the rule from the context menu.  The reason being, is that this would have placed your override in the Default Management Pack.  This is bad, as it is a best practice not to save anything to your Default MP.

 

In OpsMgr 2012, you can now use this menu option.  What happens, is you will now be prompted to choose a Management Pack to save your overrides to.  In the below example, I am disabling a monitor for SQL Server Service Pack Compliance:

 

image

 

Note what now happens.  OpsMgr automatically creates an override to disable the monitor – but we now are *forced* to choose a Management Pack to save the override to.  We will no longer automatically, or accidentally save them to the default MP.

image

 

image

 

This will greatly help keep the Default MP from getting overrides placed there accidentally, and make it easier to use the “Disable” function to quickly tune a MP to your requirements.

Comments
  • Excellent!  We should be able to manage things directly from the console views.  Looking forward to more with 2012.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs