1. Log on to the computer with an account that is a member of the Operations Manager Administrators user role or Operations Manager Authors user role for the Operations Manager 2007 management group.

2. In the Operations console, click the Authoring button.

3. In the Authoring pane, expand Authoring, expand Management Pack Objects, and then click Monitors.

4. In the Monitors pane, click Change Scope.

5. In the Scope Management Pack Objects dialog box, in the Find text box, type Windows Computer, select the Windows Computer check box, and then click OK.

6. In the Monitors pane, expand Windows Computer, expand Entity Health, right-click Availability, point to Create a monitor, and then click Dependency Rollup Monitor.

7. In the Create a dependency monitor wizard, on the General Properties page, in the Name box, type a name for the dependency rollup monitor (for example, Windows Logical Hardware Components Health Rollup), and then you can type a description.

   Note

   You can either select a management pack from the Select destination management pack list or create a new unsealed management pack by clicking New. By default, when you create a management pack object, disable a rule or monitor, or create an override, Operations Manager saves the setting 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.

8. In the Parent monitor list, click the appropriate parent monitor, and then click Next.

9. On the Configure Monitor Dependency page, expand Windows Logical Hardware Component, expand Entity Health, click Availability, and then click Next.

10. On the Configure Health Rollup Policy page, under Health Rollup Policy, do one of the following:

    • Click Worst state of any member if you want the health state of the dependency rollup monitor to reflect the least healthy state of any member, and then click Next.
      
      
    • Click Worst state of the specified percentage of members in good health state if you want the state of the dependency rollup monitor to reflect the worst state of the best n percentage of the total number of members, and then type the percentage of the total number of members, and then click Next.
      
      
    • Click Best state of any member if you want the health state of the dependency rollup monitor to reflect the most healthy state of any member, and then click Next.
      
      

11. On the Configure Health Rollup Policy page, under Monitoring Unavailable and Maintenance Mode, for Monitoring unavailable, select one of the following:

    • Rollup monitoring unavailable as error if you want an unmonitored instance to roll up as an error.
      
      
    • Rollup monitoring unavailable as warning if you want an unmonitored instance to roll up as a warning.
      
      
    • Ignore if you do not want an unmonitored instance to roll up.
      
      

12. On the Configure Health Rollup Policy page, under Monitoring Unavailable and Maintenance Mode, for Maintenance mode select one of the following:

    • Rollup monitor in maintenance mode as error if you want monitored objects in maintenance mode to roll up as an error.
      
      
    • Rollup monitor in maintenance mode as warning if you want monitored objects in maintenance mode to roll up as a warning.
      
      
    • Ignore, if you do not want an instance in maintenance mode to roll up.
      
      

      Note
      As a best practice for steps 11 and 12, consider instances that are unavailable to be a higher concern than those that are in maintenance mode. For example, instances in maintenance mode roll up as a warning and instances that are unavailable roll up as error.

13. Click Next.

14. On the Configure Alerts page, specify the alert settings appropriate for your environment, and then click Create.

Tasks