In Operations Manager 2007, management pack files are XML files that can have either an .mp or an .xml extension and contain monitoring settings for applications and services. After a management pack is imported into an Operations Manager 2007 management server, it immediately begins monitoring objects based on default configurations and thresholds that are already set by the author of the management pack.
Management Pack Formats
The defined schema file for Operations Manager 2007 management packs is MPSchema.xsd. The .mp files are sealed management packs, and management pack files with the .xml extension are not. To learn more about sealed management packs, see Management Pack Formats.
|The AKM file format used by Operations Manager 2005 is not an accepted management pack file format in Operations Manager 2007. However,Microsoft Operations Manager 2005 AKM management packs can be converted to Operations Manager 2007 management packs. For more information about converting Microsoft Operations Manager 2005 management packs, see Management Pack Conversion.|
Management Pack Libraries and Dependencies
A selection of management packs are imported as part of the Operations Manager 2007 installation process. These management packs are referred to as "libraries," because they provide a foundation of object types on which many other management packs depend. If your management pack references other management packs, you must first import all referenced management packs before you can import your management pack.
Management packs are available in the System Center Management Pack Catalog. For information about downloading and importing management packs, see How to Import a Management Pack in Operations Manager 2007.
Management Pack Customizations
The default settings and thresholds contained in a management pack reflect the author's definition of a healthy state for the application, service, or hardware device that you are monitoring. These settings provide a starting point for administrators, who can then make customizations using overrides or by creating additional management pack elements such as rules and monitors.
Sealed management pack files are formatted so that you cannot make changes to them. This means that any customizations you create are not saved to the original management pack. Instead, customizations are saved, by default, to the Default Management Pack.
|As a best practice, you should create a separate management pack for each sealed management pack you want to customize, rather than saving your customized settings to the Default Management Pack. For more information, see Default Management Pack.|
By default, when a management pack is imported, the monitoring settings contained within the management pack are applied to all managed computers within the management group. If you customize the settings of a management pack, you can apply these customizations to other management groups. To do this, you must first export the customized settings to a management pack file (as described in How to Export Management Pack Customizations). This management pack is dependent on the original vendor's management pack and can be imported only to management groups that have the original vendor's management pack.
Management Pack Removal
The settings imported from a management pack file are saved to the Operations Manager database and can be accessed through the Operations console. When you no longer need these settings, you can delete the management pack file and all associated settings in Operations Manager 2007 by using the Delete action for that management pack.
TasksHow to Convert an Operations Manager 2005 Management Pack
How to Create a Management Pack in Operations Manager 2007
How to Seal a Management Pack
ConceptsAbout the Management Packs Node in Operations Manager 2007
Management Pack Conversion
Management Pack Formats
Other ResourcesHow To Work with Management Packs
Did you find this information useful? Please send your suggestions and comments about the documentation.