Upgrades
Table Of Contents
- View Upgrades
- Contents
- View Upgrades
- View Upgrade Overview
- System Requirements for Upgrades
- Upgrading View Server Components
- Upgrading View Composer
- Upgrading Horizon Connection Server
- Upgrading View Security Server
- Upgrading View Servers in a Cloud Pod Architecture Environment
- Upgrading View Servers to Allow HTML Access
- Upgrade vCenter Server
- Accept the Thumbprint of a Default SSL Certificate
- Using Horizon 7 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 1
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.
I With Horizon 6 version 6.2 and later versions, you can install View components to run in FIPS
mode. View does not support upgrading from a non-FIPS installation to a FIPS installation. View does
support upgrading from Horizon 6 version 6.2 in FIPS mode to Horizon 7 in FIPS mode. If you need to do a
fresh installation, see "Installing View in FIPS Mode," in the View Installation document.
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 specic order. Order is also important within each upgrade
stage.
N This overview relates to upgrades for major, minor, and maintenance releases. For information about
patches, see Chapter 7, “Applying View Patches,” on page 67.
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 20.
If you have a standalone View Composer, which is installed in a separate machine from vCenter Server,
you need only make a backup of the View Composer database and the View Composer TLS/SSL
certicate. You can schedule an upgrade of vCenter Server separately, if you want to also upgrade
vCenter Server.
For details about which versions of Horizon are compatible with which versions of vCenter Server and
ESXi, see the VMware Product Interoperability Matrix at
hp://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
2 Upgrade View Composer on the existing host or migrate to a new machine. See “Upgrade View
Composer,” on page 21.
3 On the physical or virtual machines that host View Connection Server instances, make backups and
record various conguration and system seings. See “Preparing Connection Server for an Upgrade,”
on page 32.
VMware, Inc.
7