Export (0) Print
Expand All

Migrating to VMM 2008 from VMM 2008 Beta

Updated: August 14, 2009

Applies To: Virtual Machine Manager 2008

This topic provides step-by-step instructions for migrating from System Center Virtual Machine Manager (VMM) 2008 Beta to VMM 2008 while retaining your previous VMM data.

When you update the VMM database, the following data and objects are lost:

  • Jobs table

  • The passwords and product keys for the following:

    • Standalone templates

    • Operating system profiles

    • Hardware profiles

When you update the VMM database, the following data and objects are retained:

  • Self-service information

  • Custom fields for virtual machines and hosts

CautionCaution
To avoid the loss of important data, before you update the VMM database, it is highly recommended that you perform a full backup of your VMM database.

To migrate from Virtual Machine Manager 2008 Beta to VMM 2008

  1. In the VMM Administrator Console, remove all hosts that are either on a perimeter network or that are in a domain that does not have a two-way trust with the VMM server’s domain.

    ImportantImportant
    You must remove these hosts before you upgrade the VMM 2008 Beta VMM database, and then add the hosts back after you have completed the migration to VMM 2008. You must also reconfigure the host reserves for these hosts after you have added them to VMM 2008.

  2. If you are using VMM to manage one or more VMware Infrastructure 3 environments, you must remove any VMware VirtualCenter servers before you upgrade the VMM 2008 Beta VMM database, and then add them back after you have completed the migration to VMM 2008. For more information about removing a VMware VirtualCenter server, see How to Remove a Virtualization Manager from VMM. For more information about adding a VMware VirtualCenter server, see How to Add a VMware VirtualCenter Server.

  3. On the computer where your VMM 2008 Beta VMM server is installed, uninstall the VMM server and, on the Uninstallation Options page, click Retain data. For more information, see Uninstalling VMM Components.

  4. Obtain the UpgradeV2Beta.exe program, and then move it to a folder on which you have Write permission.

    The UpgradeV2Beta.exe program is available from Microsoft Help and Support. For more information, see the News and Troubleshooting from the Product Team and Support Engineers website (http://go.microsoft.com/fwlink/?LinkId=127036).

  5. On a computer with .NET Framework 2.0 and SQL Server tools installed, open a Command Prompt window with elevated privileges, and then run the UpgradeV2Beta.exe program specifying the following:

    • The computer name and SQL Server instance name where your VMM 2008 Beta database is located.

    • The name of the VMM 2008 Beta database using the following syntax: UpgradeV2Beta.exe -server [servername\instancename] -database [databasename]. The default VMM instance name is MICROSOFT$VMM$ and the default database name is VirtualManagerDB.

    ImportantImportant
    You must move the UpgradeV2Beta.exe program to a folder on which you have Write permission before you run it.

  6. On the same computer that your VMM 2008 Beta VMM server was installed on, or on another computer that meets the minimum system requirements for installing the VMM server for VMM 2008, install the VMM server for VMM 2008 and, on the SQL Server Settings page of the wizard specify the previously upgraded database.

    noteNote
    For more information about the minimum system requirements for installing the VMM server, see System Requirements: VMM Server.

  7. Follow the instructions for installing the VMM Administrator Console, and then connect it to the new VMM server. For more information, see Installing the VMM Administrator Console.

  8. In the VMM Administrator Console, in Host view, click one or more hosts, and then, in the Actions pane, click Refresh.

  9. In the VMM Administrator Console, in Administration view, click Managed Computers.

    If you installed the VMM 2008 VMM server on the same computer as your VMM 2008 Beta VMM server, all hosts that were being managed by VMM 2008 Beta will have an agent version status of Unsupported.

    If you installed the VMM 2008 VMM server on a different computer than your VMM 2008 Beta VMM server, all hosts that were being managed by VMM 2008 Beta will have an agent version status of Access Denied.

  10. In the VMM Administrator Console, in the Managed Computers node of Administration view, do one of the following:

    • In the results pane, select one or more hosts with an agent version status of Unsupported, and then click Update Agent.

      noteNote
      So that performance is not adversely affected, it is recommended that you update hosts in batches of 10 to 25.

      The hosts will now have an agent version status of Up-to-date. This indicates that the update for these agents on the hosts is complete.

    • Select one or more hosts, with an agent communication status of Access Denied, and then do the following:

      1. In the Actions pane, click Reassociate.

        noteNote
        So that performance is not adversely affected, it is recommended that you update hosts in batches of 10 to 25.

        The hosts will now have an agent version status of Update Agent.

      2. Select one or more hosts with an agent version status of Update Agent, and then, in the Actions pane, click Update Agent.

        The hosts will now have an agent version status of Up-to-date. This indicates that the update for the agents on the hosts is complete.

      3. Repeat the preceding steps until the agents on all hosts have been updated.

  11. In the VMM Administrator Console, in Library view, do the following:

    • In the Resources pane, click a library server, and then, in the Actions pane, click Refresh.

    • If you have more than one library server, repeat the previous step for each library server.

  12. In the VMM Administrator Console, in the Managed Computers node of Administration view, do one of the following:

    • In the results pane, select one or more computers that have a role of Library and an agent communication status of Access Denied, and then, in the Actions pane, click Reassociate.

      The library servers will have an agent version status of Unsupported.

    • Select one or more computers that have a Library role and an agent version status of Unsupported, and then click Update Agent.

      The library servers will have an agent communication status of Responding and an agent version status of Up-to-date. This indicates that the update for the agents on the library servers is complete.

  13. In the VMM Administrator Console, in Hosts view, select all hosts with a status of Needs Attention, and then click Refresh.

    Hosts that have the Virtual Server 2005 R2 SP1 update installed will have a host status of OK. This indicates that the update for the hosts is complete.

    Hosts that do not have the Virtual Server 2005 R2 SP1 update installed will still have a host status of Needs Attention and the Update Virtual Server action will now be enabled.

  14. Select one or more hosts with a status of Needs Attention, and then in the Actions pane, click Update Virtual Server.

    The host will have a host status of OK. This indicates the update for the hosts is complete.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft