5.0

Procedure
1 Verify that an upgraded instance of View Connection Server is running and is accessible to the new
machine where you plan to install View Connection Server.
When you install View Connection Server on the new host, you will point to this existing instance.
2 On the new machine, install a replicated instance of View Connection Server.
The View LDAP on the new instance will replicate that of the upgraded source instance.
3 If applicable, uninstall View Connection Server from the old host by using the Windows Add/Remove
Programs utility.
4 In View Administrator, go to View Configuration > Servers and determine whether the View Connection
Server instance that was uninstalled still appears in the list.
5 If the uninstalled View Connection Server instance still appears in the list, use a vdmadmin command to
remove it.
vdmadmin.exe -S -s server_name -r
In this example, server_name is the host name or IP address of the View Connection Server host. For more
information about the vdmadmin command-line tool, see the VMware View Administration document.
A new instance of View Connection Server is added to a group and an old instance is removed.
What to do next
If you are upgrading from View 4.0.x or earlier and the upgrade is successful, install and configure the event
database. For instructions, see the VMware View Installation document. If you are upgrading from View 4.5.x
or 4.6.x, you probably installed the event database when you installed View 4.5.x or 4.6.x. The event database
does not require an upgrade for View 5.0.
Upgrade the other View server components. If you use View Composer, see “Upgrade View Composer
Only,” on page 31 or “Upgrade to View Composer 2.7 and vCenter Server 5.0 on a Different Machine,” on
page 35. If you use VMware View with Local Mode, see “Upgrade View Transfer Server,” on page 29.
If you ever reinstall View Connection Server on a Windows Server 2008 operating system and you have a data
collector set configured to monitor performance data, stop the data collector set and start it again.
Create a Replicated Group After Reverting View Connection Server to a Snapshot
If an upgrade fails, or if for some other reason, you must revert a virtual machine that hosts View Connection
Server to a snapshot, you must uninstall the other View Connection Server instances in the group and recreate
the replicated group.
If you revert one View Connection Server virtual machine to a snapshot, the View LDAP objects in the database
of that virtual machine are no longer consistent with the View LDAP objects in the databases of the other
replicated instances. After you revert to a snapshot, the following event is logged in the Windows Event log,
in the VMwareVDMDS Event log (Event ID 2103): The Active Directory Lightweight Directory Services
database has been restored using an unsupported restoration procedure. The reverted virtual machine
stops replicating its View LDAP.
If you find it necessary to revert to a snapshot, you must uninstall other View Connection Server instances and
uninstall the View LDAP on those virtual machines and then reinstall replica instances.
Prerequisites
Determine which View Connection Server instance is to be the new standard, or master,
View Connection Server. This Connection Server has the desired View configuration data.
VMware View Upgrades
28 VMware, Inc.