Because vCenter Server and View Composer are often installed on the same virtual or physical machine, some preparation tasks apply to both.

If you are upgrading vCenter Server in addition to upgrading to Horizon View 5.2, you must consult the VMware 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 the version of vCenter Server that you want to upgrade to.

For example, vCenter Server 5.0 and later versions require two CPUs and must run on a 64-bit operating system. Because View Composer 2.6 was supported on 32-bit operating systems, upgrading might mean that you must upgrade vCenter Server and View Composer to a different machine.

2

Verify that the virtual or physical machine on which the current View Composer is installed meets the security requirements for the new version.

See Upgrade Requirements for View Composer.

3

Verify that the server on which vCenter Server is installed has a CA (certificate authority)-signed SSL server certificate installed and configured. After you upgrade View Connection Server, if vCenter Server does not use a CA-signed certificate, the default self-signed certificate is shown as invalid in View Administrator, and a message indicates that vCenter Server is unavailable. For information about replacing the default certificate for vCenter Server, see the vSphere Examples and Scenarios document.

4

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.

5

If the computer name is longer than 15 characters, shorten the name to 15 or fewer characters.

6

Back up the vCenter Server database and the View Composer database.

For instructions on performing a database backup, see the documentation from your database vendor.

7

Verify that the database server is compatible with the version of vCenter Server you plan to use.

For example, if the database server is Oracle 9i, you must upgrade.

8

Verify that the database is compatible with View Composer 5.2.

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.

9

Make a copy of the folder that contains SSL certificates.

This folder is located at %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter.

10

Document the IP address and system name of the machine on which vCenter Server is installed.

11

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.

12

If any desktop pools are set to refresh the OS disk on logoff, edit the Desktop/Pools settings for that pool and set Refresh OS disk on logoff to Never.

This setting prevents an error from occurring when the newly upgraded View Composer attempts to refresh a desktop that has not yet been upgraded to View Agent 5.2.

13

If any desktop pools are scheduled to do a refresh or recompose operation, cancel these tasks.

If you are upgrading only View Composer and are not upgrading vCenter Server, you must perform the following tasks:

1

Verify that the server on which View Composer is installed has a CA (certificate authority)-signed SSL server certificate installed and configured. After you upgrade View Connection Server, if View Composer does not use a CA-signed certificate, the default self-signed certificate is shown as invalid in View Administrator, and a message indicates that View Composer is unavailable. For information about replacing the default certificate for View Composer, see the topic "Configuring SSL Certificates for View Servers" in the VMware Horizon View Installation document. You must run the SviConfig RelaceCertificate command.

2

Verify that the virtual or physical machine on which the current View Composer is installed meets the security requirements for the new version.

See Upgrade Requirements for View Composer.

3

If View Composer is installed in a virtual machine, take a snapshot of the virtual machine.

For instructions on taking snapshots, see the vSphere Client online help.

4

Back up the 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 is compatible with View Composer 5.2.

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.

6

Make a copy of the folder that contains SSL certificates.

This folder is located at %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter.

7

Document the IP address and system name of the machine on which vCenter Server is installed.

8

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.

9

If any desktop pools are set to refresh the OS disk on logoff, edit the Desktop/Pools settings for that pool and set Refresh OS disk on logoff to Never.

This setting prevents an error from occurring when the newly upgraded View Composer attempts to refresh a desktop that has not yet been upgraded to View Agent 5.2.

10

If any desktop pools are scheduled to do a refresh or recompose operation, cancel these tasks.