Before You Import the Management Pack
Before deploying the Microsoft® Configuration Manager 2007 Management Pack, review the Microsoft Operations Manager 2007 Deployment Guide on the Operations Manager 2007 Web page (http://go.microsoft.com/fwlink/?LinkID=83259). This section provides additional instructions for deploying Operations Manager Management Packs.
To deploy the Configuration Manager 2007 Management Pack, you must complete the following processes:
- Design your monitoring environment based upon
operational and organizational needs. Consider performance and
scale factors. It is recommended that all primary site servers and
default management points should be monitored.
- Deploy the Operations Manager 2007 agent
to all Configuration Manager 2007 server component computers
that will be monitored. An incremental approach is best.
- Verify that all agents are healthy.
- Configure Operations Manager 2007 agents
for Configuration Manager 2007 Providers and Configuration
Manager 2007 Primary Site servers so that they can proxy for
other computers.
- Import the Configuration Manager 2007
Management Pack into an Operations Manager 2007 configuration
group.
- Complete the recommended test and pilot test
tasks.
- Complete the recommended tuning tasks.
How to Import the Configuration Manager 2007 Management Pack
Before a Management Pack can be used to monitor Configuration Manager 2007 installations, the Management Pack must be imported into Operations Manager 2007. For instructions on how to do this, see "How to Import a Management Pack in Operations Manager 2007" on the Operations Manager Web page (http://go.microsoft.com/fwlink/?LinkID=98348).
Create a New Management Pack for Customizations
Most Management Packs are sealed so that you cannot change any of the original settings in the Management Pack file. However, you can create customizations, such as overrides or new monitoring objects, and save them to a different Management Pack. By default, Operations Manager saves all customizations to the Default Management Pack. As a best practice, you should instead create a separate Management Pack for each sealed Management Pack you want to customize.
Creating a new Management Pack for storing overrides has the following advantages:
- It simplifies the process of exporting
customizations that were created in your test and preproduction
environments to your production environment. For example, instead
of exporting a Default Management Pack that contains customizations
from multiple Management Packs, you can export just the Management
Pack that contains the customizations of a single Management
Pack.
- It allows you to delete the original
Management Pack without first needing to delete the Default
Management Pack. A Management Pack that contains customizations is
dependent on the original Management Pack. This dependency requires
you to delete the Management Pack with customizations before you
can delete the original Management Pack. If all of your
customizations are saved to the Default Management Pack, you must
delete the Default Management Pack before you can delete an
original Management Pack.
- It is easier to track and update
customizations to individual Management Packs.
For more information about sealed and unsealed Management Packs, see Management Pack Formats. For more information about Management Pack customizations and the Default Management Pack, see About Management Packs.
To create a new management pack for customizations-
Open the Operations Console, and then click the Administration button.
-
Right-click Management Packs, and then click Create New Management Pack.
-
Enter a name, for example, ConfigMgr 2007 MP Customizations, and then click Next.
-
Click Create.