To prepare the VMM server for Operations Manager integration

You must perform step 1 before you perform all other steps. To avoid potential access permissions issues when you run the Setup wizard, wait a few minutes to allow replication of Active Directory updates to domain controllers.

Unless the VMM server also is serving as your Operations Manager root management server, install a VMM Administrator Console on the VMM server. For instructions, see Installing the VMM Administrator Console.

The root management server is the first management server installed in an Operations Manager management group. The Configure Operations Manager option of Setup.exe, which you will run in the following procedure, will install the VMM Administrator on that server.

Install an Operations Console for Operations Manager 2007 SP1 on the VMM server.

To configure your Operations Manager management servers

Log on to your Operations Manager root management server under an account that is a member of the Operations Manager Administrator user role. You cannot perform this procedure as a local user.

To import the management packs, on the Actions menu, click Actions, and then click Import Management Packs.

If the pre-release version of any of the VMM 2008 management packs has been imported, delete those management packs. That is, delete all management packs with names that begin with “System Center Virtual Machine Manager 2008”. To delete a management pack, right-click the management pack, and then click Delete.

On the root management server, run Setup.exe from your VMM 2008 installation media, and select the Configure Operations Manager option.

Importante

If your management group contains multiple management servers, run this wizard only on the root management server. Before running the wizard, you must install the VMM server.

The Setup Wizard performs the following tasks:

Imports the VMM 2008 management packs, including all management packs required for Performance and Resource Optimization (PRO) in VMM.

Grants the run-as account of the VMM server the necessary access to Operations Manager.

Installs a VMM Administrator Console on the root management server.

Before proceeding further, you need to update the VMM 2008 Management Pack with the latest version, which provides reports for Virtual Machine Manager. In addition, the Microsoft.SystemCenter.VirtualMachineManager.Pro.2008.Public class in the System Center Virtual Machine Manager 2008 PRO Library management pack has been redefined as an abstract class. For this reason, you will need to delete the PRO management packs before you import the new management pack files.

To replace the previous VMM 2008 Management Pack:

Delete all previously installed PRO management packs that were installed during the previous step. In the Administration pane of the Operations console, expand Management Packs to view a list of management packs that have been imported. Delete all management packs with a name that begins with “System Center Virtual Machine Manager 2008 PRO” in addition to any dependent management packs. To delete a management pack, right-click the management pack, and then click Delete.

Nota

If any other imported management packs depend on the VMM 2008 Management Pack, the Dependent Management Packs error message appears. You must remove the dependent management packs before you can complete the task. You must update any PRO-enabled management packs that were developed before this release of the VMM 2008 Management Pack. To update an existing PRO-enabled management pack, contact the organization that developed it.

In the results pane, right-click Administrator, and then click Properties.

On the Members tab of the User Role Properties for Administrator dialog box, add the default action account for each of the management servers, and then click OK.

On each management server and on the VMM server, enable remote running of scripts in the Windows PowerShell – Virtual Machine Manager snap-in. This is needed to enable PRO to run scripts remotely on the server.

To open a VMM PowerShell session, on the Program menu, click System Center, click Virtual Machine Manager 2008, and then click Windows PowerShell – Virtual Machine Manager.

At the prompt, select [A]lways to always trust remote signed scripts from this snap-in. If you don’t see a prompt, the policy already allows PRO to run scripts.

To configure the Operations Manager server in VMM

In Administration view of the VMM Administrator Console, click System Center.

In the results pane, right-click Operations Manager Server, and then click Properties.

In the Server name field, enter the computer name, NETBIOS, or fully qualified domain name (FQDN) of the root management server for Operations Manager. In a disjointed namespace, you must enter the FQDN.

Verify a Successful Integration

To verify a successful Operations Manager integration, check the Diagram views in the Operations Console to ensure that a view has been added for the VMM server.

To verify a successful integration

Display the VMM server diagram view to view the objects that Operations Manager is monitoring in the VMM management group.

