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.
Preparing for Upgrades of View Composer Only
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,” on page 15.
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.
VMware Horizon View Upgrades
22 VMware, Inc.
Komentarze do niniejszej Instrukcji