Preparing Vcenter Server And View Composer For An Upgrade - VMware View Manager 4.5 Upgrade Manual

VMware View Upgrade Guide
Determine if your company has written any batch files or scripts that run against the View database on
n
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
n
balancers.

Preparing vCenter Server and View Composer for an Upgrade

Because vCenter Server and View Composer are installed on the same virtual or physical machine, some
preparation tasks apply to both.
Preparing for Upgrades That Include vSphere
If you are upgrading to vCenter Server 4.1 in addition to upgrading to VMware View 4.5 with
View Composer 2.5, you must consult the vSphere Upgrade Guide and perform the following tasks in the
following order:
1 Verify that the virtual or physical machine meets the system requirements for vCenter Server 4.1.
For example, vCenter Server 4.1 requires two CPUs and must run on a 64-bit operating system. Because
View Composer 1.0 and 2.0.x were supported only on 32-bit operating systems, upgrading to vSphere 4.1
means that you must upgrade View Composer to a different machine.
2 If vCenter Server is installed in a virtual machine, take a snapshot of the virtual machine.
For instructions on taking snapshots, see the vSphere Client online help.
3 If the computer name is longer than 15 characters, shorten the name to 15 or fewer characters.
You use this name first on the 32-bit VirtualCenter Server 2.5 host or the vCenter Server 4.0 host, and then
you use this name when you migrate to the 64-bit vCenter Server 4.1 host. You also use the same IP address.
4 Back up the VirtualCenter or vCenter Server database and the View Composer database.
For instructions on performing a database backup, see the documentation from your database vendor.
5 Verify that the database server is compatible with vCenter Server 4.1.
For example, if the database server is Oracle 9i, you must upgrade to Oracle 10g or 11g. If you plan to
migrate vCenter Server from a 32-bit operating system to a 64-bit operating system and the database will
be on the same system, verify that the database is supported on 64-bit operating systems.
6 Verify that the database is compatible with View Composer 2.5.
View Composer supports a subset of the database servers that vCenter Server supports. If you are already
using vCenter Server with a database server that is not supported by View Composer, continue to use that
database server for vCenter Server and install a separate database server to use for View Composer and
View Manager database events.
7 Make a copy of the folder that contains SSL certificates.
This folder is located at
8 Document the IP address and system name of the machine on which vCenter Server is installed.
9 For all linked-clone desktop pools, disable provisioning of new virtual machines.
Because View Composer might be upgraded during a different maintenance window than its desktop
pools, provisioning must be postponed until both components are upgraded.
18
%ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter
.
VMware, Inc.