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
6 If you use physical PCs or virtual machines as Microsoft RDS hosts, to provide remote desktops or
applications, download and run the installer for the new version of View Agent on these machines.
You can download the installer from the VMware Web site.
7 If you use physical PCs as desktop sources, download and run the installer for the new version of View
Agent on these physical machines.
You can download the installer from the VMware Web site.
8 Use a Horizon Client that has not been upgraded to verify that you can log in to the upgraded remote
desktop sources with your old client software.
What to do next
If you use View Composer desktop pools, recompose or recreate the pools. See “Upgrade View Composer
Desktop Pools,” on page 50.
Upgrade clients. See “Upgrade the Client Application,” on page 51.
Upgrade View Composer Desktop Pools
Part of the final phase of a View upgrade includes upgrading View Composer desktop pools.
Upgrading pools that were created with View Composer requires that you use a snapshot taken after
upgrading View Agent on the parent virtual machine.
IMPORTANT If you use View Composer linked clones and you want to use the space reclamation feature
available with vSphere 5.1 and later virtual machines, you must configure certain settings in View LDAP
and in View Administrator, in addition to performing the steps in this procedure. For a complete list of
tasks, see “Tasks for Upgrading Desktop Pools to Use Space Reclamation,” on page 54.
NOTE If you are also upgrading the virtual hardware version, such as upgrading to virtual hardware
version 8 or later, included with vSphere 5 or later, the snapshot of the upgraded parent virtual machine is
used to upgrade the virtual hardware version of the rest of the virtual machines in the linked-clone pool.
Upgrading in this way, from one virtual hardware version (or compatibility level) to a higher version, is
supported. You cannot, however, recompose linked clones to a lower hardware version than their current
version. For example, you cannot recompose hardware version 8 clones to a parent virtual machine that is
hardware version 7.
Prerequisites
n
Complete the procedure described in “Upgrade View Composer,” on page 25.
n
Complete the procedure described in “Upgrade View Connection Servers in a Replicated Group,” on
page 34.
n
If you are also upgrading ESXi hosts and virtual machines, complete the procedure described in
Chapter 6, “Upgrade ESXi Hosts and Their Virtual Machines,” on page 45.
For information about the vSphere versions that are required for various new features, see Table 6-1.
n
Complete the procedure described in “Upgrade View Agent,” on page 48 for upgrading the agent in the
parent virtual machine.
IMPORTANT If you are upgrading from View 5.1.x or earlier, and you use Sysprep, and your end users
will connect USB devices to their remote desktops, you must follow the procedure described in the
VMware Knowledge Base, at http://kb.vmware.com/kb/2051801. Otherwise, after you upgrade to View
Agent 6.0, the USB redirection feature might not work.
View Upgrades
50 VMware, Inc.