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
4 Use View Administrator to edit the vCenter Server settings, navigate to the Storage tab, and select
Reclaim VM disk space.
For instructions on editing server settings, click the Help button in View Administrator.
5 Use View Administrator to edit the pool settings, navigate to the Advanced Storage section, select
Reclaim VM disk space, and set the threshold for space reclamation to 1GB.
Upgrade Tasks If You Use VMware Virtual SAN Datastores
Starting with vSphere 5.5 Update 1, you can use the Virtual SAN feature for high-performance storage and
policy-based management.
With Virtual SAN, the locally attached physical storage disks available on a cluster of vSphere hosts are
aggregated into one virtual datastore. You specify this datastore when creating a desktop pool, and the
various components, such as virtual machine files, replicas, user data, and operating system files, are placed
on the appropriate solid-state drive (SSD) disks or direct-attached hard disks (HDDs).
View defines virtual machine storage requirements, such as capacity, performance, and availability, in the
form of default storage policy profiles, depending on the pool settings used. Storage is provisioned and
automatically configured according to the assigned policies.
NOTE The space reclamation feature is not supported if your virtual machine desktops are hosted on
Virtual SAN datastores.
Upgrade from a Non-Virtual SAN Datastore to a Virtual SAN Datastore
Upgrading pools to use VMware Virtual SAN datastores involves changing a pool setting and then
rebalancing the pool.
The tasks outlined in this procedure describe upgrading from a non-Virtual SAN datastore to a Virtual SAN
datastore. Upgrading from Virtual SAN datastore on a vSphere 5.5 or earlier cluster (a Tech Preview
feature) is not supported.
IMPORTANT Because this procedure involves recomposing the desktop pool, any changes that end users
have made to the operating system disk will be lost.
Prerequisites
n
Verify that all ESXi hosts in the cluster used for the pool are upgraded to 5.5 Update 1 or later and that
they meet the system requirements for the Virtual SAN feature. VMware recommends that you
upgrade to vSphere 6.0 or later because the Virtual SAN feature available with vSphere 6.0 and later
releases contains many performance improvements over the feature that was available with vSphere 5.5
Update 1. With vSphere 6.0 this feature also has broader HCL (hardware compatibility) support.
For information about upgrades, see Chapter 6, “Upgrade ESXi Hosts and Their Virtual Machines,” on
page 45 and see the VMware vSphere Upgrade Guide. For information about Virtual SAN requirements
and upgrades, see the Administering VMware Virtual SAN document.
n
In vCenter Server, verify that the following privileges are added to the Composer role:
Profile-Driven Storage: All
Folder: Create Folder & Delete Folder
Host: Configuration: Advanced settings
Procedure
1 Use vCenter Server 5.5 Update 1 or later to enable Virtual SAN for the vSphere cluster.
For more information, see the vSphere Storage document.
Chapter 8 Post-Upgrade Tasks to Enable New Features in Your View Setup
VMware, Inc. 55