Management Pack Life Cycle

Each management pack should be accompanied by a management pack guide that is installed to the same folder as the management pack. A management pack guide contains instructions for installing and configuring the management pack, and information about the management pack, such as objects that the management pack discovers and how health rolls up. You can use this information to help you customize the management pack for your purposes. You should always review the management pack guide before you import the management pack.

A tool for reviewing the contents of a sealed management pack is the MPViewer, which can display the following contents of a management pack: rules, monitors, views, tasks, console tasks, and reports. MPViewer will also display the knowledge associated with the particular management pack item. You can install and use MPViewer on any computer on which the Operations Manager Operations console is installed. Search the MSDN Blogs at https://blogs.msdn.com/b/dmuscett/archive/2012/02/19/boris-s-tools-updated.aspx for the most recent version of MPViewer.

When you have a new management pack, you should import it to a pre-production environment. In Operations Manager, it is a best practice to have a production implementation that is used for monitoring your production applications and a pre-production implementation that has minimal interaction with the production environment. The pre-production management group is used for testing and tuning management pack functionality before the management pack is deployed in the production environment.

To accurately measure the data that a management pack gathers, you need to expose the agent to the demands of your production environment. The hardware of the management server in the pre-production environment should reflect the hardware that is in use in your production environment. Your pre-production management group should have the same management packs imported to the management server as the production management group. To test interoperability, your pre-production environment should also include the same types of server roles that are in your production environment, just on a smaller scale.

You can assign an Operations Manager agent to more than one management group, which is called multihoming. If you multihome a representative subset of agents in your production environment and your pre-production environment, the pre-production environment should give you much of the information you need to correctly tune the management pack. For more information on multihoming agents, see Configuring Agents.

You can use overrides to refine the settings of a monitoring object in Operations Manager, including monitors, rules, object discoveries, and attributes. You should create a management pack in which to save customizations that you make.

For more information about using overrides, see Tuning Monitoring by Using Targeting and Overrides. For more information about creating management packs in which to save customizations, see Best Practices for Change Control.

When you are satisfied with the performance and results of the management pack in the pre-production environment, you can deploy the management pack and its customizations in the production environment. The management pack in which you saved the customizations must be exported so that you can import it to other computers. For more information, see How to Export an Operations Manager Management Pack. The management pack that contains the overrides that you set is dependent on the original management pack and can be imported only to management groups that have the original management pack installed.

After a management pack has been deployed, you should periodically evaluate its performance and results in the production environment to ensure that it continues to meet business needs. The following list describes common events that might require changes to a management pack:

• Environmental changes, such as new hardware or a new operating system 

  When you are testing new hardware or a new operating system that you plan to add to your production environment, you should include existing management packs in your test plan to identify any additional tuning that might be necessary. For a new operating system, you might need to import new management packs specific to that operating system.

• Adding a new application to the production environment 

  A new application might require a new management pack or adjustments to existing management packs.

• Upgrading a version of an application 

  When organizations upgrade application versions, they usually either upgrade in stages, during which both versions of the application will exist in the network, or upgrade all installations of the application at one time. After testing the management packs with the new version and making any necessary adjustments, you should use the same approach for deploying the management packs that you use for deploying the upgrades. If both versions of the application will be in use at one time, you should install management packs appropriate for each version. If all installations of the application will be upgraded at one time, remove the management pack for the old version of the application and install the management pack for the new version.

• When a new or updated version of the management pack is available 

  You should use the pre-production environment to review and tune new or updated versions of a management pack.

• Policy changes 

  Ongoing changes in your business or organization might require adjustments to management packs to accomplish more monitoring or less monitoring.

The following are some best practices to follow when managing Operations Manager management packs:

• Maintain an archive of management pack versions to enable you to roll back changes when necessary. An efficient method for maintaining the archive is by using version control software, such as Microsoft Team Foundation Server or Windows SharePoint Services. Another method is to use a file share on the network with individual folders for each management pack version.

• When you set overrides for a management pack, save them to a 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. For more information, see Creating a Management Pack for Overrides.

• When a management pack is updated, update the corresponding _Overrides.xml file with the new version number. You must use an XML editor to update the version number of the _Overrides.xml file. If you make changes to an _Overrides.xml file but do not change the version attribute, you can import the file but the settings in the file will not be applied.

• Document the overrides that you make to management packs. When you set an override, add an explanation of the action you are taking and the reason for it to the description field by clicking Edit in the Details pane of the Override Properties dialog box. You may also want to maintain a spreadsheet or other form to document changes that you make to management packs.