How to Import and Configure the Operations Manager Management Pack

更新日期: 2010年8月

適用於: Operations Manager 2007

The Operations Manager Management Pack is automatically installed when you install System Center Operations Manager. To import updated versions of the management pack, download the management pack from the System Center Operations Manager 2007 Catalog.

For instructions on importing a management pack, see How to Import a Management Pack in Operations Manager 2007.

Configuring the Operations Manager Management Pack

After you install the System Center Operations Manager, configure the Operations Manager Management Pack as follows:

  • Create a Run As account with administrator access on the target computers.

  • Add a Run As account to the Automatic Agent Management Account Run As profile to enable automatic agent recovery.

  • Create a new management pack for Customizations

  • Enable recovery for the Health Service Heartbeat Failure monitor.

  • Add a Run As account to the Validate Alert Subscription Account Run As profile.

  • Enable the Operational Database Watchers Group to Management Group Availability Health Rollup.

  • Set the configuration service to automatically restart.

  • Make sure that the action account on the root management server is a member of the Operations Manager Administrators Group.

  • The following sections explain how to make these changes.

Create a Run As Account for Use with Run As Profiles

If you did not create a Run As account with administrator access when you installed Operations Manager, you must do so before you can set the Automatic Agent Management Account Run As profile and the Validate Alert Subscription Account Run As profile.

To create a Run As Account

  1. Log on to the computer by using an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 Management Group.

  2. In the Operations console, on the Go menu, click Administration.

  3. In the navigation pane, expand Administration, expand Security, right-click Run As Accounts, and then click CreateRunAsAccount.

  4. In the Create Run As Account Wizard, on the Introduction page, click Next.

  5. On the General page, do the following:

    1. Select Windows in the RunAsAccounttype list.

    2. Type a display name in the Display Name text box.

    3. As an option, type a description in the Description text box.

    4. Click Next.

  6. On the Account page, type a user name, password, and then select the domain for the account that you want to make a member of this Run As account.

  7. Click Create.

Add a Run As Account to the Automatic Agent Management Account Run As Profile

Before Operations Manager can automatically recover agents, you must add a Run As account to the Automatic Agent Management Account Run As profile. The Run As account must have administrator access on the target computers.

To add a Run As Account to the Run As profile for the Automatic Agent Management Account

  1. In the Operations console, on the Go menu, click Administration.

  2. In the navigation pane, expand Administration, expand Security, and then click Run As Profiles.

  3. Double-click Automatic Agent Management Account, and then click the Run As Accounts tab.

  4. Click New, and then in the Run As Account drop-down menu, click a Run As account that has administrative rights on the target computers.

  5. Under Matching Computers, click the management server that the agent reports to, and then click OK.

note附註
To identify the management server that an agent reports to, in the navigation pane, expand Administration, expand Device Management, click Agent Managed, and then locate the primary management server for the agent.

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 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 a 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.

  • 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.

To Create a New Management Pack for Customizations

  1. Open the Operations console, and then click the Administration button.

  2. Right-click Management Packs, and then click Create New Management Pack.

  3. Enter a name (for example, ADMP Customizations), and then click Next.

  4. Click Create.

Enable Recovery for the Health Service Heartbeat Failure Monitor

The overrides that automatically recover the Health Service Heartbeat Failure monitor for agents are disabled by default. To automatically recover the monitor when it falters, you must set overrides for enabling, restarting, and reinstalling the Health Service.

