How to Update Your Operations Manager Integration After Upgrading to VMM 2008 R2

  • Article

Applies To: Virtual Machine Manager 2008 R2

If you are migrating to System Center Virtual Machine Manager (VMM) 2008 R2 from VMM 2008, and you have previously integrated System Center Operations Manager 2007 with VMM 2008, this topic explains how to update the Operations Manager integration for VMM 2008 R2. To do this, you must import the System Center Virtual Machine Manager 2008 R2 Management Pack for Operations Manager 2007 and its prerequisite management packs.

Note

If you are a new VMM customer deploying VMM 2008 R2 or if you are migrating from VMM 2007 to VMM 2008 R2, use the procedures in How to Integrate Operations Manager with VMM 2008 R2 to perform your initial Operations Manager integration.

Before you begin

Note

You do not have to upgrade Operations Manager 2007. VMM 2008 R2 supports Operations Manager 2007 with Service Pack 1 (SP1) and Operations Manager 2007 R2.

To update your Operations Manager integration after migrating to VMM 2008 R2

  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. Open the Operations console, and display a list of the current management packs:

    1. On the Start menu, click All Programs, click System Center Operations Manager 2007, and then click Operations Console.Display Administration view by clicking the Administration button beneath the navigation pane.

    2. In the navigation pane, click the Management Packs node.

  4. 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.

    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. This includes all PRO-enabled management packs that you deployed to support Performance and Resource Optimization (PRO) in VMM 2008. Most PRO-enabled management packs that were developed for VMM 2008 are compatible with VMM 2008 R2 and can be imported again after you update the Operations Manager integration.

  5. Determine whether the following management pack files have been imported. 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.

    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

  6. If needed, download the prerequisite management packs from the following Web sites:

  7. To import the management packs, on the Actions menu of the Operations console, click Actions, click Import Management Packs, select the management packs to be imported, and then click Install.

  8. If the management server is running Windows Server 2003, verify that Windows PowerShell version 1.0 is installed. For download instructions, see Download Windows PowerShell 1.0 (https://go.microsoft.com/fwlink/?LinkId=77521). You cannot install a VMM Administrator Console as described in the following step unless Windows PowerShell is installed.

    You do not have to perform this step if the management server is running Windows Server 2008 R2 or Windows Server 2008. In Windows Server 2008 R2, Windows PowerShell is installed automatically. In Windows Server 2008, Windows PowerShell is available as an optional component on the installation disk or via Server Manager; the VMM Setup Wizard will install the component if it has not already been installed.

    Important

    If you changed to a different VMM service account when you upgraded to VMM 2008 R2, do not perform the following step 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 service connection point (SCP) to replicate 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.

    If your management group contains more than one management server, perform the following step on the root management server only.

  9. Configure Operations Manager on the root management server by using one of the following methods:

    • 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.

    • 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 then 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 (https://go.microsoft.com/fwlink/?LinkId=121007).

      On the Port Assignment page, enter the following options:

      In VMM server box, specify the VMM server to connect to. If you are not using the default port for client connections to the VMM server (port 8100), type the computer name followed by a colon and the connection port that you assigned when you installed the VMM server.

      Important

      If the VMM server is in a disjointed namespace, you must identify it by its fully qualified domain name (FQDN).

      In the VMM server port box, type the port to use for the VMM Administrator Console to communicate with the VMM server.

      Important

      The port setting that you assign for the VMM Administrator Console must match the port setting that you assigned for the VMM Administrator Console during the installation of the VMM server. For more information about assigning ports, see VMM Ports and Protocols (https://go.microsoft.com/fwlink/?LinkID=128912).

    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.

      Important

      If you use the Setup Wizard to configure Operations Manager, you might need to manually add the VMM service account to the Administrator role in Operations Manager. The Setup Wizard adds the VMM service account to the BUILTIN\Administrators group on the root management server, which by default populates the Administrator role in Operations Manager. If your organization uses a different group to populate the Administrator role, you must manually add the VMM service account to that group. For more information, see How to Add Members to the Administrator Role in Operations Manager 2007.

    • 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.

  10. 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 the Windows PowerShell Cmdlet Help Topics on TechNet, see Set-ExecutionPolicy (https://go.microsoft.com/fwlink/?LinkID=151620).

    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.

  11. If you removed any management packs that depend on the VMM 2008 Management Pack, you can import those management packs back into Operations Manager. If you are unable to import a PRO-enabled management pack, find out from the management pack developer whether an updated version is available for VMM 2008 R2. You can check the System Center Operations Manager 2007 Catalog (https://go.microsoft.com/fwlink/?LinkID=98812) for updates to PRO-enabled management packs that you downloaded from that site.

  12. On the VMM server, use the Windows PowerShell – Virtual Machine Manager command shell to specify the root management server in VMM:

    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 PS> prompt, enter the following cmdlet, where <OpsMgrServerName> is the name of the Operations Manager root management server:

      Set-VMMServer -OpsMgrServer <OpsMgrServerName>

    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.

  13. On all of the other management servers, perform the following steps:

    1. Remove the VMM Administrator Console and then use your VMM 2008 R2 installation media to reinstall it.

    2. Open the Windows PowerShell – Virtual Machine Manager command shell. If you see a prompt, type A to select [A]lways to always trust remote signed scripts from this snap-in.

  14. 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:

See Also

Concepts

Configuring Reporting for VMM
How to Integrate Operations Manager with VMM 2008 R2

Other Resources

Configuring Security for Operations Manager Integration and PRO in VMM
Upgrading to VMM 2008 R2 from VMM 2008