VMM: Upgrading from Beta 2

Now that VMM has RTMd, if you are a Beta 2 user, you may have some questions about the upgrade to RTM, assuming you want to retain your data?  If you do not want to retain your data, uninstall the Beta 2 version and perform a clean installation of the released version of VMM.

What happens to my virtual machines, checkpoints and hosts when I uninstall by using the "Retain data" option and then run upgrade.exe?

Virtual machines (VM), checkpoints and host associations are preserved. Your hosts that are joined to a domain, and the VMs and checkpoints on them, are discovered after you perform the upgrade and are displayed in the Administrator Console. Any hosts that are on a perimeter network are also displayed after you remove and then add the agent locally. Agents on hosts that are not on a perimeter network are displayed in the Administrator Console as requiring an update.

What happens to my jobs, Self-Service accounts and Virtual Machine Administrator accounts?

Jobs, Self-Service Trusted Web Server accounts and Virtual Machine Administrator accounts are deleted. You must add the Self-Service and Virtual Machine Administrator accounts after you perform the upgrade.

What happens to my library servers and library resources?

Library servers and library resources, such as hardware configurations and operating system profiles, are preserved and appear in the Administrator Console after you perform the upgrade.

What happens to self-service policies, tags, and custom properties on VMs?

Self-Service policies are preserved. Tags and custom properties on VMs that you have created are preserved. After you add the hosts, the VMs, with their custom properties and tags, are displayed in the Administrator Console. 

What happens to my reports?

The information that is used for the reports is preserved, but you must uninstall the Beta 2 Management Pack and install the Operations Manager 2007 Management Pack. 

Upgrade Requirements

SQL Server tools must be installed. If you plan to run the upgrade.exe on a server other than the VMM server, you must first install SQL Server Native Client and tools (SQL Server Tools). You can install the SQL Server Native Client and SQL Server Tools from your VMM CD under the Prerequisites\SQLEXPR\1033 folder, or you can download the SQL Express Edition package at http://go.microsoft.com/fwlink/?LinkId=95583.

The command-line upgrade tool, upgrade.exe, uses the Security Support Provider Interface (SSPI) to connect to the VMM database. The account that is used to run Upgrade.exe must have DB Owner permission on the database.

Upgrade Limitations

·      You must use an account with appropriate permissions to the VMM database in SQL Server, whether the database is installed locally on the VMM server or accessed remotely, to retain your data when you uninstall Beta 2.

·      You must locally uninstall the agents on hosts that are on a perimeter network before you upgrade the VMM server.

·      You should perform a clean install of all agent certificates.

·      Self-Service Portal associations are lost. After you upgrade, you must re-associate any Self-Service Portal in the Administrator Console.

If you have a large number of Beta 2 Self-Service Web Portals, you can run the following Windows PowerShell commands on the VMM server before you perform the upgrade to export the computer names to a text file:

Get-VMMServer <Server Name>

Get-SelfServiceWebServer | Out-File -FilePath <Text File Name>

After you perform the upgrade, run the following Windows PowerShell commands on the VMM server to import the computer names that you saved before the upgrade:

Get-VMMServer <Server Name>

Get-Content <Text File Name> | ForEach-Object -Process {Add-SelfServiceWebServer -ComputerName $_}

·      During the upgrade, members of the following local user groups are deleted:

·      Virtual Machine Manager Administrators

·      Virtual Machine Manager Self-Service Portals

·      Virtual Machine Manager Servers

After upgrade you must add the members of these groups back if you want them to be the same as they were before the upgrade.

·      Any firewall port exceptions that you entered during setup remain when you upgrade Virtual Machine Manager.

·      If you used the default SQL Server instance name (MSSQLSERVER) when you installed Beta 2, you must not specify the instance name when you run the upgrade tool. For example,

upgrade.exe -server <computer name> -database VirtualManagerDB

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

Comments (0)

Skip to main content