Export (0) Print
Expand All

Creating a Management Pack for Overrides

Updated: November 1, 2013

Applies To: System Center 2012 - Operations Manager, System Center 2012 R2 Operations Manager, System Center 2012 SP1 - Operations Manager

In System Center 2012 – Operations Manager, in a number of wizards and dialog boxes, you select a destination management pack in which to store the results. You can select any unsealed management pack file in your management group or create a new one.

Management packs can be sealed or unsealed. A sealed management pack cannot be modified directly. Any changes to the workflows in the sealed management pack, such as an override for a monitor, must be saved to an unsealed management pack. The unsealed management pack references the sealed management pack that it modifies.

The following illustration shows the unsealed management packs that are installed with Operations Manager.

Dropdown menu for selecting management pack

Never use the management packs that are installed with Operations Manager to save any settings that you change or elements that you create. When you have to select a destination management pack, always select a management pack that you create.

You select a destination management pack when you create an override or disable a rule, monitor, or object discovery. You also select a destination management pack when you create or configure the following elements:

  • A folder in the Monitoring workspace

  • A unit, aggregate, or dependency monitor

  • An attribute

  • A group

  • A rule

  • A task

  • A Run As profile

  • Monitoring by using a management pack template

  • Monitoring of a distributed application

  • Tracking of service level objectives

Saving Overrides

As a best practice, save all overrides for each sealed management pack to an unsealed management pack that is named ManagementPack_Override, where ManagementPack is the name of the sealed management pack to which the overrides apply. For example, overrides to the management pack Microsoft.InformationWorker.Office.XP.mp would be saved to Microsoft.InformationWorker.Office.XP_Overrides.xml.

When you want to remove a sealed management pack, you must first remove any other management packs that reference it. If the unsealed management packs that reference the sealed management pack also contain overrides or elements that apply to a different sealed management pack, you lose those overrides and elements when you remove the unsealed management pack.

In the following image, overrides for management packs 1, 2, and 3 are all saved to a single unsealed management pack. If you want to remove management pack 1, you first must remove the unsealed management pack. As you can see, you would also remove all overrides for management packs 2 and 3.

Overrides saved to single management pack

The recommended method is to create an unsealed management pack for each sealed management pack that you want to override, as shown in the following image. Removing management pack 1 and its unsealed management pack does not affect the other management packs.

Save overrides to respective management packs

How to Create a Management Pack for Overrides

You can create a management pack for overrides before you configure an override or as part of the override procedure.

To create a management pack

  • In the Administration workspace, in the navigation pane, right-click, and then click Create Management Pack.

    -or-

  • In the Override Properties dialog box for a rule or monitor, in the Select destination management pack section, click New.

See Also

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft