View Upgrades VMware Horizon 7 7.2 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
View Upgrades You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2009–2017 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc.
Contents View Upgrades 5 1 View Upgrade Overview 7 2 System Requirements for Upgrades 11 Compatibility Matrix for Various Versions of View Components 11 View Composer Requirements 12 Supported Operating Systems for View Composer 12 Hardware Requirements for Standalone View Composer 13 Database Requirements for View Composer and the Events Database Upgrade Requirements for View Composer 14 Horizon Connection Server Requirements 15 Hardware Requirements for Horizon Connection Server 15 Supported Operating
View Upgrades 5 Upgrading Remote Desktops and Horizon Client 49 Security-Related Requirements for Remote Desktop Upgrade 49 Upgrade RDS Hosts That Provide Session-Based Desktops 49 Upgrade View Agent or Horizon Agent 50 Upgrade View Composer Desktop Pools 53 Upgrade the Client Application 54 6 Post-Upgrade Tasks to Enable New Features in Your View Setup 57 Change the JMS Message Security Mode to Enhanced 57 Tasks for Upgrading Desktop Pools to Use Space Reclamation 58 Upgrade Tasks If You Use VMware Virt
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.
View Upgrades 6 VMware, Inc.
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 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. For other preparation tasks, you can perform the tasks for one instance at a time, just before you perform the upgrade of that server instance. 4 Upgrade View Connection Server instances that are not paired with security servers. See “Upgrade Connection Servers in a Replicated Group,” on page 33.
Chapter 1 View Upgrade Overview Because certain commands can simultaneously upgrade more than one stage, VMware recommends that you thoroughly understand the irreversible changes at each stage before you upgrade your production environments. ® Important The VMware View Client with Local Mode feature, for using offline desktops, has been removed, and therefore this overview does not include steps for upgrading View Transfer Server instances and View Client with Local Mode.
View Upgrades 10 VMware, Inc.
2 System Requirements for Upgrades Hosts and virtual machines in a View 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 (Continued) Connection Server: Earlier Version Security Server: Earlier Version View Composer: Earlier Version View Agent: Earlier Version Horizon Client (Windows): Earlier Version View Composer 7.0 Only during upgrade Only during upgrade N/A Only during upgrade N/A Horizon Agent 7.
Chapter 2 System Requirements for Upgrades Hardware Requirements for Standalone View Composer If you install View Composer on a different physical or virtual machine from the one used for vCenter Server, you must use a dedicated machine that meets specific hardware requirements. A standalone View Composer installation works with vCenter Server installed on a separate Windows Server machine or with the Linux-based vCenter Server appliance.
View Upgrades Table 2‑4. Supported Database Servers for View Composer and for the Events Database (Continued) Database Service Packs/Releases Editions Microsoft SQL Server 2008 R2 (32- and 64-bit) SP2, SP3 Express Standard Enterprise Datacenter Oracle 12c Release 1 (any release up to 12.1.0.2) Standard One Standard Enterprise Note The following versions are no longer supported: Microsoft SQL Server 2008 SP4 and Oracle 11g Release 2 (11.2.0.04).
Chapter 2 System Requirements for 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 Upgrade Requirements for View Connection Server The View Connection Server upgrade process has specific requirements and limitations. n View Connection Server requires a valid license key for this latest release. n The domain user account that you use to install the new version of View Connection Server must have administrative privileges on the View Connection Server host. The View Connection Server administrator must have administrative credentials for vCenter Server.
Chapter 2 System Requirements for Upgrades 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 Connection Server. If you cannot apply patches, reenable TLSv1.0 on View Connection Server before upgrading. For more information, see “Enable TLSv1.0 on vCenter Connections from Connection Server,” on page 35.
View Upgrades 18 VMware, Inc.
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 Preparing vCenter Server and View Composer for an Upgrade Because vCenter Server and View Composer are often installed on the same virtual or physical machine, some preparation tasks apply to both.
Chapter 3 Upgrading View Server Components Preparing for Upgrades of View Composer Only If you are upgrading only View Composer and are not upgrading vCenter Server, you must perform the following tasks: 1 Verify that the virtual or physical machine on which the current View Composer is installed meets the security requirements for the new version. See “Upgrade Requirements for View Composer,” on page 14. 2 If View Composer is installed in a virtual machine, take a snapshot of the virtual machine.
View Upgrades n Determine whether to let the installer wizard upgrade the View Composer database if a schema upgrade is required. You can choose to run the SviConfig command-line utility after the wizard finishes to upgrade the database schema manually and to create a log of the upgrade. Procedure 1 On the virtual or physical machines where View Composer is installed, download and run the installer for View Composer. You can download the installer from the VMware Web site.
Chapter 3 Upgrading View Server Components 5 Restart the VMware Horizon View Composer service. TLSv1.0 connections from View Composer to vCenter are now enabled. 6 7 8 In the Windows Registry on the View Composer machine, navigate to HKLM\SOFTWARE\VMware, Inc.\VMware View Composer. Create or edit the String value EnableTLS1.0 and set it to 1. If the View Composer host is a 64-bit machine, navigate to HKLM\SOFTWARE\WOW6432Node\VMware, Inc\VMware View Composer.
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.
Chapter 3 Upgrading View Server Components 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. Update SVI_DEPLOYMENT_GROUP table. Update SVI_REPLICA table. Update SVI_SIM_CLONE table. SviConfig finished successfully. Database is upgraded successfully. 5 Enter the command to start the View Composer.
View Upgrades Troubleshooting a View Composer Database Upgrade Failure When you upgrade the View Composer service with the View Composer installer or run the SviConfig databaseupgrade command, the operation might fail to upgrade the View Composer database. Problem The SviConfig databaseupgrade operation displays error code 17, or the View Composer installer displays a warning message.
Chapter 3 Upgrading View Server Components n Migrate View Composer with an Existing Database on page 27 When you migrate View Composer to another physical or virtual machine, if you intend to preserve your current linked-clone virtual machines, the new VMware Horizon View Composer service must continue to use the existing View Composer database.
View Upgrades n From a standalone machine to a vCenter Server machine n From a standalone machine to another standalone machine n From a vCenter Server machine to another vCenter Server machine When you migrate the VMware Horizon View Composer service, you can also migrate the View Composer database to a new location. For example, you might need to migrate the View Composer database if the current database is located on a vCenter Server machine that you are migrating as well.
Chapter 3 Upgrading View Server Components 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 4 Configure an SSL server certificate for View Composer on the new machine. You might be able to copy the certificate that was installed for View Composer on the original machine, or you can install a new certificate. 5 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.
Chapter 3 Upgrading View Server Components Procedure 1 On the source machine on which the existing VMware Horizon View Composer service resides, open a command prompt and navigate to the %windir%\Microsoft.NET\Framework\v2.0xxxxx directory. 2 Type the aspnet_regiis command to save the RSA key pair in a local file. aspnet_regiis -px "SviKeyContainer" "keys.xml" -pri The ASP.NET IIS registration tool exports the RSA public-private key pair from the SviKeyContainer container to the keys.
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.
Chapter 3 Upgrading View Server Components Upgrade Connection Servers in a Replicated Group This procedure describes upgrading Connection Server instances that are not paired with security servers. For example, this procedure applies to Connection Servers that are configured for connections to clients that are inside the corporate firewall.
View Upgrades 2 3 Log in to Horizon Administrator and disable the Connection Server instance that you are about to upgrade. 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. c Click OK to confirm disabling the server. On the host of the Connection Server instance, download and run the installer for the new version of Connection Server.
Chapter 3 Upgrading View Server Components 11 Log in to Horizon Administrator and examine the dashboard to verify that the vCenter Server and View Composer icons are green. If either of these icons is red and an Invalid Certificate Detected dialog box appears, you must click Verify and either accept the thumbprint of the untrusted certificate, as described in "What to Do Next," or install a valid CA-signed SSL certificate.
View Upgrades Procedure 1 Start the ADSI Edit utility on your Connection Server host. 2 In the console tree, select Connect to. 3 4 In the Select or type a Distinguished Name or Naming Context text box, type the distinguished name DC=vdi, DC=vmware, DC=int. In the Computer pane, select or type localhost:389 or the fully qualified domain name (FQDN) of the Connection Server host followed by port 389. For example: localhost:389 or mycomputer.example.
Chapter 3 Upgrading View Server Components 2 On the new machine, install a replicated instance of Connection Server. The View LDAP on the new instance will replicate that of the upgraded source instance. 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.
View Upgrades 3 On the virtual machines that are to host the replica Connection Server instances, run the Connection Server installer, select the View Replica Server installation option, and specify the host name or IP address of the standard Connection Server instance. The replicated group of Connection Server instances is recreated and their View LDAP objects are consistent.
Chapter 3 Upgrading View Server Components The first few steps of this procedure involve upgrading the View Connection Server instance. After the View Connection Server upgrade, but before the security server upgrade, one of the steps describes removing the IPsec rules for the security server. When you remove the IPsec rules for an active security server, all communication with the security server is lost until you upgrade or reinstall the security server.
View Upgrades 3 Remove IPsec rules for the security server paired with the View Connection Server instance that you just upgraded. a In View Administrator, click View Configuration > Servers. b In the Security Servers tab, select a security server and click More Commands > Prepare for Upgrade or Reinstallation. If you disabled IPsec rules before you installed the security server, this setting is inactive. In this case, you do not have to remove IPsec rules before you reinstall or upgrade. c Click OK.
Chapter 3 Upgrading View Server Components 12 Verify that the dashboard icons for the connection server instances are also are green. If any instances have red icons, click the instance to determine the replication status.
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.
Chapter 3 Upgrading View Server Components 3 Log in to View Administrator and examine the dashboard to verify that the vCenter Server and View Composer icons are green. If either of these icons is red and an Invalid Certificate Detected dialog box appears, you must click Verify and either accept the thumbprint of the untrusted certificate, as described in "What to Do Next," or install a valid CA-signed SSL certificate.
View Upgrades Similarly, in View Administrator you can configure a SAML authenticator for use by a View Connection Server instance. If the SAML server certificate is not trusted by View Connection Server, you must determine whether to accept the certificate thumbprint. If you do not accept the thumbprint, you cannot configure the SAML authenticator in View. After a SAML authenticator is configured, you can reconfigure it in the Edit View Connection Server dialog box.
Chapter 3 Upgrading View Server Components 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.
View Upgrades 46 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.
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 n Verify that the RDS host currently hosting remote desktops is running Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2. Windows Server 2008 (Terminal Services) was supported for earlier versions of View but is not a supported operating system for this release. If you do not have a supported Windows Server operating system, you must do a fresh installation rather than an upgrade.
Chapter 5 Upgrading Remote Desktops and Horizon Client This procedure provides an overview of the tasks you must perform to upgrade the agent software in virtual machines used as desktop sources. To complete some of these tasks, you might need the step-by-step instructions found in the vSphere Client online help or in Setting Up Virtual Desktops in Horizon 7, available by clicking the Help button in Horizon Administrator.
View Upgrades 3 If you plan to create instant-clone or View Composer linked-clone desktop pools, take a snapshot of each upgraded parent virtual machine. Use the new snapshot for creating an instant-clone or linked-clone desktop pool, or for recomposing an existing linked-clone desktop pool. For instructions on taking snapshots, see the vSphere Client online help.
Chapter 5 Upgrading Remote Desktops and Horizon Client 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 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 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.
Chapter 5 Upgrading Remote Desktops and Horizon Client Procedure 1 2 VMware, Inc. Have end users upgrade to the latest version of Horizon Client. Option Action Horizon Client Download and send the Horizon Client installers to your end users or post them on a Web site and ask end users to download the installer and run it. You can download the installers or have your end users download them from the VMware Web site at https://www.vmware.com/go/viewclients.
View Upgrades 56 VMware, Inc.
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 Procedure 1 Configure back-end firewall rules to allow security servers to send JMS traffic on port 4002 to View Connection Server instances. 2 In View Administrator, go to View Configuration > Global Settings, and on the Security tab, set Message security mode to Enhanced. 3 Manually restart the VMware Horizon View Message Bus Component service on all View Connection Server hosts in the pod, or restart the View Connection Server instances.
Chapter 6 Post-Upgrade Tasks to Enable New Features in Your View Setup Recomposing the pool from a snapshot of an upgraded virtual machine is just one method of upgrading all virtual machines in a linked-clone pool. You can also upgrade the virtual machines one by one. 3 4 Upgrade the disk format used for the virtual machines. n On the Connection Server host, use ADSIEdit to navigate to the server group that corresponds to the pool, and change the value in the pae-UseSeSparseFormat field from 0 to 1.
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 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,” on page 53.
Chapter 6 Post-Upgrade Tasks to Enable New Features in Your View Setup 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 Upgrade from Horizon View 5.3.x 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.x after the desktop pool is upgraded. In addition, when you upgrade from View 5.3.x, the Use VMware Virtual SAN pool setting will not automatically be enabled, even if the pool is on a Virtual SAN datastore.
Chapter 6 Post-Upgrade Tasks to Enable New Features in Your View Setup 4 Edit the pool settings of the newly upgraded desktop pool to change the datastore from a non-Virtual SAN datastore to a Virtual SAN datastore, and use the Rebalance command. What to do next If you upgraded your virtual machines to VMware vSphere 6.0, to upgrade to using Virtual SAN 2 rather than Virtual SAN 1, see “Upgrade from Virtual SAN Disk Format Version 1,” on page 60.
View Upgrades Procedure 1 On the View Connection Server host, open the portal-links-html-access.properties file with a text editor. The location of this file is CommonAppDataFolder\VMware\VDM\portal\portal-links-htmlaccess.properties. For Windows Server 2008 operating systems, the CommonAppDataFolder directory is C:\ProgramData. To display the C:\ProgramData folder in Windows Explorer, you must use the Folder Options dialog box to show hidden folders. If the portal-links-html-access.
Chapter 6 Post-Upgrade Tasks to Enable New Features in Your View Setup 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: n link.
View Upgrades 66 VMware, Inc.
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 Procedure 1 On the virtual machine that hosts View Composer, download the installer file for the patch version of View Composer. Your contact at VMware will provide instructions for this download. 2 Run the installer that you downloaded for the patch release of View Composer. Note With Horizon 6 version 6.2 and later releases, you are no longer required to uninstall the previous version before installing the patch.
Chapter 7 Applying View Patches 3 Run the installer that you downloaded for the patch release of View Connection Server. For information about running the installer, see the View Installation document. Note With Horizon 6 version 6.2 and later releases, you are no longer required to uninstall the previous version before installing the patch. 4 Follow the installation wizard prompts and click OK when asked to continue the installation with the existing ADAM instance.
View Upgrades 7 If you canceled any refresh or recompose operations for any linked-clone desktop pools, schedule the tasks again. 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.
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.
View Upgrades 72 VMware, Inc.
Index A ASP.
View Upgrades port, changing for View Composer during upgrade 21 R result codes, databaseupgrade operation 25 RSA key container migrating to View Composer 30 using NET Framework 30 S security servers operating system requirements 15 upgrading 33, 38 services Horizon Connection Server 33 VMware Horizon View Connection Server 38 VMwareVDMDS 33, 38 space reclamation feature 58 space-efficient disk format 58 SQL Server databases 13 SSL, accept a certificate thumbprint 43 SSL certificate backups 20 sviconfig
