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 Upgrade Overview 2
Upgrading an enterprise View deployment involves several high-level tasks. Upgrading is a multistage
process in which procedures must be performed in a particular order. You upgrade View Composer before
upgrading View Connection Server and the other View servers.
During an upgrade, View does not support View Composer provisioning and maintenance operations.
Operations such as provisioning and recomposing linked-clone desktops are not supported during the
transitional period when any View servers are still running the earlier version. You can successfully perform
these operations only when all instances of View Connection Server and View Composer have been
upgraded.
You must complete the upgrade process in a specific order. Order is also important within each upgrade
stage.
NOTE This overview relates to upgrades for major, minor, and maintenance releases. For information about
patches, see Chapter 9, “Applying View Patches,” on page 63.
How many of the following tasks you need to complete depends on which components of View you use in
your deployment.
1 On the physical or virtual machines that host View Composer and VMware
®
vCenter Server™, make
backups and temporarily halt certain scheduled tasks. See “Preparing vCenter Server and View
Composer for an Upgrade,” on page 21.
For details about which versions of View are compatible with which versions of vCenter Server and
ESXi, see the VMware Product Interoperability Matrix at
http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
2 On the physical or virtual machines that host View Connection Server instances, make backups and
record various configuration and system settings. See “Preparing View Connection Server for an
Upgrade,” on page 23.
3 If you use security servers, make backups and record various configuration and system settings. See
“Preparing View Security Server for an Upgrade,” on page 24.
4 Upgrade View Composer on the existing host or migrate to a new machine. See “Upgrade View
Composer,” on page 25.
5 Upgrade View Connection Server instances that are not paired with security servers. See “Upgrade
View Connection Servers in a Replicated Group,” on page 34.
IMPORTANT After you upgrade a View Connection Server instance to the latest version, you cannot
downgrade that instance to an earlier version. After you upgrade all View Connection Server instances
in a replicated group, you cannot add another instance that runs an earlier version.
VMware, Inc.
11