Getting Started

  • Article

This section describes the actions you should take before you import the management pack, steps you should take after you import the management pack, and information about customizations.

Before you import the management pack

Before you import the BranchCache Management Pack, note the following limitations of the management pack:

  • The BranchCache Management Pack does not support agentless monitoring

  • The BranchCache Management Pack does not support monitoring any BITS-related functionality using BranchCache

Before you import the BranchCache Management Pack, take the following actions:

  • The BranchCache Management Pack requires the Windows Server Operating System Management Pack (version 6.0.6579.0 or above). Import this management pack first before importing the BranchCache Management Pack

  • The Agent Proxy setting in the Security setting on the Agent Properties must be checked (enabled) to enable the hierarchical discovery of the branch offices using hosted cache mode and branch offices using distributed cache mode. This step is necessary for the monitored BranchCache system to show up in the BranchCache Diagram view. If this is not set before the BranchCache application is discovered, please change the setting and restart the OpsMgr Health Service manually, or wait until the next discovery cycle.

Files in this management pack

  1. Microsoft.Windows.BranchCache.MP (version 6.1.7600.0)

  2. Microsoft.Windows.BranchCache.Reports.MP (version 6.1.7600.0)

  3. OM2007_MP_BranchCache.doc

  4. EULA.RTF

How to import the BranchCache Management Pack

For instructions about importing a management pack, see How to Import a Management Pack in Operations Manager 2007. After the BranchCache Management Pack is imported, create a new management pack in which you store overrides and other customizations.

Create a new management pack for customizations

Most vendor 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 2007 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 pre-production environments to your production environment. For example, instead of exporting the default management pack that contains customizations from multiple management packs, you can export just the management pack that contains customizations of a single management pack.

  • You can 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 in Operations Manager 2007.