Upgrade View Composer Only - VMware View Manager 4.5 Upgrade Manual

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.
Procedure
1 On all View Connection Server instances except the one chosen to be the new standard
View Connection Server instance, uninstall View Connection Server and the View LDAP instance.
If the operating system on the virtual machine is Windows Server 2003, the View LDAP instance is called
ADAM Instance VMwareVDMDS. If the operating system is Windows Server 2008, the View LDAP
instance is called AD LDS Instance VMwareVDMDS.
2 On the virtual machine that hosts the standard, or master, View Connection Server instance, open a
command prompt and enter the following command to ensure that replication is not disabled.
repadmin /options localhost:389 -DISABLE_OUTBOUND_REPL -DISABLE_INBOUND_REPL
3 On the virtual machines that are to host the replica View Connection Server instances, run the
View Connection Server installer, select the View Replica Server installation option, and specify the host
name or IP address of the standard View Connection Server instance.
The replicated group of View Connection Server instances is recreated and their View LDAP objects are
consistent.

Upgrade View Composer Only

During the first maintenance window, after you upgrade View Connection Server, you can also upgrade
View Composer, which is hosted on the same virtual or physical machine as vCenter Server.
This procedure provides an overview of the tasks you must perform during the first maintenance window. To
complete some of these tasks, you might need step-by-step instructions found in other documents.
Prerequisites
Determine when to perform this procedure. Choose an available desktop maintenance window. For
n
information about how much time is required, see the vSphere Upgrade Guide.
Complete the tasks listed in
n
Verify that you have a domain user account with administrative privileges on the hosts that you will use
n
to run the installer and perform the upgrade.
If you are upgrading from View Composer 1.0, which is included with VMware View 3.0, determine
n
whether to let the installer wizard upgrade the View Composer database. You can choose to run the
command-line utility after the wizard finishes to upgrade the database manually and to create
SviConfig
a log of the upgrade.
N Upgrading directly from View Composer 1.0 to View Composer 2.5 is not supported. This
OTE
information is provided only to point out the product behavior that occurs if a database schema upgrade
is required.
VMware, Inc.
"Preparing for Upgrades of View Composer Only,"
Chapter 5 Upgrading VMware View Components
on page 19.
25