Upgrades
Table Of Contents
- View Upgrades
- Contents
- View Upgrades
- Component Compatibility Matrix
- View Upgrade Overview
- System Requirements for Upgrades
- Preparing for a View Upgrade
- Upgrading View Server Components
- Upgrade View Composer
- Upgrade View Connection Servers in a Replicated Group
- Upgrade View Security Servers and Their Paired View Connection Servers
- Upgrading View Servers in a Cloud Pod Architecture
- Upgrade vCenter Server
- Using View Group Policy Administrative Template Files
- Upgrade ESXi Hosts and Their Virtual Machines
- Upgrading Remote Desktops and Horizon Client
- Post-Upgrade Tasks to Enable New Features in Your View Setup
- Applying View Patches
- Upgrading vSphere Components Separately in a View Environment
- Index
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 database events.
8 Make a copy of the folder that contains SSL certificates.
This folder is located at %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter.
9 Document the IP address and system name of the machine on which vCenter Server is installed.
10 For all linked-clone desktop pools, use View Administrator to 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.
11 If any desktop pools are set to refresh the OS disk on logoff, use View Administrator to edit the
Desktop/Pools settings for that pool and set Delete or refresh machine on logoff to Never.
This setting prevents an error from occurring when the newly upgraded View Composer attempts to
refresh a desktop on which View Agent has not yet been upgraded.
12 If any desktop pools are scheduled to do a refresh or recompose operation, use View Administrator to
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 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.
2 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.
3 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.
4 Verify that the database is compatible with the new version of View Composer.
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 database events.
5 Make a copy of the folder that contains SSL certificates.
This folder is located at %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter.
6 Document the IP address and system name of the machine on which vCenter Server is installed.
7 For all linked-clone desktop pools, use View Administrator to 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.
View Upgrades
22 VMware, Inc.