After you configure the Operations Manager server in VMM, the diagram view should begin populating immediately. For very large VMM virtualized environments, the initial discovery might take as long as an hour to complete.

Nota

Operations Manager does not begin monitoring a host group until at least one host has been added. For this reason, the diagram shows the status of empty host groups as Not Monitored.

If Operations Manager integration is not successful, a Discovery Failed error is added to the VM Manager event log on the VMM server.

Troubleshooting Operations Manager Integration with VMM

The two most common issues that arise after an Operations Manager configuration relate to PRO tip failures:

PRO tip remediation action fails—Ensure that a VMM Administrator Console is installed on the management server that is monitoring the PRO target.

Access is denied during a PRO action—Ensure that the action account for the management server monitoring the PRO target has been added to the Administrator user role in VMM.

Next Steps

Deploy Operations Manager agents on your hosts and virtual machines—To collect data for PRO, you must install an Operations Manager agent on each Hyper-V host and Virtual Server host and on the guest operating system of each virtual machine. If you are using VMM to manage a VMware Infrastructure 3 environment, you don’t need to install any Operations Manager agents for the VirtualCenter server and ESX Server hosts; the Operations Manager agent on the VMM server monitors the VMware components. However, you do need to install an Operations Manager agent on the operating system of each VMware virtual machine. For information installing the agents, see Appendix B: Deploying Operations Manager Agents on Host and Virtual Machines.

Enable PRO in VMM—Enable PRO for individual host groups and host clusters and for VMM server-level actions. For more information, see Enabling PRO in VMM.

Set up reporting in VMM—VMM reports are generated by Operations Manager and available in VMM. Until you configure reporting, Reporting view is not displayed in the VMM Administrator Console. For more information, see Setting Up Reporting in VMM.

Appendix A: Adding Users to the Operations Manager Administrators Role

Use the following procedure to add members to the Operations Manager Administrator role. When Operations Manager 2007 is deployed, an Active Directory users group is specified as the Operations Manager Administrators group. To be added to the Operations Manager Administrators user role, your domain account must be a member of that group. The account must also have Administrator rights on the VMM server.

Nota

To perform the following procedure, you must be a member of the Operations Manager Administrators role.

To add members to the Operations Manager Administrator role

Open the Operations Console for Operations Manager 2007. To do this, on the Start menu, click All Programs, click System Center Operations Manager 2007, and then click Operations Console.

Click Administration under the navigation pane to display the Administration view.

In the navigation pane, click User Roles.

In the results pane, under Profile: Administrator, right-click Operations Manager Administrators, and then select Properties.

In the Operations Manager Administrators – User Role Properties dialog box, the General tab shows the Active Directory users group that was assigned to this user role during Setup. The default group is BUILTIN\Administrators.

To begin to add members to the user role, click Add.

In the Select Group dialog box, click Locations.

In the Locations dialog box, expand the OU tree, navigate to the OU that contains the group that you want to add to the role, and then click OK.

In the Select Group dialog box, under Enter the object name to select, type the name of the group or user account, and then click Check Names. If the account is found, the account name will be underlined. Click OK.

In the Operations Manager Administrators – User Role Properties dialog box, note that the group that you just selected has been added to the Administrator user role.

To collect data for hosts and virtual machines, you must install an Operations Manager agent on each Hyper-V host and each Virtual Server host that VMM is managing and on each virtual machine.

Nota

If VMM is managing a VMware Infrastructure 3 environment, you do not need to install any Operations Manager agents on the managed VMware ESX Server hosts. For those servers, the Operations Manager agent on the VMM server provides health and performance data to Operations Manager and to PRO. However, you do need to install an Operations Manager agent on the operating system of each VMware virtual machine.

You can use a Windows PowerShell script to install agents on your existing hosts and virtual machines.

To install an agent on new hosts and virtual machines, it is recommended that you install the agent on your host images and your virtual machine templates and then use Active Directory Domain Services to assign the computers to the VMM management group.