Before you upgrade View Connection Server or before you upgrade any of the vSphere components that View Connection Server relies on, you must perform several tasks to ensure that these upgrades are successful.
Verify that the virtual or physical machine on which the current View Connection Server instance is installed meets the system requirements for the new version.
If View Connection Server is installed in a virtual machine, take a snapshot of the virtual machine. If you have a replicated group of View Connection Server instances, take a snapshot of only one View Connection Server instance.
For instructions on taking snapshots, see the vSphere Client online help. If you ever need to revert to this snapshot and if you have other View Connection Server instances in a replicated group, you must uninstall those instances before you revert the master to the snapshot. After you revert, you can reinstall the replicated instances and point to the instance you reverted.
You can label the snapshot Upgrade Preparation Phase.
If your deployment currently uses the Local Mode feature, ask end users to check in their Local Mode desktops, or use View Administrator to roll back the Local Mode desktops so that no desktops are shown as checked out in View Administrator.Important:
If any Local Mode desktops are checked out at the time you run the View Connection Server installer to install the upgrade, the upgrade will fail.
If your deployment currently uses the Local Mode feature, open View Administrator, go to, and remove all Transfer Server instances.
Open View Administrator and document all the global settings and settings for desktops and pools: Pools section and Desktops section in the Inventory tree, and the Global Settings section in the View Configuration tree.
For example, take a screen shot of the applicable settings. If you have multiple instances of View Connection Server in a replicated group, you need only document the settings for one instance.
Use the vdmexport.exe utility to back up the LDAP database.
For instructions, see the administration guide for your current version of the View Administration document. If you have multiple instances of View Connection Server in a replicated group, you need only export the data from one instance.
Document the IP address and system name of the machine on which View Connection Server is installed.
Determine if your company has written any batch files or scripts that run against the View database on the View Connection Server instance, and if so, document their names and locations.
If you use load balancers for View Connection Server, document the configuration settings for the load balancers.