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
Procedure
1 Upgrade vCenter Server and your ESXi hosts to vSphere 6 or later, as described in the chapter about
upgrading the Virtual SAN cluster in the Administering VMware Virtual SAN document, available in the
vSphere 6.0 documentation center.
At this point, the desktop pool is still using Virtual SAN disk format 1, and the virtual machines and
VMware Tools have not yet been upgraded to vSphere 6.0 virtual hardware version 11.
2 Upgrade the desktop pool to the latest version, as described in “Upgrade View Agent,” on page 48 and
“Upgrade View Composer Desktop Pools,” on page 50.
This process includes installing the latest version of View Agent on the parent virtual machine, virtual
machine template, or full-clone virtual machines in the pool. For linked-clone pools, the process also
includes taking a snapshot and recomposing the pool.
The virtual machines in the desktop pool now have View Agent 6.1 or later installed, and the virtual
machines still reside on Virtual SAN datastores available with vSphere 5.5 Update 1. At this point, the
desktop pool is using Virtual SAN disk format 1.
3 Use the command-line RVC tool to upgrade the Virtual SAN disk format version from version 1 to
version 2.
For complete instructions, see the topic "Upgrading the Virtual SAN Disk Format," in the upgrade
chapter of the Administering VMware Virtual SAN document.
Ruby vSphere Console (RVC) is a Ruby-based command-line console for VMware ESXi hosts and
vCenter Server. RVC is included in both the Windows and Linux versions of vCenter Server. For
detailed information about using the RVC commands, see the RVC Command-line Reference Guide.
4 After the disks are upgraded for all the ESXi hosts in the cluster, on the parent virtual machine, virtual
machine template, or full-clone virtual machines in the pool, complete the following tasks in the
following order.
a If the parent virtual machine is on a Virtual SAN datastore, delete all snapshots.
The virtual machine cannot start using the new snapshot format available with Virtual SAN disk
format 2 until all previous redolog-based snapshots are deleted. If the virtual machine is not on a
Virtual SAN datastore, you are not required to delete the snapshots.
b Upgrade the virtual machine hardware to version 11 and upgrade VMware Tools.
5 For linked-clone pools, take a new snapshot and recompose the desktop pool using the new snapshot.
The desktop pool is now using Virtual SAN disk format 2.
Upgrade from Horizon View 5.3.1 on a Virtual SAN Datastore
Horizon 6.0 introduced some new default storage policies for Virtual SAN. These policies are not
automatically applied to existing virtual machine desktops created on Virtual SAN by View 5.3.1 (or 5.3.x
maintenance releases) after the desktop pool is upgraded.
In addition, when you upgrade from View 5.3.1, the Use VMware Virtual SAN pool setting will not
automatically be enabled, even if the pool is on a Virtual SAN datastore. You have the following upgrade
options:
n
If you continue to use VMware vSphere 5.5 Update 1, after upgrading, continue to use the default
storage policies that were used with View 5.3.1. If you choose this option, edit the pool settings so that
Use VMware Virtual SAN is enabled.
Chapter 8 Post-Upgrade Tasks to Enable New Features in Your View Setup
VMware, Inc. 57