VMM teams up with OpsMgr to provide a comprehensive end-to-end services management through monitoring the health and performance of workloads all the way down to the application level.
VMM and PRO (a feature of VMM that allows you to extend the services management and augment the available knowledge in the MPs to make recommendations or take actions that take advantage of the additional capabilities available when workloads are running in a virtualized environment) require System Center Operations Manger 2007, with SP1. Once you install that follow these instructions to import the VMM 2008 management pack.
1. From Administration view in the Operators Console for Operations Manager, click the Management Packs node in the navigation pane.
2. In the Actions pane on the right, click Import Management Pack.
3. Browse and select the following management pack files, and click Import:
4. After the management packs are imported, close the dialog box
The VMM server runs as the Local System account of the machine that it is installed on. If the Operations Manager server and the VMM server are installed on the same machine, you can skip this section. If they are installed on separate machines, you will need to grant access to the computer account of the VMM server to the Operations Manager Administrators user profile in Operations Manager. When Operations Manager is installed, it automatically grants the Local Administrators group Operations Manager Administrators rights. Thus, you can grant the VMM server those same rights by adding its computer account to the Local Administrators group on the OpsMgr server. After you make that change, you must restart the OpsMgr SDK Service in order for Operations Manager to recognize group membership changes.
After configuring Operations Manager, you can complete the configuration of PRO from the VMM Administrators Console by performing the following steps (you can also do the below operations from PowerShell using the cmdlet “Set-VMMServer -OpsMgrServer <servername>”):
1. Open the VMM Administrator’s Console, and click the Administration button beneath the navigation pane to display Administration view.
2. Select the System Center node in the navigation pane. Then right-click Operations Manager Server in the results pane, and click Modify.
3. In the dialog box (depicted below), enter the name of the Root Management Server of your Operations Manager installation, and click OK.
If you get an error here saying “VMM service does not have the necessary privileges to access the Operations Manager SDK service on <servername”, then you need to check if the OpsMgr SDK service is running under domain credentials. If yes, you need to register SPNs for the following two accounts: MSOMSdkSvc/<RMS FQDN> and MSOMSdkSvc/<RMS NETBIOSNAME>. You can use the SetSpn.exe utility for this. You need to be a domain admin to create an SPN. Also make sure that you provide the RMS server’s values in those commands. RMS is the OpsMgr Root Management Server in your environment.
A lot of this content was written by member of the VMM technical team (so I didn’t come up with all of these myself) 🙂
Next week, I will talk about how to enable PRO in the environment I just explained how to set up.