View Upgrades Modified on 4 JAN 2018 VMware Horizon 7 7.
View Upgrades You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about this documentation, submit your feedback to docfeedback@vmware.com VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com Copyright © 2009–2018 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc.
Contents View Upgrades 5 1 View Upgrade Overview 6 2 System Requirements for Upgrades 9 Compatibility Matrix for Various Versions of Horizon 7 Components View Composer Requirements 9 10 Supported Operating Systems for View Composer 10 Hardware Requirements for Standalone View Composer 11 Database Requirements for View Composer and the Events Database Upgrade Requirements for View Composer Horizon Connection Server Requirements 11 12 13 Hardware Requirements for Horizon Connection Server 13 Su
View Upgrades Using Horizon 7 Group Policy Administrative Template Files 47 4 Upgrade ESXi Hosts and Their Virtual Machines 49 5 Upgrading Remote Desktops and Horizon Client 52 Security-Related Requirements for Remote Desktop Upgrade Upgrade RDS Hosts That Provide Session-Based Desktops Upgrade View Agent or Horizon Agent 52 54 Upgrade View Composer Desktop Pools Upgrade the Client Application 52 56 58 6 Post-Upgrade Tasks to Enable New Features in Your View Setup 60 Change the JMS Message Securit
View Upgrades View Upgrades provides instructions for upgrading from the latest maintenance releases of Horizon View 5.3, VMware Horizon™ 6 (with View), or VMware Horizon 6 version 6.1 or 6.2, to VMware Horizon 7. You can also use this guide when you upgrade to View maintenance and patch releases. ® If you are also upgrading your version of VMware vSphere , this guide tells you which steps of that upgrade to do at various stages of the View upgrade.
1 View Upgrade Overview 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. Important 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 Upgrades 2 Upgrade View Composer on the existing host or migrate to a new machine. See Upgrade View Composer. 3 On the physical or virtual machines that host View Connection Server instances, make backups and record various configuration and system settings. See Preparing Connection Server for an Upgrade. If you have multiple View Connection Server instances in a replicated group, make backups and record configuration settings for only one instance in the group.
View Upgrades 10 If you currently use Windows Terminal Services servers as desktop sources, upgrade to Windows Server 2008 R2 or later and verify that the RDS Host role is installed. See Upgrade RDS Hosts That Provide Session-Based Desktops 11 Upgrade the Horizon™ Agent or View Agent™ software that runs on the physical or virtual machines that are used as desktop sources, as full-clone desktops in a pool, and as individual desktops in a manual pool. See Upgrade View Agent or Horizon Agent.
System Requirements for Upgrades 2 Hosts and virtual machines in a Horizon 7 deployment must meet specific hardware and operating system requirements.
View Upgrades Table 2‑1. Compatibility Matrix for VMware Horizon 7 and Earlier Versions of View Components Connection Server: Earlier Version Security Server: Earlier Version View Composer: Earlier Version View Agent: Earlier Version Horizon Client (Windows): Earlier Version Connection Server 7.0 Only during upgrade Only if paired before upgrade No Only during upgrade Yes Security Server 7.0 (PCoIP and RDP) No N/A No Only during upgrade Yes View Composer 7.
View Upgrades Table 2‑2. Operating System Support for View Composer Operating System Version Edition Windows Server 2008 R2 SP1 64-bit Standard Enterprise Datacenter Windows Server 2012 R2 64-bit Standard Datacenter Windows Server 2016 64-bit Standard Datacenter Note Windows Server 2008 R2 with no service pack is no longer supported. If you plan to install View Composer on a different physical or virtual machine than vCenter Server, see Hardware Requirements for Standalone View Composer.
View Upgrades If a database server instance already exists for vCenter Server, View Composer can use that existing instance if it is a version listed in the VMware Product Interoperability Matrixes at http://www.vmware.com/resources/compatibility/sim/interop_matrix.php. If a database server instance does not already exist, you must install one. View Composer supports a subset of the database servers that vCenter Server supports.
View Upgrades n To enhance the security of View Composer, disable the weak cryptographic cipher suites on the Windows Server computer on which the View Composer service is installed. See "Disable Weak Ciphers in SSL/TLS" in the View Installation document. n You might need to make security protocol configuration changes to continue to be compatible with vSphere. If possible, apply patches to ESXi and vCenter Server to support TLSv1.1 and TLSv1.2 before upgrading View Composer.
View Upgrades The following operating systems support all Horizon Connection Server installation types, including standard, replica, and security server installations. Table 2‑5.
View Upgrades Also, updated clients expect information about the server's certificate to be communicated as part of the SSL handshake between client and server. Often updated clients do not trust self-signed certificates. For complete information about security certificate requirements, see "Configuring SSL Certificates for View Servers" in the View Installation guide.
View Upgrades Supported Operating Systems for Horizon Agent The Horizon Agent component (called View Agent in previous releases) assists with session management, single sign-on, device redirection, and other features. You must install Horizon Agent on all virtual machines, physical systems, and RDS hosts. The types and editions of the supported guest operating system depend on the Windows version.
Upgrading View Server Components 3 The server components that you must upgrade include View Connection Server, replicated servers, and security servers. Depending on the optional components you use, you might also need to upgrade View Composer. If you spread the upgrade tasks across multiple maintenance windows, you can verify success or discover issues at each phase of the process. VMware recommends upgrading all server components during the first maintenance window.
View Upgrades Upgrading View Composer 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. Note Before you can use the View Composer 6.
View Upgrades 8 Make a copy of the folder that contains SSL certificates. This folder is located at %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter. 9 Document the IP address and system name of the machine on which vCenter Server is installed. 10 For all linked-clone desktop pools, use View Administrator to disable provisioning of new virtual machines.
View Upgrades 7 If any desktop pools are set to refresh the OS disk on logoff, use View Administrator to edit the Desktop/Pools settings for that pool and set Delete or refresh machine on logoff to Never. This setting prevents an error from occurring when the newly upgraded View Composer attempts to refresh a desktop on which View Agent has not yet been upgraded. 8 If any desktop pools are scheduled to do a refresh or recompose operation, use View Administrator to cancel these tasks.
View Upgrades What to do next If you need to do a manual upgrade of the database schema, see Run SviConfig to Manually Upgrade the Database. If you have an older version of vCenter Server, see Enable TLSv1.0 on vCenter and ESXi Connections from View Composer. At your next maintenance window, continue with the View upgrade. See Upgrade Connection Servers in a Replicated Group. Enable TLSv1.0 on vCenter and ESXi Connections from View Composer Horizon 7 and later components have the TLSv1.
View Upgrades 8 If the View Composer host is a 64-bit machine, navigate to HKLM\SOFTWARE\WOW6432Node\VMware, Inc\VMware View Composer. 9 Create or edit the String value EnableTLS1.0 and set it to 1. 10 Restart the VMware Horizon View Composer service. TLSv1.0 connections from View Composer to ESXi hosts are now enabled. Enable Digest Access Authentication for View Composer Effective in Horizon 7 version 7.0.
View Upgrades When you upgrade View Composer to a version with an updated database schema, an installer prompt asks if you want the wizard to upgrade the database. If you choose not to use the installer wizard, you must use the SviConfig utility to upgrade the database and migrate the existing data. Using the SviConfig command-line utility has the following advantages: n This utility returns result codes and creates a log of the database upgrade to simplify troubleshooting if the upgrade fails.
View Upgrades 3 Run the SviConfig databaseupgrade command. sviconfig -operation=databaseupgrade -DsnName=target_DSN -Username=database_administrator_username For example: sviconfig -operation=databaseupgrade -dsnname=LinkedClone -username=Admin 4 When prompted, supply the password. A successful operation displays output that shows the upgrade steps. Establishing database connection. Database connection established successfully. Upgrading database. Load data from SVI_VC_CONFIG_ENTRY table.
View Upgrades Table 3‑1. Result Codes for the databaseupgrade Command (Continued) Code Description 3 The driver for the database is not supported. 4 An unexpected problem arose and the command failed to complete. 14 Another application is using the View Composer service. Shut down the service before executing the command. 15 A problem arose during the restore process. Details are provided in the onscreen log output. 17 Unable to upgrade the database data.
View Upgrades Migrate View Composer to Another Machine In some situations, you might need to migrate a VMware Horizon View Composer service to a new Windows Server virtual or physical machine. For example, you might migrate View Composer and vCenter Server to a new ESXi host or cluster to expand your View deployment. In addition, View Composer and vCenter Server do not have to be installed on the same Windows Server machine.
View Upgrades Guidelines for Migrating View Composer The steps you take to migrate the VMware Horizon View Composer service depend on whether you intend to preserve existing linked-clone virtual machines. To preserve the linked-clone virtual machines in your deployment, the VMware Horizon View Composer service that you install on the new virtual or physical machine must continue to use the existing View Composer database.
View Upgrades Prerequisites n Familiarize yourself with the View Composer migration requirements. See Guidelines for Migrating View Composer. n Familiarize yourself with the steps for migrating the RSA key container to the new VMware Horizon View Composer service. See Prepare a Microsoft .NET Framework for Migrating RSA Keys and Migrate the RSA Key Container to the New View Composer Service. n Familiarize yourself with installing the VMware Horizon View Composer service.
View Upgrades 7 In View Administrator, configure the new View Composer settings. a In View Administrator, select View Configuration > Servers. b On the vCenter Servers tab, select the vCenter Server instance that is associated with this View Composer service and click Edit. c In the View Composer Server Settings pane, click Edit and provide the new View Composer settings.
View Upgrades Procedure 1 In View Administrator, remove View Composer from View Administrator. a Select View Configuration > Servers. b On the vCenter Servers tab, select the vCenter Server instance that is associated with the View Composer service and click Edit. c In the View Composer Server Settings pane, click Edit. d Select Do not use View Composer and click OK. 2 Uninstall the VMware Horizon View Composer service from the current machine.
View Upgrades Prerequisites Download the .NET Framework and read about the ASP.NET IIS registration tool. Go to http://www.microsoft.com/net. Procedure 1 Install the .NET Framework on the physical or virtual machine on which the VMware Horizon View Composer service associated with the existing database is installed. 2 Install the .NET Framework on the destination machine on which you want to want to install the new VMware Horizon View Composer service.
View Upgrades The -exp option creates an exportable key pair. If a future migration is required, the keys can be exported from this machine and imported to another machine. If you previously migrated the keys to this machine without using the -exp option, you can import the keys again using the -exp option so that you can export the keys in the future. The registration tool imports the key pair data into the local key container.
View Upgrades For instructions on taking snapshots, see the vSphere Client online help. If you ever need to revert to this snapshot and if you have other Connection Server instances in a replicated group, you must uninstall those instances before you revert the master to the snapshot. After you revert, you can reinstall the replicated instances and point to the instance you reverted. You can label the snapshot Upgrade Preparation Phase.
View Upgrades For Connection Server instances that are paired with security servers, use the procedure described in Upgrade View Security Servers and Their Paired View Connection Servers. Note This procedure describes an in-place upgrade. To migrate to a different machine, see Upgrade to the Latest Version of Connection Server on a Different Machine. Prerequisites n Determine when to perform this procedure. Choose an available desktop maintenance window.
View Upgrades Procedure 1 If you are using a load balancer to manage a group of Connection Server instances, disable the server that hosts the Connection Server instance that you are about to upgrade. 2 Log in to Horizon Administrator and disable the Connection Server instance that you are about to upgrade. 3 a Go to View Configuration > Servers and click the Connection Servers tab. b Select the Connection Server instance in the list and click the Disable button above the table.
View Upgrades 9 Repeat the previous steps to upgrade each Connection Server instance in the group. Important If you do not upgrade all Connection Server instances in a replicated group, the health indicators in the Horizon Administrator dashboard might show that one or more instances are in an error state. This situation arises because different versions supply different kinds of data. The solution is to upgrade all instances in the replicated group. 10 Use the vdmexport.
View Upgrades Enable TLSv1.0 on vCenter Connections from Connection Server Horizon 7 and later components have the TLSv1.0 security protocol disabled by default. If your deployment includes an older version of vCenter Server that supports only TLSv1.0, you might need to enable TLSv1.0 for Connection Server connections after installing or upgrading to Connection Server 7.0 or a later release. Some earlier maintenance releases of vCenter Server 5.1, and 5.5 support only TLSv1.
View Upgrades Upgrade to the Latest Version of Connection Server on a Different Machine As part of your upgrade, you can migrate Connection Server to a new machine. Prerequisites n Upgrade at least one existing Connection Server instance to the latest version. See Upgrade Connection Servers in a Replicated Group. During this upgrade, your existing View LDAP will be upgraded. n Verify that the new physical or virtual machine meets the system requirements for installing Connection Server.
View Upgrades A new instance of Connection Server is added to a group and an old instance is removed. What to do next If you have an older version of vCenter Server, see Enable TLSv1.0 on vCenter Connections from Connection Server. Upgrade the other Horizon 7 server components. If you ever reinstall Connection Server on a server that has a data collector set configured to monitor performance data, stop the data collector set and start it again.
View Upgrades Upgrading Security Servers If your deployment uses load balancers to manage multiple security servers, you can perform an upgrade of the Connection Server infrastructure with zero down time. Note To use Unified Access Gateway appliances instead of security servers, you must upgrade the Connection Server instances to Horizon 6 version 6.
View Upgrades This procedure is designed to upgrade one security server and its paired View Connection Server instance before moving on to upgrade the next security server and its paired View connection Server instance. This strategy allows for zero down time. If the instance is not paired with a security server, use the procedure Upgrade Connection Servers in a Replicated Group. The first few steps of this procedure involve upgrading the View Connection Server instance.
View Upgrades Procedure 1 If you are using a load balancer to manage security servers that are paired with Connection Server instances, disable the security server that is paired with the Connection Server instance you are about to upgrade. 2 Upgrade the View Connection Server instance that is paired with this security server. Follow steps 2 through 6 of Upgrade Connection Servers in a Replicated Group.
View Upgrades 9 In View Administrator, go to View Configuration > Servers > Security Servers tab and remove any duplicate security servers from the list. The automated security server pairing mechanism can produce duplicate entries in the Security Servers list if the full system name does not match the name that was assigned when the security server was originally created. 10 Use the vdmexport.exe utility to back up the newly upgraded View LDAP database.
View Upgrades Upgrading a Cloud Pod Architecture Environment The Cloud Pod Architecture feature uses standard Horizon 7 components to provide cross-data center administration. With the Cloud Pod Architecture feature, you link together multiple pods to provide a single large desktop and application brokering and management environment.
View Upgrades Prerequisites n Determine when to perform this procedure. Choose an available desktop maintenance window. For information about how much time is required, see the VMware vSphere Upgrade Guide. n Back up the vCenter Server database and the View Composer database. n Back up the View LDAP database from a View Connection Server instance by using the vdmexport.exe utility. For instructions, see the View Administration document.
View Upgrades n If you upgrading only View components, see Upgrade View Agent or Horizon Agent. Accept the Thumbprint of a Default SSL Certificate When you add vCenter Server and View Composer instances to Horizon 7, you must ensure that the SSL certificates that are used for the vCenter Server and View Composer instances are valid and trusted by Connection Server.
View Upgrades 3 Examine the certificate thumbprint that was configured for the vCenter Server or View Composer instance. a On the vCenter Server or View Composer host, start the MMC snap-in and open the Windows Certificate Store. b Navigate to the vCenter Server or View Composer certificate. c Click the Certificate Details tab to display the certificate thumbprint. Similarly, examine the certificate thumbprint for a SAML authenticator.
View Upgrades n The User Configuration policies set policies that apply to all users, regardless of the remote desktop or application they connect to. User Configuration policies override equivalent Computer Configuration policies. Microsoft Windows applies policies at desktop startup and when users log in. VMware, Inc.
Upgrade ESXi Hosts and Their Virtual Machines 4 Upgrading ESXi hosts and virtual machines is the most time-consuming aspect of this middle phase of a View upgrade. This procedure provides an overview of the tasks you must perform during the second and subsequent maintenance windows. To complete some of these tasks, you might need step-by-step instructions found in the VMware vSphere Upgrade Guide and the View Administration document.
View Upgrades Procedure 1 Upgrade ESXi hosts, cluster by cluster. For instructions, see the VMware vSphere Upgrade Guide. If your clusters contain Virtual SAN datastores, also see the chapter about upgrading the Virtual SAN cluster, in the Administering VMware Virtual SAN document. This chapter contains a topic about upgrading ESXi hosts. If you have many clusters, this step could take several maintenance windows to complete.
View Upgrades What to do next Upgrade the agent software. See Upgrade View Agent or Horizon Agent. VMware, Inc.
Upgrading Remote Desktops and Horizon Client 5 The remote desktop and the client components that you can upgrade include Horizon Client for any of the supported desktop and mobile client platforms, thin clients provided by VMware partners, and the Horizon Agent, which runs inside the operating systems of remote desktops and Microsoft RDS hosts. Important This chapter does not contain information about upgrading Horizon Agent on a Linux virtual machine.
View Upgrades Prerequisites n Verify that at least one Horizon Connection Server instance in the replicated group has been upgraded. Connection Server must be upgraded first so that the secure JMS pairing mechanism can work with Horizon Agent. n Verify that the RDS host currently hosting remote desktops is running Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2.
View Upgrades Upgrade View Agent or Horizon Agent The strategy for upgrading the agent software depends on the type of desktop source. Note To upgrade the operating system in a virtual machine desktop from Windows 8 to Windows 8.1, you must uninstall Horizon Agent, upgrade the operating system from Windows 8 to Windows 8.1, and then reinstall Horizon Agent. Alternatively, you can perform a fresh installation of Windows 8.1 and then install Horizon Agent.
View Upgrades Procedure 1 If you plan to deploy instant clones or View Composer linked clones, upgrade the agent software on a parent virtual machine and create a desktop pool for testing purposes. a Download and run the new version of the Horizon Agent installer on a parent virtual machine. You can download the installer from the VMware Web site. b Create a small desktop pool from this virtual machine.
View Upgrades 5 For automated and manual Windows 7 and 8 pools that are not instant-clone or linked-clone pools, to turn on the 3D rendering feature, edit the pool and power the virtual machine desktops off and on. a b Configure the following pool settings: n Set the pool to use the PCoIP display protocol or the VMware Blast display protocol. n Set Allow users to choose protocol to No. n Turn on the 3D Renderer feature. Power off each virtual machine and power it on again.
View Upgrades Upgrading pools that were created with View Composer requires that you use a snapshot taken after upgrading Horizon 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.
View Upgrades 3 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. 4 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 Upgrades n Verify that the client desktop, laptop, tablet, or phone meets the operating system requirements and hardware requirements of Horizon Client. See the "Using Horizon Client" document for the specific type of desktop or mobile client device. Go to https://www.vmware.com/support/viewclients/doc/viewclients_pubs.html. Procedure 1 Have end users upgrade to the latest version of Horizon Client.
Post-Upgrade Tasks to Enable New Features in Your View Setup 6 After you finish upgrading the servers, virtual machines, and agent software for desktop and application pools, you can configure your setup to take advantage of certain new features. In addition to the tasks described in the topics in this chapter, if applicable, you can use View Administrator to edit advanced storage options for desktop pools, and change the scope of transparent page sharing.
View Upgrades Prerequisites Verify that you have upgraded all View Connection Server instances, security servers, and View desktops to Horizon 6 version 6.1 or a later release. View components that predate Horizon 6 version 6.1 cannot communicate with a View Connection Server 6.1 instance that uses Enhanced mode. Procedure 1 Configure back-end firewall rules to allow security servers to send JMS traffic on port 4002 to View Connection Server instances.
View Upgrades Although the space reclamation feature reduces the amount of disk space used for a virtual machine, it can reclaim only space that is not used. This feature cannot reclaim disk space created by virtual machines that have not been optimized. To optimize an operating system image, you can turn off Windows services such as the indexer service, the defragmenter service, and restore points.
View Upgrades 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.
View Upgrades 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. 2 Upgrade the desktop pool to the latest version, as described in Upgrade View Composer Desktop Pools. This process includes installing the latest version of Horizon Agent on the parent virtual machine and taking a snapshot.
View Upgrades 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 n Familiarize yourself with the Virtual SAN upgrade process. See the chapter about upgrading Virtual SAN in the Administering VMware Virtual SAN document, available at https://www.vmware.com/support/pubs/virtual-san-pubs.html.
View Upgrades 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.
View Upgrades For information about upgrades, see Chapter 4 Upgrade ESXi Hosts and Their Virtual Machines and see the VMware vSphere Upgrade Guide. For information about Virtual SAN requirements and upgrades, see the Administering VMware Virtual SAN document.
View Upgrades The oslinks.properties file is installed in the installation-directory\VMware\VMware View\Server\broker\webapps\portal\WEB-INF folder. If this file is missing during the HTML Access session, the download link will direct users to https://www.vmware.com/go/viewclients by default. The file contains the following default values: link.download=https://www.vmware.com/go/viewclients # download Links for particular platforms link.win32=https://www.vmware.com/go/viewclients#win32 link.
View Upgrades If the portal-links-html-access.properties file does not exist and the oslinks.properties file does, open the \VMware\VMware View\Server\broker\webapps\portal\WEB-INF\oslinks.properties file to modify the URLs to use for downloading specific installer files. Note Customizations for View 5.x and earlier releases resided in the portal-links.properties file, which is located in the same CommonAppDataFolder\VMware\VDM\portal\ directory as the portal-links-html-access.
View Upgrades Option Property Setting Create links for specific installers The following examples show full URLs, but you can use relative URLs if you place the installer files in the downloads directory, which is under the C:\Program Files\VMware\VMware View\Server\broker\webapps\ directory on View Connection Server, as described in the next step. n General link to download installer: link.download=https://server/downloads n 32-bit Windows installer: link.
View Upgrades Option Property Setting n Chrome OS installer: link.chromeos=https://server/downloads/VMware-HorizonClient-ChromeOS-build#.apk Change the URL for the Help link in the login page 3 link.help By default, this link points to a help system hosted on the VMware Web site. The Help link appears at the bottom of the login page. To have users download installers from a location other than the VMware Web site, place the installer files on the HTTP server where the installer files will reside.
Applying View Patches 7 Patch releases can include installer files for the following View components: View Composer, View Connection Server, Horizon Agent, and various clients. The patch components that you must apply depend on the bug fixes that your View deployment requires.
View Upgrades n Back up the vCenter Server database and the View Composer database. For instructions on performing a database backup, see the documentation from your database vendor. n For all linked-clone desktop pools, disable provisioning of new virtual machines. n If any desktop pools are scheduled to do a refresh or recompose operation, cancel these tasks. Procedure 1 On the virtual machine that hosts View Composer, download the installer file for the patch version of View Composer.
View Upgrades Prerequisites n Determine when to perform this procedure. Choose an available desktop maintenance window. The amount of time required depends on the number of View Connection Server instances in the group. Budget 15 minutes to half an hour for each instance. n Verify that you have a domain user account with administrative privileges on the hosts that you will use to run the patch installer.
View Upgrades Prerequisites Verify that you have a domain user account with administrative privileges on the hosts that you will use to run the patch installer. Procedure 1 On all parent virtual machines, virtual machines used for full-clone templates, full clones in a pool, and manually added individual virtual machines, download the installer file for the patch version of View Agent (for Horizon 6) or Horizon Agent (for Horizon 7). Your contact at VMware will provide instructions for this download.
View Upgrades 2 If the client device is a Mac or Linux desktop or laptop, remove the current version of the client software from your device. Use the customary device-specific method for removing applications. Note With Horizon Client 3.5 for Windows and later releases, you do not need to uninstall the previous version before you install the patch on Windows clients. With Horizon Client 4.
Upgrading vSphere Components Separately in a View Environment 8 If you upgrade vSphere components separately from View components, you must back up some View data and reinstall some View software. Instead of performing an integrated upgrade of View and vSphere components, you can choose to first upgrade all View components and then upgrade vSphere components, or the reverse. You might also upgrade only vSphere components when a new version or update of vSphere is released.
