System Center Virtual Machine
Manager 2008 R2 RC Guide to Integrating
Operations Manager with VMM
Microsoft Corporation
Published: June 2009
Abstract
This guide provides information essential for the successful integration of System Center
Operations Manager 2007 with Service Pack 1 (SP1) or later with System Center Virtual Machine
Manager (VMM) 2008 R2 RC. The topics in this section provide system requirements and
detailed procedures for performing a successful integration, whether you are a new VMM
customer or you previously integrated Operations Manager with VMM 2008 or
VMM 2008 R2 Beta.

This document supports a preliminary release of a software product that may be changed
substantially prior to final commercial release. This document is provided for informational
purposes only and Microsoft makes no warranties, either express or implied, in this document.
Information in this document, including URL and other Internet Web site references, is subject to
change without notice. The entire risk of the use or the results from the use of this document
remains with the user. Unless otherwise noted, the companies, organizations, products, domain
names, e-mail addresses, logos, people, places, and events depicted in examples herein are
fictitious. No association with any real company, organization, product, domain name, e-mail
address, logo, person, place, or event is intended or should be inferred. Complying with all
applicable copyright laws is the responsibility of the user. Without limiting the rights under
copyright, no part of this document may be reproduced, stored in or introduced into a retrieval
system, or transmitted in any form or by any means (electronic, mechanical, photocopying,
recording, or otherwise), or for any purpose, without the express written permission of Microsoft
Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
© 2009 Microsoft Corporation. All rights reserved.
Microsoft, Windows, Active Directory, Windows Server, Hyper-V, Windows Vista, Windows XP,
SQL Server, and Windows PowerShell are trademarks of the Microsoft group of companies.
All other trademarks are property of their respective owners.

Contents
Updating Operations Manager Integration After Upgrading to VMM 2008 R2 ................................ 5
Configuring Operations Manager Integration with VMM 2008 ........................................................ 8
Ensure That Your Operations Manager Deployment Meets VMM Requirements ....................... 8
Configure Basic Operations Manager Integration with VMM ..................................................... 10
1. Prepare the VMM server for Operations Manager integration ........................................... 10
2. Set up your Operations Manager root management server for VMM integration .............. 11
3. Configure your other management servers for VMM integration ....................................... 13
4. Complete the VMM configuration ....................................................................................... 13
5. Install Operations Manager agents on managed hosts and virtual machines .................... 14
6. Verify a successful Operations Manager integration .......................................................... 15
Configure Reporting in VMM ...................................................................................................... 15
Enable PRO in VMM .................................................................................................................. 17
How to Manually Configure Operations Manager for VMM 2008 R2 ............................................ 18
How to Add Members to the Administrator Role in Operations Manager 2007 ............................ 20
How to Add a New VMM Server to an Existing VMM Management Group .................................. 22
How to Add a New Management Server to an Existing VMM Management Group ...................... 24

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
Updating Operations Manager Integration
After Upgrading to VMM 2008 R2
For customers who are migrating to System Center Virtual Machine Manager (VMM) 2008 R2
from VMM 2008, and who earlier integrated System Center Operations Manager 2007 with
VMM 2008, this topic explains how to update the Operations Manager integration for
VMM 2008 R2. You will need to import the System Center Virtual Machine Manager 2008 R2
Management Pack for Operations Manager 2007 and its prerequisites.
Note
If you are a new VMM customer or if you are moving from VMM 2007 to VMM 2008 R2,
to perform your initial Operations Manager integration with VMM, use the procedures in
Configuring Operations Manager Integration with VMM 2008.
Before you begin
Upgrade the VMM server from VMM 2008 to VMM 2008 R2. For instructions, see
“Upgrading from VMM 2008 to VMM 2008 R2” in the System Center Virtual Machine
Manager 2008 R2 RC Deployment Guide.
Note
You do not need to upgrade Operations Manager. VMM 2008 R2 supports
Operations Manager 2007 Service Pack 1 (SP1) and later.
To update to the VMM 2008 R2 Management Pack
1. Log on to your Operations Manager root management server under a domain account
that has Administrator rights on the local computer and is a member of the Operations
Manager Administrator user role. You cannot perform this procedure as a local user.
Note
If you have not been added to this role, see How to Add Members to the
Administrator Role in Operations Manager 2007.
2. Use Add or Remove Programs to remove the VMM Administrator Console.
3. On the Start menu, click All Programs, click System Center Operations
Manager 2007, and then click Operations Console.
4. Display Administration view by clicking the Administration button beneath the
navigation pane.
5. In the navigation pane, click the Management Packs node to view a list of the current
management packs.
6. Make the following changes to imported management packs:
a. Delete all management packs with names that begin with “System Center Virtual
5

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
Machine Manager 2008”. To delete a management pack, right-click the management
pack, and then click Delete.
Note
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. After completing the upgrade, you can reinstall any
PRO-enabled management packs that you had deployed to support
Performance and Resource Optimization (PRO) in VMM 2008. All PRO-
enabled management packs that were developed for VMM 2008 are
compatible with VMM 2008 R2. Their temporary removal is for maintenance
purposes only.
b. Import prerequisite management packs for the VMM 2008 R2 Management Pack.
The only new requirement for the VMM 2008 R2 Management Pack is the
management packs for Microsoft Windows Server Internet Information Services
(IIS) 7.0. Ensure that all the prerequisite management packs in the following list have
been imported.
Microsoft SQL Server Management Pack:
Microsoft.SQLServer.Library version 6.0.5000.0 or later
Windows Server Internet Information Services (IIS) 2000/2003/2008
Management Pack:
Microsoft.Windows.InternetInformationServices.2003 version 6.0.5000.0 or later
Microsoft.Windows.InternetInformationServices.2008 version 6.0.6539.0 or later
You can download these management packs from the System Center Operations
Manager 2007 Catalog (http://go.microsoft.com/fwlink/?LinkId=82105). For
deployment instructions, see the individual management pack guides, which are
downloaded with the management pack files.
7. Use the VMM 2008 R2 installation media to run the Configure Operations Manager
option of the Setup Wizard.
The Setup Wizard imports the VMM 2008 R2 Management Pack into Operations
Manager.
8. If you removed any management packs that depend on the VMM 2008 Management
Pack in step 6, you can import those management packs into Operations Manager again
at this point.
9. On the VMM server, use the Windows PowerShell – Virtual Machine Manager command
shell to specify the root management server in VMM:
a. To open Windows PowerShell – VMM, on the Start menu, click All Programs, click
Microsoft System Center, click Virtual Machine Manager 2008 R2, and then click
Windows PowerShell – Virtual Machine Manager.
6

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
b. At the PS> prompt, enter the following cmdlet, where <OpsMgrServerName> is the
name of the Operations Manager root management server:
Set-VMMServer –OpsMgrServer <OpsMgrServerName>
Important
You must perform this step to force a new discovery of the Operations
Manager root management server, even if you retained your VMM database
when you upgraded to VMM 2008 R2.
10. If you did not retain your VMM 2008 database when you upgraded to VMM 2008 R2, you
will need to reconfigure reporting and PRO in VMM:
a. Specify the reporting server for VMM. For more information, see “Setting Up
Reporting” in VMM 2008 R2 Help.
b. Enable PRO for the host groups and host clusters that you want to participate. Also, if
any of your PRO-enabled management packs contain PRO tips that target Virtual
Machine Manager, configure PRO settings for VMM. For more information, see
Enabling PRO in VMM 2008.
7

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
Configuring Operations Manager Integration
with VMM 2008
This topic provides procedures for integrating System Center Operations Manager 2007 with
System Center Virtual Machine Manager (VMM) 2008 R2 to enable health monitoring of
managed virtual machines and their hosts, Diagram views of the virtualized environment in VMM,
Performance and Resource Optimization (PRO), and VMM reporting.
Before you begin, ensure that your Operations Manager deployment meets VMM requirements.
Complete the basic Operations Manager integration procedures to provide health monitoring for
VMM and add Diagram views to the VMM Administrator Console. Then optionally set up
reporting and enable PRO in VMM.
This topic provides guidance and procedures for the following integration tasks:
Ensure that your Operations Manager deployment meets VMM requirements.
Configure basic Operations Manager integration with VMM.
Configure reporting in VMM.
Enable PRO in VMM.
Ensure That Your Operations Manager
Deployment Meets VMM Requirements
To be integrated successfully with VMM, your Operations Manager deployment must meet the
following requirements:
System Center Operations Manager 2007 Service Pack (SP1) or later must be installed.
A VMM server, and the hosts and virtual machines that the VMM server manages, must be
managed by a single Operations Manager management group. However, a single Operations
Manager management group can manage multiple instances of VMM. To be managed by the
same management group, all VMM servers must be running the same version of VMM (either
VMM 2008 or VMM 2008 R2).
You must deploy Operations Manager in an Active Directory domain that has a two-way trust
relationship with the domain that contains the VMM server. The integration requires Kerberos
authentication between VMM and Operations Manager. Because of differences in the way
that the two products handle Kerberos authentication, authentication issues can prevent
successful enabling of PRO when the Operations Manager server is not in a trusted domain.
Each time the OpsMgr SDK service (known in Operations Manager 2007 R2 as the System
Center Data Access service) starts on your Operations Manager root management server,
the service must be able to register Service Principle Names (SPNs) for itself in Active
Directory Domain Services (AD DS). If the SDK service runs as Local System, the account
has the needed permissions to read and write the SPNs, and you don’t need to update any
configurations. However, if you are using an Active Directory domain account as the run-as
8

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
account for the service, either you must manually register the SPNs for the root management
server or you must grant the SDK service account the permissions needed to read and write
the SPNs when the service starts.
The following procedures explain both methods for doing this.
To register SPNs for the root management server manually
At a command prompt on a domain-joined computer, running under an account that has
Write SPN permission, run the following commands to create an SPN for the fully
qualified domain name (FQDN) and the NetBIOS name of the root management server. If
the root management server is in a cluster, use the virtual server name.
SetSPN.exe –A MSOMSDK/<RootManagementServerFQDN>
<domain>\\<SDKServiceAccount>
SetSPN.exe –A MSOMSDK/<RootManagementServerNetBIOS>
<domain>\\<SDKServiceAccount>
Note
The Setspn tool is installed automatically with Windows Server 2008. For Windows
Server 2003–based computers, you can install the tool with the Windows Server 2003
Support Tools from the product CD or from the Microsoft Download Center
(http://go.microsoft.com/fwlink/?LinkId=100114). Setspn can be used with all releases of
Windows Server 2003 and with Windows Server 2008 and later. For more information
about how to install Windows Support Tools from the product CD, see Install Windows
Support Tools (http://go.microsoft.com/fwlink/?LinkId=62270).
To grant the SDK service account permission to read and write the SPNs
1. On the domain controller, open ADSIEdit.msc.
2. Navigate to your SDK service account. Right-click the account, and click Properties.
On an Operations Manager 2007 SP1 server, update the service account for the
OpsMgr SDK service.
On an Operations Manager 2007 R2 server, update the service account for the
System Center Data Access service.
3. On the Security tab, click Advanced, click Add, type SELF, and then click OK.
4. On the Properties tab, in the Apply Onto list, select This object only.
5. In the properties list, scroll to Read servicePrincipleName and Write
servicePrincipleName, and select Allow for each of them.
6. After saving the new permissions, restart the Operations Manager SDK service (in
Operations Manager 2007 SP1, the OpsMgr SDK service; in Operations
Manager 2007 R2, the System Center Data Access Service) on the root management
server.
9

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
Important
To help enhance security, grant the most restrictive access permissions that you can.
Although a domain administrator account can perform these actions by default, it is
recommended that you do not use a domain administrator account for the Operations
Manager SDK service account.
Configure Basic Operations Manager Integration
with VMM
The following procedures explain how to perform a basic Operations Manager integration with
VMM to provide health monitoring of virtual machines and hosts and enable Diagram views in the
VMM Administrator Console:
1. Prepare the VMM server for Operations Manager integration.
2. Set up your Operations Manager root management server for VMM integration.
3. Configure your other management servers for VMM integration.
4. Complete the VMM configuration.
5. Install Operations Manager agents on managed hosts and virtual machines.
6. Verify a successful Operations Manager integration.
1. Prepare the VMM server for Operations Manager integration
Before you begin configuring Operations Manager for integration with VMM, you must install the
VMM server and then perform the following procedure.
To prepare the VMM server for Operations Manager integration
1. Install the Virtual Machine Manager server if you have not already done so. For
instructions, see Installing the VMM Server in the System Center Virtual Machine
Manager 2008 R2 RC Deployment Guide.
2. 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 in the System Center Virtual Machine
Manager 2008 R2 RC Deployment Guide.
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 a VMM Administrator Console on
that server.
3. Install an Operations console for Operations Manager 2007 SP1 or later (install the
Operations Manager version that is running on your management servers) on the
VMM server.
10

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
2. Set up your Operations Manager root management server for
VMM integration
Perform the following procedure on the root management server only.
To set up your Operations Manager root management server for VMM integration
1. Log on to your Operations Manager root management server under a domain account
that is a member of the Operations Manager Administrator user role. You cannot perform
this procedure as a local user.
Note
If you have not been added to this role, see How to Add Members to the
Administrator Role in Operations Manager 2007.
2. If a VMM Administrator Console has been installed on the root management server, use
Add or Remove Programs to remove the console.
3. Import prerequisite management packs in Operations Manager:
a. On the Start menu, click All Programs, click System Center Operations
Manager 2007, and then click Operations Console.
b. Display Administration view by clicking the Administration button beneath the
navigation pane.
c. In the navigation pane, click the Management Packs node to view a list of the
current management packs.
d. Ensure that the following management packs, which are prerequisites for the
VMM 2008 R2 Management Pack, have been imported.
Microsoft SQL Server Management Pack:
Microsoft.SQLServer.Library version 6.0.5000.0 or later (Required)
Microsoft.SQLServer.2005.Monitoring (Recommended)
Microsoft.SQLServer.2005.Discovery (Recommended)
Microsoft.SQLServer.2008.Monitoring (Recommended)
Microsoft.SQLServer.2008.Discovery (Recommended)
Microsoft Windows Server Internet Information Services (IIS) 2000/2003/2008
Management Pack:
Microsoft.Windows.InternetInformationServices.CommonLibrary version
6.0.5000.0 or later
Microsoft.Windows.InternetInformationServices.2003 - 6.0.5000.0 or later
Microsoft.Windows.InternetInformationServices.2008 version 6.0.6539.0 or later
You can download the management packs from the System Center Operations
Manager 2007 Catalog (http://go.microsoft.com/fwlink/?LinkId=86411). To import the
management packs, on the Actions menu, click Actions, and then click Import
11

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
Management Packs.
4. Configure Operations Manager on the root management server by using one of the
following methods:
If your root management server is in the same Active Directory domain as the VMM
server, run Setup.exe from your VMM 2008 R2 installation media, and select the
Configure Operations Manager option. To install the console, you must be logged
on to the local computer as a local administrator. For installation instructions, see
Installing the VMM Administrator Console in the System Center Virtual Machine
Manager 2008 R2 RC Deployment Guide.
Important
Do not run this wizard option immediately after you install the VMM server.
The Setup Wizard will attempt to add the VMM service account to the local
Administrators group on the root management server. That operation will fail
unless you have allowed time for the replication of the SPNs for both the
VMM server and the VMM service account to your AD DS domain
controllers. AD DS replication time varies depending on factors such as the
network configuration, locations of your domain controllers, and the size and
complexity of the AD DS environment.
The Setup Wizard performs the following tasks:
Imports the VMM 2008 R2 Management Pack into Operations Manager.
Adds the VMM service account to the Administrator role in Operations Manager.
Restarts the Operations Manager SDK service on the root management server.
(The service name in Operations Manager 2007 SP1 is OpsMgr SDK service; in
Operations Manager 2007 R2, the service name is System Center Data Access
service.)
Installs a VMM Administrator Console and Windows PowerShell – Virtual
Machine Manager command shell on the root management server.
If your Operations Manager server is in a different Active Directory domain than
the VMM server, configure Operations Manager integration manually by following
the instructions in How to Manually Configure Operations Manager for VMM
2008 R2. The root management server must be in an Active Directory domain
that has a two-way trust relationship with the domain of the VMM server.
Important
If your management group contains multiple management servers, perform this
task only on the root management server.
5. To enable the running of PRO scripts, ensure that the local Windows PowerShell –
Virtual Machine Manager command shell allows execution of unsigned scripts or
remotely signed scripts. For more information about setting the script execution policy, in
12

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
the Windows PowerShell Cmdlet Help Topics on TechNet, see Set-ExecutionPolicy
(http://go.microsoft.com/fwlink/?LinkID=151620).
a. To open a Windows PowerShell – VMM session, on the Program menu, click
System Center, click Virtual Machine Manager 2008 R2, and then click Windows
PowerShell – Virtual Machine Manager.
b. 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.
3. Configure your other management servers for VMM integration
To complete the Operations Manager configuration, perform the following steps on each of the
other management servers that will monitor hosts and virtual machines managed by the
VMM server.
To configure an Operations Manager management server for VMM
1. Log on to the Operations Manager management server under an account that has local
Administrator rights.
2. Use your VMM 2008 R2 installation media to install a VMM Administrator Console on the
management server. For installation instructions, see “Installing the VMM Administrator
Console” in the System Center Virtual Machine Manager 2008 R2 RC Deployment
Guide.
3. To enable the running of PRO scripts, ensure that the local Windows PowerShell –
Virtual Machine Manager command shell allows execution of unsigned scripts or
remotely signed scripts:
a. Open the Windows PowerShell – Virtual Machine Manager command shell.
b. 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.
4. Complete the VMM configuration
To complete the VMM configuration, perform the following tasks on the VMM server.
To finish configuring VMM
1. Log on to the VMM server under an account that is a member of the Administrator user
role in VMM and an Administrator on the local computer.
2. Add the default action account for all Operations Manager management servers and for
the Operations Manager agent on the VMM server to the Administrator role in VMM:
a. In Administration view of the VMM Administrator Console, in the navigation pane,
click User Roles.
b. In the results pane, right-click Administrator, and then click Properties.
13

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
c. On the Members tab of the User Role Properties for Administrator dialog box, add
the default action account for the following, and then click OK:
Root management server for VMM
All other management servers in the VMM management group
Operations Manager agent on the VMM server
Important
If any of the default action accounts is Local System, you must also add the
computer account for that machine to the Administrator role.
3. Specify the Operations Manager server in VMM:
a. Still in Administration view, click System Center.
b. 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.
4. To enable the running of PRO scripts, ensure that the local Windows PowerShell –
Virtual Machine Manager command shell allows execution of unsigned scripts or
remotely signed scripts:
a. Open the Windows PowerShell – Virtual Machine Manager command shell.
b. 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.
5. Install Operations Manager agents on managed hosts and
virtual machines
To enable Operations Manager to discover the hosts and virtual machines and begin to collect
health and performance data, you must install an Operations Manager agent on your hosts and
virtual machines, including the following:
All Windows Server–based hosts running Hyper-V or Virtual Server that VMM is managing
Note
If VMM is managing a VMware Infrastructure 3 environment, you do not need to
install any Operations Manager agent on managed VMware ESX Server hosts or on
the VMware VirtualCenter server. For those computers, the Operations Manager
agent on the VMM server provides health and performance data to Operations
Manager and to PRO. However, to get monitoring within the guest operating systems
of VMware virtual machines, you do need to install an Operations Manager agent on
each virtual machine on your ESX Server hosts.
The guest operating systems of all virtual machines running Windows operating systems
14

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
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.
For more information about deploying Operations Manager agents, see the following topics:
How to Deploy the Operations Manager 2007 Agent for Agent-Management of Computers
(http://go.microsoft.com/fwlink/?LinkID=98813)
How to Use Active Directory Domain Services to Assign Computers to Operations
Manager 2007 Management Groups (http://go.microsoft.com/fwlink/?LinkId=127695)
6. Verify a successful Operations Manager 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 Operations Manager integration
1. In Monitoring view of the Operations console, expand Virtual Machine
Manager 2008 R2 Views.
The list should contain a diagram view for the VMM server.
2. 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.
Note
Operations Manager does not begin monitoring a host group until at least one
host has been added to the host group and is being monitored. The displayed
status of empty host groups is Not Monitored.
If a diagram view is not added for the VMM server, check the VM Manager event log on
the VMM server for a Discovery Failed error.
Configure Reporting in VMM
In VMM, reports are generated by Operations Manager, but they can be opened in Reporting
view of the VMM Administrator Console. Until you configure reporting in VMM, the console does
not display Reporting view, and the reports are not available in VMM.
Before you perform the VMM reporting configuration
1. Set up your reporting server in Operations Manager 2007 SP1 or later. For more
15

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
information, see Deploying Operations Manager 2007
(http://go.microsoft.com/fwlink/?LinkId=120280). For information about upgrading a
reporting server from Operations Manager 2007 to Operations Manager 2007 SP1, see
the Operations Manager 2007 SP1 Upgrade Guide
(http://go.microsoft.com/fwlink/?LinkId=151612).
2. Complete basic Operations Manager integration with VMM. For instructions, see
Configure Basic Operations Manager Integration with VMM, earlier in this topic.
To enable reporting in Virtual Machine Manager
1. To enable VMM administrators to view and use reports in VMM, add their user accounts
to the Report Operator role in Operations Manager. For instructions, see How to Add
Users or Groups to the Report Operator User Role in Operations Manager 2007
(http://go.microsoft.com/fwlink/?LinkId=120282).
2. Log on to the VMM client computer under an account that is a member of the
Administrator role in VMM.
3. Open the VMM Administrator Console, and display Administration view.
4. In the navigation pane, click System Center, and then, in the results pane, click
Operations Manager Reporting URL.
5. In the Actions pane, under Settings, click Modify.
6. To enable reporting, in the Reporting Settings dialog box, do the following:
a. Select the Enable reporting check box.
b. Specify the URL for the Operations Manager report server in the format
http[s]://<OpsMgrReportServer>[:<port>]/<ReportServer>, where:
<OpsMgrReportServer> is the computer name of your report server
<ReportServer> is the name of the report server virtual directory (by default,
“ReportServer”)
Note
The name of the report server cannot contain Unicode characters.
7. Click OK to have VMM check for a valid report server and then save the settings.
The Reporting view should be added to the buttons beneath the navigation pane.
After you configure reporting, you can immediately verify whether the reports are available in
Virtual Machine Manager.
To verify that reporting was successfully enabled in VMM
1. In the VMM Administrator Console, verify that Reporting has been added to the buttons
beneath the navigation pane.
2. If you do not see a Reporting button, close and re-open the VMM Administrator Console.
16

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
3. Click the Reporting button to display Reporting view.
If you don’t see a list of reports in Reporting view, this indicates that you have not been
added to the Report Operator role in Operations Manager. For information about adding
members to that role, see How to Add Users or Groups to the Report Operator User Role
in Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=120282).
Enable PRO in VMM
After you integrate Operations Manager 2007 with VMM, you can optionally enable Performance
and Resource Optimization (PRO) for individual host groups and host clusters that VMM is
managing. You can also set VMM PRO settings to enable PRO for issues that affect multiple
VMM-managed computers throughout your virtualized environment.
PRO takes integration with Operations Manager 2007 to a new level by allowing customers to tie
specific Operations Manager alerts to remediation actions that can be implemented automatically
or manually in VMM to return the virtualized environment to a healthy state.
For example, you might want to load-balance virtual machines between physical hosts when
specific thresholds are exceeded (transactions per second, CPU utilization, e-mail message
delivery SLA, and so on). Alternatively, you might want to migrate virtual machines when a
hardware failure is detected (for example, a fan failure). A PRO tip that targets VMM might define
a remediation action for an overheated blade chassis, for an issue with a distributed application
(such as Microsoft Exchange) that is deployed on multiple physical computers, or for an issue
with a storage array.
PRO is implemented through specially designed PRO-enabled management packs that define
PRO target classes and groups, and provide monitors that watch the performance of virtual
machines, hosts, applications, and hardware to identify opportunities to optimize a virtualized
environment.
VMM administrators view and implement PRO tips by using the PRO Tips window in the VMM
Administrator Console. PRO tips are closed automatically and dismissed from the PRO Tips
window when a monitored object returns to a healthy state.
The VMM 2008 R2 Management Pack includes four PRO-enabled management packs that
define the basic classes and groups that support PRO and provide monitors to optimize the
performance of hosts and virtual machines based on CPU and memory thresholds. The VMM
product team is working with partners to develop additional PRO-enabled management packs. To
find out about available PRO-enabled management packs, go to the PRO Partners site
(http://go.microsoft.com/fwlink/?LinkId=128923). All other PRO-enabled management packs are
dependent on the VMM 2008 R2 Management Pack.
For a detailed description of the basic PRO capabilities provided by the VMM 2008 R2
Management Pack, information about how PRO is implemented, guidance for planning for PRO,
and instructions for enabling PRO for individual host groups, individual host clusters, and
systemwide PRO actions, see Enabling PRO in VMM 2008.
17

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
How to Manually Configure Operations
Manager for VMM 2008 R2
If your Virtual Machine Manager server is in a different Active Directory domain than the
Operations Manager root management server that you will use to manage VMM and its
components, use the following procedure instead of the Configure Operations Manager option
of the VMM Setup Wizard to configure System Center Operations Manager 2007 with SP1 or
later for System Center Virtual Machine Manager 2008 R2 (VMM).
Important
Do not perform this procedure without first performing the preceding integration tasks that
are described in Configuring Operations Manager Integration with VMM 2008. This
procedure explains how to perform one task in the integration process. To ensure a
successful integration, follow the end-to-end procedures in that topic carefully.
Before you begin
Ensure that your Operations Manager deployment meets VMM requirements. For
Operations Manager requirements, see Configuring Operations Manager Integration with
VMM 2008.
To manually configure Operations Manager for VMM
1. Log on to your Operations Manager root management server under a domain account
that has Administrator rights on the local computer and is a member of the Administrator
user role in Operations Manager.
2. Add the VMM service account to the Administrator role in Operations Manager. For
instructions, see How to Add Members to the Administrator Role in Operations Manager
2007.
3. Restart the Operations Manager SDK service on the root management server:
On an Operations Manager 2007 SP1 server, restart the OpsMgr SDK service.
On an Operations Manager 2007 R2 server, restart the System Center Data Access
service.
4. In the Operations console for Operations Manager, import the VMM 2008 R2
Management Pack. You can import the management pack files from the
amd64\\VirtualizationMP folder on your VMM 2008 R2 installation media, or you can
download the management pack from the System Center Operations Manager 2007
Catalog (http://go.microsoft.com/fwlink/?LinkId=82105).
5. Install the VMM Administrator Console on the root management server. For instructions,
see “Installing the VMM Administrator Console” in the System Center Virtual Machine
Manager 2008 R2 RC Deployment Guide.
18

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
See Also
Configuring Operations Manager Integration with VMM 2008
19

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
How to Add Members to the Administrator
Role in Operations Manager 2007
To configure System Center Operations Manager 2007 SP1 or later for integration with System
Center Virtual Machine Manager 2008 R2 (VMM), you must be a member of the Administrator
role in Operations Manager. Use the following procedure to add members to the Administrator
role in Operations Manager. The account that you use for the Operations Manager integration
with VMM also must have Administrator rights on the VMM server.
When Operations Manager 2007 SP1 or later is deployed, an Active Directory users group is
specified as the Operations Manager Administrators group. To be added to the Operations
Manager Administrator user role, your domain account must be a member of that group.
Note
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
1. 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.
2. Click Administration under the navigation pane to display the Administration view.
3. In the navigation pane, click User Roles.
4. 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.
5. To add to the group membership, click Add.
6. In the Select Group dialog box, click Locations.
7. 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.
8. 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.
9. 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.
20

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
See Also
Configuring Operations Manager Integration with VMM 2008
Updating Operations Manager Integration After Upgrading to VMM 2008 R2
21

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
How to Add a New VMM Server to an Existing
VMM Management Group
Use the following procedure to add another VMM server to an Operations Manager management
group that is already monitoring a System Center Virtual Machine Manager (VMM) 2008 or
VMM 2008 R2 server.
A single Operations Manager management group can manage multiple VMM servers. However,
a VMM server must be managed by only one management group. To be managed by the same
management group, all VMM servers must be running the same version of VMM (either
VMM 2008 or VMM 2008 R2).
Note
If you have not already integrated the Operations Manager management group with
VMM, use the procedures in Configuring Operations Manager Integration with VMM
2008.
To prepare the VMM server for Operations Manager integration
1. Install the Virtual Machine Manager server if you have not already done so. For
instructions, see Installing the VMM Server.
2. Install an Operations console for Operations Manager 2007 SP1 or later (install the
Operations Manager version that is running on your management servers) on the VMM
server.
To add another VMM server to an integrated Operations Manager management group
1. Log on to the Operations Manager root management server under a domain account that
has Administrator rights on the local computer and is a member of the Operations
Manager Administrator user role. You cannot perform this procedure as a local user.
Note
If you have not been added to this role, see How to Add Members to the
Administrator Role in Operations Manager 2007.
2. Add the VMM server’s run-as account to the Administrator role in Operations Manager.
For instructions, see How to Add Members to the Administrator Role in Operations
Manager 2007.
3. Restart the SDK service on the root management server:
On an Operations Manager 2007 SP1 server, restart the OpsMgr SDK service.
On an Operations Manager 2007 R2 server, restart the System Center Data Access
service.
4. Log on to the VMM server under an account that is a member of the Administrator user
22

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
role in VMM and an Administrator on the local computer.
5. Add the default action account for each of the Operations Manager management servers
and for the Operations Manager agent on the VMM server to the Administrator role
in VMM:
a. In Administration view of the VMM Administrator Console, in the navigation pane,
click User Roles.
b. In the results pane, right-click Administrator, and then click Properties.
c. On the Members tab of the User Role Properties for Administrator dialog box, add
the default action account for the following:
Root management server
All other management servers in the VMM management group
Operations Manager agent on the VMM server
Important
If the default action account for a management server is Local System, you also
must add the computer account for that machine to the Administrator role.
6. Specify the Operations Manager server in VMM:
a. In Administration view, click System Center.
b. 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.
7. To enable the running of PRO scripts, ensure that the local Windows PowerShell –
Virtual Machine Manager command shell allows execution of unsigned scripts or
remotely signed scripts:
a. Open the Windows PowerShell – Virtual Machine Manager command shell.
b. 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.
Note
For more information about setting the script execution policy, in the Windows
PowerShell Cmdlet Help Topics on TechNet, see Set-ExecutionPolicy
(http://go.microsoft.com/fwlink/?LinkId=151620).
See Also
Configuring Operations Manager Integration with VMM 2008
How to Add Members to the Administrator Role in Operations Manager 2007
23

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
How to Add a New Management Server to an
Existing VMM Management Group
Use the following procedure to update your System Center Operations Manager 2007 integration
with System Center Virtual Machine Manager (VMM) 2008 or VMM 2008 R2 after you add a new
management server to the Operations Manager management group that is monitoring VMM.
Note
All management servers that you use with a VMM server must be in the same Operations
Manager management group.
To integrate an additional Operations Manager management server with VMM
1. Log on to the management server under a domain account that has local Administrator
rights and is a member of the Administrator role in VMM.
2. Use your VMM 2008 R2 installation media to install a VMM Administrator Console on the
management server. For instructions, see Installing the VMM Administrator Console in
the System Center Virtual Machine Manager 2008 R2 RC Deployment Guide.
3. Add the default action account for the management server to the Administrator role
in VMM:
a. On the Start menu, click All Programs, click Microsoft System Center, click Virtual
Machine Manager 2008 R2, and then click Virtual Machine Manager
Administrator Console.
b. To display Administration view, click the Administration button beneath the
navigation pane.
c. In the navigation pane, click User Roles.
d. In the results pane, right-click Administrator, and then click Properties.
e. On the Members tab of the User Role Properties for Administrator dialog box, add
the default action account for the management server, and then click OK.
4. Enable remote running of scripts in the Windows PowerShell – Virtual Machine Manager
command shell. This is needed to enable Performance and Resource Optimization
(PRO) to run scripts remotely on the server for Hyper-V and Virtual Server hosts that are
managed by the management server.
a. 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.
b. 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.
24

[This is prerelease documentation and is subject to change in future releases.
Blank topics are included as placeholders.]
Note
For more information about setting the script execution policy, in the Windows
PowerShell Cmdlet Help Topics on TechNet, see Set-ExecutionPolicy
(http://go.microsoft.com/fwlink/?LinkID=151620).
See Also
Configuring Operations Manager Integration with VMM 2008
25