Search This Blog

Sunday, October 18, 2009

Integrate Operation Manager with VMM 2008 R2

Well, i can say that this is the toughest configuration that i have encountered while R & D on SCVMM which took me several days. Here is the result of my findings:-

My lab environment is using:-
a) SCVMM 2008 R2 with SQL Server 2008 SP1 (computer name: scvmm01)
b) SCOM 2007 R2 with SQL Server 2008 SP1 (computer name:scom01) . The SQL server is running SQL_Latin1_General_CP1_CS_AS collation.

To integrate Operation Manager with VMM 2008 R2, follow the step by step instruction:-

a) Install Operation Manager 2007 R2 or 2007 with SP1
b) Register SPNs for the root management server manually. Go to domain controller command prompt and enter the following command

SetSPN.exe –A MSOMSdkSvc/RootManagementServerFQDN domain\SDKServiceAccount


SetSPN.exe –A MSOMSdkSvc/RootManagementServerNetBIOS domain\SDKServiceAccount

example for my setup:-

setspn.exe -A MSOMSdkSvc/scom01.ms4u.info ms4u\OM-SDK
setspn.exe -A MSOMSdkSvc/scom01 ms4u\OM-SDK

c) View the registered SPN

setspn.exe -L scom01

d) Grant SDK service account permission to read and write the SPNs

1. On the domain controller, open adsiedit.msc. Navigate to the service account for the SDK service.
2. Right-click the service account (System Center Data Access service), and click Properties.
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.

e) Restart the domain controller and Operation Manager server.

f) Install Virtual Machine Manager server with using domain user account as services. (i have created a user account named "scvmmservices". Make sure you assign scvmmservices account as the local administrator group in the VMM server.

g) On the Operation Manager server, import the following Management Pack
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

h) Execute Configure Operation Manager option from VMM installation media. The Operations Manager configuration involves the following tasks:

-Import the VMM 2008 R2 Management Pack into Operations Manager.
-Add the VMM service account to the Administrator role in Operations Manager.
-Restart 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.)
-Install a VMM Administrator Console and Windows PowerShell – Virtual Machine Manager command shell on the root management server.

For the account assignment:-
1. On the Operation manager server
- Local administrator group consists of
  • Default Action Account
  • SDK Account
  • VMM Service Account
2. On the domain level
- Operation Manager Admin Group (OM-Admin) consists of
  • VMM Service Account
- Domain Admin Group consists of
  • Default Action Account
  • SDK Account
  • VMM Service Account
i) Enable the running of PRO scripts on VMM server and Operation manager server

Follow the following steps:-
1.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.

2.At the prompt, type A to 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.

j) On the VMM server, Install Operation Manager console

k) Add the default action accounts on Operations Manager management servers. In the Administration View of the VMM console, Click User roles, right click Administrator, select Properties and add Default Action Account on the Members tab.
















l) Specify the Operations Manager server in VMM.
Follow the following steps:-

1. On the Administration View, select System Center, right click Operation Manager Server and select Modify.
2. Enter the Operation Manager server name. eg: scom01.ms4u.info (enter Netbios or FQDN)


















m) Finally, you must install operation manager agent on VMM managed hosts and virtual machine.

n) To verify a successful Operation manager integration, click on Diagram button in the VMM console.







The diagram view should begin populating immediately.


















On next article, I will look into how to enable PRO in VMM and configure reporting in VMM.

No comments:

Post a Comment