You can find the full instructions in the upgrade guide, and the upgrade.exe on the Microsoft Connect site (Windows Live ID required) at: https://connect.microsoft.com/vmm/Downloads/DownloadDetails.aspx?DownloadID=8384

Before you upgrade, you must:

1.   Back up the VMM database.

2.   Uninstall the VMM agent using Add or Remove Programs for each managed host that is in a perimeter network.

3.   Uninstall the VMM Beta 2 server by using the "Retain data" option.

4.   Uninstall the Windows Remote Management (WinRM) component on the VMM server, library servers, and all hosts. To uninstall WinRM it by using Add or Remove Programs, you might have to select the Show updates box. Uninstall the component named "Windows Remote Management (KBHWMGMT)."

5.   Restart the computer and then install the version of WinRM available at http://go.microsoft.com/fwlink/?LinkId=84599.

Upgrade

To upgrade to the released version of Virtual Machine Manager, you must perform the following actions:

1.   Update the VMM database. Download and run upgrade.exe locally on the database server using an account that has DB Admin permission. Upgrade.exe is available at http://go.microsoft.com/fwlink/?LinkId=98304.

For example:

upgrade.exe –server localhost\MICROSOFT$VMM$ -database VirtualManagerDB

1.   Install the released version of Virtual Machine Manager 2007 server.

2.   Add back to the following three local user groups, any account you previously had:

a.         Virtual Machine Manager Administrators

b.         Virtual Machine Manager Self-Service Portals

c.         Virtual Machine Manager Servers

3.   Uninstall the Beta 2 version of the VMM Administrator Console, and then install the released version.

4.   Uninstall the Beta 2 version of the Self-Service Portal, and then install the released version of the Self-Service Portal.

5.   For each managed host that is in a trusted Active Directory domain with the VMM server, update the WinRM version. You must also update the agents. You can use the Update action in the VMM Administrator Console to update the VMM agent on the host. For instructions, see "How to Update an Agent on a Host" in Virtual Machine Manager Help. Alternatively, you can update the agent using Windows PowerShell -- Virtual Machine Manager command shell with the following commands:

Get-VMMServer <servername>
$credential = Get-Credential
Get-VMMManagedComputer | where {$_.VersionState -eq "NotSupported" } | Update-VMMManagedComputer -Credential $credential

6.   For each managed host that is on a perimeter network, perform the following actions:

a.         Re-install the agent locally, and create a new certificate.

b.         Add hosts to Virtual Machine Manager by using the new certificate you created. Be sure to destroy the credential after you add the host.

To find the server, SQL instance and DB name

·         Open the registry and navigate to the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager 2007 Server\Settings\Sql.

·         The database name can be found at

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager 2007 Server\Settings\Sql\DatabaseName

·         If the database is remote the following key value is non-zero

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager 2007 Server\Settings\Sql\OnRemoteServer

·         The DB server name can be found at

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager 2007 Server\Settings\Sql\MachineName

·         The instance name for the database can be found at:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager 2007 Server\Settings\Sql\InstanceName

Troubleshooting

If upgrade.exe fails to complete the upgrade, run the tool again. In an un-repairable situation, you can restore the database from a backup and then run upgrade.exe again.

Ensure that you are using credentials that have DB Owner permissions on the SQL database server.

 

Issue

Possible cause

Solution

Upgrade fails with a SQL server connection exception.

This error can occur for several reasons:

·      Incorrect server name

·      Incorrect instance name

·      Incorrect database name

·      Incorrect credentials

Try the upgrade again. For the default settings, run

upgrade.exe -server <machinename>\MICROSOFT$VMM$ -database VirtualManagerDB

If the upgrade still fails, contact product support.

Upgrade fails with the error: " Unable to access registry Software\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup"

OR

"Could not find the location of SQL Tools: Unable to access registry Software\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup."

SQL Server tools are not installed.

Install SQL Server tools from your VMM CD.

1.   Navigate to Prerequisites\SQLEXPR\1033 folder download the SQL Express Edition package at http://go.microsoft.com/fwlink/?LinkId=95583

2.   Restart your computer and run Upgrade.exe again.

Agent installation fails with error 441: "Agent communication is blocked since the version of Virtual Machine Manager agent on <computer name> is unsupported>. Or if <computer name> is a host then the version of Virtual Server is unsupported."

The version of WinRM that VMM uses has changed from Beta 2 to RTM. You must uninstall the old version and install the supported version before installing the agent (library, host or in converting a physical server).

1.   Using Add or Remove Programs, uninstall the WinRM component on the VMM server, any remote SQL database server, library servers and all hosts.

2.   Restart the computer and then install the version of WinRM that is available at http://go.microsoft.com/fwlink/?LinkId=84599

Administrator Console fails with error 1612: "The connection to the Virtual Machine Manager server <server name> was lost."

You are using a Beta 2 version of the  Administrator Console with a released version VMM server.

Upgrade the Administrator Console to the released version.

Unexpected Virtual Server service error after SQL Express SP2 was uninstalled.

Uninstalling SQL Express SP2 MSXML 6.0 Parser. Virtual Server has a dependency on MSXML 6.0 Parser.

1.   Stop the Virtual Server service.

2.   Download and install the version of MSXML 6.0 Parser that is supported by VMM at http://go.microsoft.com/fwlink/?LinkId=86867

3.   Start the Virtual Server service.