Configuring the Monitoring Pack for VMM
Use the information in this section to configure your VMM Monitoring Pack.
Best Practice: Create a Management Pack for Customizations
Security Configuration
Tuning Performance Threshold Rules
Best Practice: Create a Management Pack for Customizations
By default, Operations Manager saves all customizations such as overrides 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.
When you create a management pack for the purpose of storing customized settings for a sealed management pack, it is helpful to base the name of the new management pack on the name of the management pack that it is customizing, such as “VMM Management Server Customizations”.
Creating a new management pack for storing customizations of each sealed management pack makes it easier to export the customizations from a test environment to a production environment. It also makes it easier to delete a management pack, because you must delete any dependencies before you can delete a management pack. If customizations for all management packs are saved in the Default Management Pack and you need to delete a single management pack, you must first delete the Default Management Pack, which also deletes customizations to other management packs.
Security Configuration
To support interactions between the VMM monitoring pack and Virtual Machine Manager, the VMM service account must be an administrator in Operations Manager, and the action account on each Operations Manager management server must be a member of the Administrator user role in VMM.
VMM Service Account Requirements
VMM connects to the Operations Manager server as the VMM service account. The service account can be either Local System or an Active Directory domain account with administrative rights in Operations Manager. The service account is specified when you integrate VMM with Operations Manager.
By default, the Operations Manager Administrator role is populated by the accounts in the local Administrators group. Therefore, adding the account to that group provides the administrator rights that VMM requires. However, the local group that populates the Administrator role is a configurable option in Operations Manager. If a different local group has been specified for this purpose, you must add the VMM service account to that group manually. The run-as account for the VMM server can be either Local System or a domain account. When you configure VMM to work with Operations Manager, VMM adds the run-as account to the Operations Manager Administrator role.
Action Account Requirements for PRO on Management Servers
To provide the credentials to perform PRO remedial actions in VMM, the management server action account on each of your Operations Manager management servers must be a member of the Administrator role in VMM.
The action account can be the Local System account, or it can be an Active Directory domain account that has administrative rights on the management server. You do not need to use the same action account on all of your management servers.
To make the account a VMM administrator, add it to the Administrator role in VMM. User roles are configured in the Security node, under User Roles in the Settings workspace of the VMM console. For a procedure, see Configuring Operations Manager Integration with VMM.
Groups
You can delegate authority to a precise level with user roles. For more information about user roles, see About User Roles in Operations Manager 2007 in Operations Manager 2007 Help or Implementing User Roles.
The VMM monitoring pack defines the following computer groups, which can be used for scoping and roles authorization:
All Clouds
All Hosts
Library Servers
Virtual Machine Manager Management Group
Tuning Performance Threshold Rules
In the VMM monitoring pack, performance thresholds for hosts and virtual machines are set by monitors in the PRO-enabled management packs. For information about tuning those thresholds, see Tuning PRO Performance Thresholds in this guide. The VMM management server, library servers, and self-service Web servers are monitored for availability but not performance.