View Upgrades Modified for Horizon 7 7.3.2 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–2017 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 11 Supported Operating Systems for View Composer 11 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 12 12 14 Hardware Requirements for Horizon Connection Server 14 Su
View Upgrades Using Horizon 7 Group Policy Administrative Template Files 49 4 Upgrade ESXi Hosts and Their Virtual Machines 50 5 Upgrading Remote Desktops and Horizon Client 53 Security-Related Requirements for Remote Desktop Upgrade Upgrade RDS Hosts That Provide Session-Based Desktops Upgrade View Agent or Horizon Agent 53 55 Upgrade View Composer Desktop Pools Upgrade the Client Application 53 58 59 6 Post-Upgrade Tasks to Enable New Features in Your View Setup 61 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 View Composer Requirements With View Composer, you can deploy multiple linked-clone desktops from a single centralized base image. View Composer has specific installation and storage requirements. Supported Operating Systems for View Composer View Composer supports 64-bit operating systems with specific requirements and limitations. You can install View Composer on the same physical or virtual machine as vCenter Server or on a separate server. Table 2‑2.
View Upgrades Table 2‑3. View Composer Hardware Requirements (Continued) Hardware Component Required Recommended Memory 4GB RAM or higher 8GB RAM or higher for deployments of 50 or more remote desktops Disk space 40GB 60GB Important The physical or virtual machine that hosts View Composer must have an IP address that does not change. In an IPv4 environment, configure a static IP address. In an IPv6 environment, machines automatically get IP addresses that do not change.
View Upgrades Security-Related Requirements n View Composer requires an SSL certificate that is signed by a CA (certificate authority). If you intend to replace an existing certificate or the default, self-signed certificate with a new certificate after you install View Composer, you must import the new certificate and run the SviConfig ReplaceCertificate utility to bind your new certificate to the port used by View Composer.
View Upgrades Horizon Connection Server Requirements Horizon Connection Server acts as a broker for client connections by authenticating and then directing incoming user requests to the appropriate remote desktops and applications. Horizon Connection Server has specific hardware, operating system, installation, and supporting software requirements.
View Upgrades Table 2‑5. Operating System Support for Horizon Connection Server 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. Upgrade Requirements for View Connection Server The View Connection Server upgrade process has specific requirements and limitations.
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 Manually Upgrading the View Composer Database Rather than letting the View Composer installer upgrade the database when a schema update is required, you can manually upgrade the database. You can use the SviConfig utility when you must observe the upgrade process more closely or when upgrade tasks must be distributed to IT administrators with different responsibilities.
View Upgrades 2 Enter the command to stop VMware View Composer. net stop svid 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.
View Upgrades Table 3‑1. Result Codes for the databaseupgrade Command Code Description 0 The operation ended successfully. 1 The supplied DSN could not be found. 2 Invalid database administrator credentials were provided. 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.
View Upgrades 3 Run the SviConfig databaseupgrade command again. 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 Prepare a Microsoft .NET Framework for Migrating RSA Keys To use an existing View Composer database, you must migrate the RSA key container between machines. You migrate the RSA key container by using the ASP.NET IIS registration tool provided with the Microsoft .NET Framework. 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 .
View Upgrades 4 On the destination machine, open a command prompt and navigate to the %windir %\Microsoft.NET\Framework\v2.0xxxxx directory. 5 Type the aspnet_regiis command to migrate the RSA key pair data. aspnet_regiis -pi "SviKeyContainer" "path\keys.xml" -exp where path is the path to the exported file. 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.
View Upgrades Preparing Connection Server for an Upgrade Before you upgrade Connection Server or before you upgrade any of the vSphere components that Connection Server relies on, you must perform several tasks to ensure that these upgrades are successful. Tasks to Perform on Only One Instance in a Replicated Group Before you begin upgrading any Connection Server instances, perform the following tasks using only one of the instances.
View Upgrades n Determine if your company has written any batch files or scripts that run against the View database on the Connection Server instance, and if so, document their names and locations. n Open Horizon Administrator and document all the settings that are specific to this instance. For example, go to View Configuration > Servers > Connection Servers, select the Connection Server instance in the table and click Edit.
View Upgrades n Verify that you have a license that is valid for the new version. Note When you upgrade from 6.0.x or 6.1.x to 6.2, your previous license will continue to work and the usage model will be set to Concurrent User. A new licensing model called Named User was added beginning with Horizon 6 version 6.2. You have the option of changing the licensing model to Named User. For more information, see http://www.vmware.com/files/pdf/products/horizon-view/VMware-Horizon-View-Pricing-LicensingFAQ.pdf.
View Upgrades 5 Log in to Horizon Administrator and enable the Connection Server instance that you just upgraded. a Go to View Configuration > Servers and click the Connection Servers tab. b Select the Connection Server instance in the list and click the Enable button above the table. c In the Version column, verify that the new version is displayed. 6 Go to View Configuration > Product Licensing and Usage, click Edit License, enter the license key, and click OK.
View Upgrades If you have an older version of vCenter Server, see Enable TLSv1.0 on vCenter Connections from Connection Server. If the upgrade fails on one or more of the Connection Server instances, see Create a Replicated Group After Reverting Connection Server to a Snapshot. Important If you plan to use enhanced message security mode for JMS messages, make sure that firewalls allow Connection Server instances to receive incoming JMS traffic on port 4002 from desktops and security servers.
View Upgrades 6 In the Properties dialog box, edit the pae-ClientSSLSecureProtocols attribute to add the following value \LIST:TLSv1.2,TLSv1.1,TLSv1 Be sure to include the back slash at the beginning of the line. 7 Click OK. 8 If this is a fresh installation, to apply the configuration change, restart the VMware Horizon View Connection Server service on each connection server instance.
View Upgrades 3 If applicable, uninstall Connection Server from the old host by using the Windows Add/Remove Programs utility. 4 In Horizon Administrator, go to View Configuration > Servers > Connection Servers tab and determine whether the Connection Server instance that was uninstalled still appears in the list. 5 If the uninstalled Connection Server instance still appears in the list, use a vdmadmin command to remove it. vdmadmin.
View Upgrades Procedure 1 On all Connection Server instances except the one chosen to be the new standard Connection Server instance, uninstall Connection Server and the View LDAP instance. The View LDAP instance is called AD LDS Instance VMwareVDMDS. 2 On the virtual machine that hosts the standard, or master, Connection Server instance, open a command prompt and enter the following command to ensure that replication is not disabled.
View Upgrades n If you use load balancers for security servers, document the configuration settings for the load balancers. Note This topic does not describe the View Administrator command called Prepare for Upgrade or Reinstallation, which is available from the Security Servers tab. That command removes IPsec rules for the security server, which stops all communication between the security server and the paired View Connection Server instance.
View Upgrades See Horizon Connection Server Requirements. n Complete the tasks listed in Preparing Connection Server for an Upgrade. Important If any Local Mode desktops are checked out at the time you run the View Connection Server installer to install the upgrade, the upgrade will fail. n Verify that you have a license for the new version. n Verify that you have a user account with administrative privileges on the hosts that you will use to run the installer and perform the upgrade.
View Upgrades You will be prompted to supply the security server pairing password. You might be prompted to dismiss a message box notifying you that the Security Server service was stopped. The installer stops the service in preparation for the upgrade. 5 After the installer wizard is finished, verify that the VMware Horizon View Security Server service is started. 6 If you are using a load balancer for managing this security server, add this server back to the loadbalanced group.
View Upgrades If the upgrade fails on one or more of the View Connection Server instances, see Create a Replicated Group After Reverting Connection Server to a Snapshot. Important If you plan to use enhanced message security mode for JMS messages, make sure that firewalls allow Connection Server instances to receive incoming JMS traffic on port 4002 from desktops and security servers. Also open port 4101 to accept connections from other Connection Server instances.
View Upgrades Upgrading View Servers to Allow HTML Access When upgrading View Connection Server instances or security servers behind a load balancer or behind a gateway such as Access Point, you must make configuration changes to continue to use HTML Access. For more information, see "Allow HTML Access Through a Load Balancer" and "Allow HTML Access Through a Gateway" in the View Installation document.
View Upgrades Procedure 1 Upgrade vCenter Server as described in the VMware vSphere Upgrade Guide. Important 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 vCenter Server. 2 If View Composer is installed on the same host, restart the View Composer service.
View Upgrades For details about configuring SSL certificates, see "Configuring SSL Certificates for View Servers" in the View Installation document. You first add vCenter Server and View Composer in Horizon Administrator by using the Add vCenter Server wizard. If a certificate is untrusted and you do not accept the thumbprint, you cannot add vCenter Server and View Composer. After these servers are added, you can reconfigure them in the Edit vCenter Server dialog box.
View Upgrades 5 Determine whether to accept the certificate thumbprint. Option Description The thumbprints match. Click Accept to use the default certificate. The thumbprints do not match. Click Reject. Troubleshoot the mismatched certificates. For example, you might have provided an incorrect IP address for vCenter Server or View Composer. Using Horizon 7 Group Policy Administrative Template Files Horizon 7 provides several component-specific Group Policy Administrative ADMX template files.
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 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 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.
View Upgrades 2 To turn on the 3D rendering feature, edit the pool to configure the following 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 Rendering feature. 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.
View Upgrades Prerequisites n Complete the procedures for upgrading the server components, which can include View Connection Server and View Composer. See Chapter 3 Upgrading View Server Components. n Verify that you have a domain user account with administrative privileges on the hosts that you will use to run the installer and perform the upgrade. n Verify that the client desktop, laptop, tablet, or phone meets the operating system requirements and hardware requirements 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 Apply a Patch for View Connection Server Applying a patch involves downloading and running the installer for the patch version. 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.
View Upgrades Apply a Patch for View Agent or Horizon Agent Applying a patch involves downloading and running the installer for the patch version. The following steps need to be performed on the parent virtual machine, for linked-clone desktop pools, or on each virtual machine desktop in a full-clone pool, or on individual desktop virtual machines for pools that contain only one virtual machine desktop.
View Upgrades Apply a Patch for Horizon Client On desktop client devices, applying a patch involves downloading and running the installer for the patch version. On mobile clients, applying a patch involves simply installing the update from the Web site that sells apps, such as Google Play, Windows Store, or the Apple App Store. Procedure 1 On each client system, download the installer file for the patch version of Horizon Client. Your contact at VMware will provide instructions for this download.
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.