To enable automatic recovery

  1. Open the Operations console, and then in the navigation pane, click the Authoring button.

  2. Under Authoring, expand Management Pack Objects, and then click Monitors.

  3. Under Monitors, expand Health Service Watcher (Agent), expand Entity Health, and then expand Availability.

  4. Right-click Health Service Heartbeat Failure, click Properties, and then click the Overrides tab.

  5. In the list, under Recovery, click Enable and Restart Health Service, click Override, and then click For all objects of type: Health Service Watcher (Agent).

  6. Under Override-controlled parameters, in the Override column, select the check box next to the Enabled value that appears in the Parameter Name column.

  7. In the Override Setting column, in the drop-down box, click True, and then click OK.

  8. In the Overrides list, under Recovery, click Restart Health Service, click Override, and then click For all objects of type: Health Service Watcher (Agent).

  9. Under Override-controlled parameters, in the Override column, select the check box next to the Enabled value that appears in the Parameter Name column.

  10. In the Override Setting column, in the drop-down box, click True, and then click OK.

  11. In the Overrides list, under Recovery, click Reinstall Health Service (triggered from Diagnostic), click Override, and then click For all objects of type: Health Service Watcher (Agent).

  12. Under Override-controlled parameters, in the Override column, select the check box next to the Enabled value that appears in the Parameter Name column.

  13. In the Override Setting column, in the drop-down box, click True, and then click OK.

Add a Run As Account to the Run As Profile for the Validate Alert Subscription Account

The alert subscription module uses the Validate Alert Subscription account to ensure that notification subscriptions are in scope. The account requires a Run As account that is a member of the Operations Manager Administrators user role and has administrator access to the root management server.

note附註
To find out whether a Run As account is a member of the Operations Manager Administrators users role, in the navigation pane, under Administration, expand Security, click User Roles, and then double-click Operations Manager Administrators.

To add a Run As Account to the Run As profile for the Validate Alert Subscription Account

  1. Open the Operations console, and then in the navigation pane, click the Administration button.

  2. Under Administration, expand Security, and then click Run As Profiles.

  3. Double-click Validate Alert Subscription Account, and then click the Run As Accounts tab.

  4. Click New, and then in the Run As Account drop-down menu, click a Run As account that has administrative rights on the root management server and has an Operations Manager Administrators user role.

  5. Under Matching Computers, click your root management server, and then click OK.

Enable the Operational Database Watchers Group to Management Group Availability Health Rollup

It is recommended that you enable the Operational Database Watchers Group to Management Group Availability Health Rollup monitor so that the state of the Operational Database Watchers Group rolls up to the management group.

To enable the monitor

  1. Open the Operations console, and then in the navigation pane, click the Authoring button.

  2. Under Authoring, expand Management Pack Objects, and then click Monitors.

  3. Under Monitors, expand Operations Manager Management Group, expand Entity Health, and then expand Availability.

  4. Right-click Operational Database Watchers Group to Management Group Availability Health Rollup, point to Overrides, point to Override the Monitor, and then click For all objects of type: Operations Manager Management Group.

  5. Under Override-controlled parameters, find the Enabled value that appears in the Parameter Name column, and then select the check box next to it in the Override column.

  6. In the Override Setting column for the Enabled parameter, in the drop-down box, click True, and then click OK.

Set the Configuration Service to Restart Automatically

The override that automatically restarts the configuration service for the Windows service state is disabled by default. To automatically start the configuration service when it stops, you must enable an override.

To set the monitor to automatically restart the configuration service

  1. Open the Operations console, and then in the navigation pane, click the Authoring button.

  2. Under Authoring, expand Management Pack Objects, and then click Monitors.

  3. Under Monitors, expand Root Management Server, expand Availability, and then expand Configuration Service Availability.

  4. Right-click Configuration Service - Windows Service State, click Properties, and then click the Overrides tab.

  5. In the list, under Recovery, click Start Config Service, click Override, and then click For all objects of type: Root Management Server.

  6. Under Override-controlled parameters, in the Override column, select the check box next to the Enabled value that appears in the Parameter Name column.

  7. In the Override Setting column, in the drop-down box, click True, and then click OK.

Make Sure That the Action Account on the Root Management Server Is a Member of the Operations Manager Administrators Group

The Operations Manager Management Pack includes a rule, Check for Updated Management Packs, which checks whether an updated version of an installed management pack is available. The rule runs a script, Powershell.exe, which requires the action account on the root management server to be a member of the Operations Manager Administrators Group.

If you configured the action account by using Local System or a user that is not part of the Operations Manager Administrators Group, the script will not work.

社群新增項目

顯示: