Part of the final phase of a View upgrade includes upgrading View Composer desktop pools.
About this task
Upgrading pools that were created with View Composer requires that you use a snapshot taken after upgrading View Agent on the parent virtual machine.
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.
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.
Complete the procedure described in Upgrade View Composer.
Complete the procedure described in Upgrade View Connection Servers in a Replicated Group.
If you are also upgrading ESXi hosts and virtual machines, complete the procedure described in Upgrade ESXi Hosts and Their Virtual Machines.
For information about the vSphere versions that are required for various new features, see Virtual Hardware Versions Required for Specific Features.
Complete the procedure described in Upgrade View Agent 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.
Plan maintenance windows carefully so that recreating and recomposing desktop pools will not overwhelm the storage array and ESXi hosts.
- If you disabled provisioning of new virtual machines in preparation for the upgrade, enable provisioning again.
- To turn on the 3D rendering feature, edit the pool to configure the following settings:
Set the pool to use the PCoIP display protocol.
Set Allow users to choose protocol to No.
Turn on the 3D Rendering feature.
- To enable the space reclamation feature available with vSphere 5.1 virtual machines, in the Advanced Storage section of pool settings, select Reclaim VM disk space, and set the threshold for space reclamation to 1GB.
- To enable View Storage Accelerator, available with vSphere 5.0 or later virtual machines, in the Advanced Storage section of pool settings, verify that the Use View Storage Accelerator check box is selected.
View Storage Accelerator can improve performance during boot storms and anti-virus scanning I/O storms by allowing ESXi hosts to cache common virtual machine disk data.Important:
This feature is turned on by default. View Storage Accelerator requires 1GB of RAM per ESXi host.
- Use the snapshot you created after upgrading the parent virtual machine to recompose desktop pools.
- If you changed the Refresh OS disk on logoff setting for a pool to Never in preparation for the upgrade, change the setting back to reflect the appropriate refresh policy.
- If you canceled any refresh or recompose operations for any desktop pools, schedule the tasks again.
What to do next
Upgrade the clients. See Upgrade the Client Application.
Perform the tasks listed in Post-Upgrade Tasks to Enable New Features in Your View Setup that apply to your setup.