VMware Horizon 7 version 7.10

Print Friendly, PDF & Email

What’s New in This Release

VMware Horizon 7 version 7.10 provides the following new features and enhancements. This information is grouped by installable component.

For information about the issues that are resolved in this release, see Resolved Issues.

Product Enhancements

The VMware Horizon 7 version 7.10 release includes many new features and enhancements to Horizon Connection Server and Horizon Agent including continuing to build on the feature parity of Horizon Console, the HTML5-based web console that will eventually replace Horizon Administrator.

Horizon Connection Server On-Premises

  • Horizon Console (HTML5-based Web Interface)
    There are several enhancements to Horizon Console. These include:
    • Monitor the status of Horizon 7 components in the Horizon Console dashboard.
    • Monitor the Connection Server load in the Horizon Console dashboard.
    • Monitor gateway service components for a Connection Server in the Horizon Console dashboard.
    • Enhancements to role-based delegated administration including privileges and roles for custom roles in Horizon Console.
    • The Console Interaction and Direct Interaction privileges are automatically applied to new roles.
    • Configure users for hybrid logon.
    • Enable the Accept logon as current user setting to allow the Connection Server instance to accept the user identity and credential information that is passed when users select Log in as current user in the Options menu in Horizon Client.
    • Configure the send domain list setting to allow the Connection Server to send the list of domain names to the client before the user is authenticated.
    • Create an automated desktop pool of full virtual machines with floating user assignments.
    • Configure load balancing for RDS hosts.
    • The restart desktop and reset virtual machine options are removed for an instant-clone farm.
    • You can duplicate a published application pool.
    • To identify the Connection Server pod you are working with, you can view the pod name in the Horizon Console header and in the Web browser tab.
    • You can duplicate an instant-clone desktop pool, linked-clone desktop pool, or an automated desktop pool that contains full virtual machines.
    • Use enhanced log to file options for event reporting.
    • A 60 second warning and subsequent error timeout window alerts you to continue the session or log in again.
    • You can select multiple virtual machines and perform relevant operations on them.
  • Cloud Pod Architecture
    • You can use the new -g option in the vdmexport command to export a Cloud Pod Architecture global LDIF configuration file. You can use the new -g option in the vdmimport command to import a Cloud Pod Architecture global LDIF configuration file. You use these options when you need to back up and restore a Cloud Pod Architecture environment. For more information, see the Horizon 7 Integration document.
  • Virtual Desktops
    • You can use instant clones in an IPv6 environment.
    • The IcCleanup.cmd utility allows you to unprotect or delete some or all internal VMs, incluing those in specific groups and their snapshots.
  • Troubleshooting
    • You can enable Horizon 7 administrator users to collect Connection Server logs for Skyline Collector Appliance. 
  • APIs

Horizon Agent for Linux

  • Supported distributions
    • ?Horizon Agent for Linux now supports RHEL 8 as an operating system for Linux remote desktops. The following limitations apply to RHEL 8 desktops:
      • Horizon Agent only supports the X11 display server protocol. The Wayland display server protocol is not supported.
      • True SSO is not supported.
      • Smartcard SSO is not supported.
    • Starting with this release, Ubuntu 14.04, Ubuntu 12.04, and SLED 11 are no longer supported as operating systems for Linux remote desktops.
  • New display driver
    • ?This release uses a new display driver for Linux remote desktops. In previous releases of Horizon Agent for Linux, the driver used vRAM from the ESXi host for rendering displays. The new driver in this release uses VM host memory instead for rendering displays.
  • vSGA requirement
    • Due to enhancements from the new display driver for Linux remote desktops, this release no longer requires or supports vSGA.

Horizon Agent

  • Remoting Protocols
    • The new Blast encoder improves on the Adaptive and H.264 encoders in desktop usage to provide crisp text and less bandwidth for video content. For pure video usage, the Switch encoder provides a mechanism to switch to H.264.
    • You can switch between encoders by setting a registry key EncoderSwitchEnabled to 1. By default this is disabled with the value of 0.
  • Remote Experience
    • With the VMware Browser Redirection feature, when a user uses the Google Chrome browser in a remote desktop, the website is rendered in the client system instead of the agent system, and it is displayed over the remote browser’s viewport. The VMware Browser Redirection feature requires Horizon Client 5.2 for Windows on the client system.
    • For virtual desktops, the Real-Time Audio-Video feature can now redirect more than one audio and video device from the client system. This feature is not supported for published desktops or published applications. This feature requires Horizon Client 5.2 for Windows on the client system.
    • You can use group policy settings to map drive letters for the client drive redirection feature.
    • The Real-Time Audio-Video and Scanner Redirection features are now supported in nested mode. See VMware Knowledge Base article 67248.
    • You can specify staple and punch options for specified printers with the VMware Integrated Printing feature.
    • If you are installing the Virtualization Pack for Skype for Business component on a Windows 7 VM, verify that you have .Net 4.0 or later installed.
    • Smartcard redirection now works with WDEG.

Horizon GPO Bundle

  • The VMware Horizon Client Drive Redirection ADMX template file, vdm_agent_cdr.admx, contains the following new settings:
    • Configure drive letter mapping mode
    • Define drive letter mapping
  • The VMware View Agent Configuration ADMX template file, vdm_agent.admx, contains the following new settings:
    • Disconnect Session Time Limit (VDI)
    • Enable automatic fallback after a whitelist violation
    • Enable Navigation URL list for VMware Browser Redirection
    • Enable VMware Browser Redirection
    • Enable URL list for VMware Browser Redirection
    • Idle Time Until Disconnect (VDI)
    • Show a page with error information before automatic fallback
  • The Scanner Redirection ADMX template file, vdm_agent_scanner.admx, contains the following new settings:
    • Force the TWAIN Scanning Properties dialog
    • TWAIN Scanner Properties dialog location
  • The VMware Horizon Client Configuration ADMX template file, vdm_client.admx, contains the following new settings:
    • Allow Blast connections to use operating system proxy settings
    • Automatically synchronize the keypad, scroll and caps lock keys
    • Enable cache for browser redirection
    • Enable WebRTC camera and microphone access for browser redirection
    • Hotkey combination to grab input focus
    • Hotkey combination to release input focus
    • Ignore certificate errors for browser redirection

Horizon Client

For information about new features in Horizon Client 5.2, including HTML Access 5.2, see the release notes on the Horizon Clients Documentation page.

Horizon 7 Cloud Connector

This is a required component for Horizon 7.6 and later to support the management of Horizon 7 pods using Horizon Cloud Service.

Horizon 7 Deployed on VMware Cloud on AWS

For a list of Horizon 7 features supported on VMware Cloud on AWS, see the VMware Knowledge Base article 58539.

Before You Begin

  • Important note about installing VMware View Composer
    If you plan to install or upgrade to View Composer 7.2 or later, you must upgrade the Microsoft .NET framework to version 4.6.1. Otherwise, the installation will fail.
  • Important note about installing VMware Tools
    If you plan to install a version of VMware Tools downloaded from VMware Product Downloads, rather than the default version provided with vSphere, make sure that the VMware Tools version is supported. To determine which VMware Tools versions are supported, go to the VMware Product Interoperability Matrix, select the solution VMware Horizon View and the version, then select VMware Tools (downloadable only).
  • If you want to install View Composer silently, see the VMware Knowledge Base (KB) article 2148204, Microsoft Windows Installer Command-Line Options for Horizon Composer.
  • This Horizon 7 release includes new configuration requirements that differ from some earlier releases. See the Horizon 7 Upgrades document for upgrade instructions.
  • Horizon 7.10 is an Extended Service Branch (ESB) that will receive periodic service pack (SP) updates, which include cumulative, critical bug fixes, and security fixes. See the VMware Knowledge Base (KB) article 52845 FAQ: Horizon 7, App Volumes, UEM Extended Service Branches (ESB) for detailed information of ESB. See the Horizon 7 Upgrades document for upgrading to SPs.
  • If you intend to upgrade a pre-6.2 installation of Horizon 7, and the Connection Server, security server, or View Composer server uses the self-signed certificate that was installed by default, you must remove the existing self-signed certificate before you perform the upgrade. Connections might not work if the existing self-signed certificates remain in place. During an upgrade, the installer does not replace any existing certificate. Removing the old self-signed certificate ensures that a new certificate is installed. The self-signed certificate in this release has a longer RSA key (2048 bits instead of 1024) and a stronger signature (SHA-256 with RSA instead of SHA-1 with RSA) than in pre-6.2 releases. Note that self-signed certificates are insecure and should be replaced by CA-signed certificates as soon as possible, and that SHA-1 certificates are no longer considered secure and should be replaced by SHA-2 certificates.
    Do not remove CA-signed certificates that were installed for production use, as recommended by VMware. CA-signed certificates will continue to work after you upgrade to this release.
  • After you have performed a fresh install or upgraded all Connection Server instances to Horizon 7 version 7.2 or later, you cannot downgrade the Connection Server instances to a version earlier than Horizon 7 version 7.2 because the keys used to protect LDAP data have changed. To keep the possibility of downgrading Connection Server instances while planning an upgrade to Horizon 7 version 7.2 or later, you must perform an LDAP backup before starting the upgrade. If you need to downgrade the Connection Server instances, you must downgrade all Connection Server instances and then apply the LDAP backup to the last Connection Server that is downgraded.  
  • Selecting the Scanner Redirection setup option with Horizon Agent installation can significantly affect the host consolidation ratio. To ensure the optimal host consolidation, make sure that the Scanner Redirection setup option is only selected for those users who need it. (By default, the Scanner Redirection option is not selected when you install Horizon Agent.) For users who need the Scanner Redirection feature, configure a separate desktop pool and select the setup option only in that pool.
  • Horizon 7 uses only TLSv1.1 and TLSv1.2. In FIPS mode, it uses only TLSv1.2. You might not be able to connect to vSphere unless you apply vSphere patches. For information about re-enabling TLSv1.0, see Enable TLSv1 on vCenter Connections from Connection Server and Enable TLSv1 on vCenter and ESXi Connections from View Composer in the Horizon 7 Upgrades document.
  • FIPS mode is not supported on releases earlier than 6.2. If you enable FIPS mode in Windows and upgrade Horizon Composer or Horizon Agent from a release earlier than Horizon View 6.2 to Horizon 7 version 7.2 or later, the FIPS mode option is not shown. You must do a fresh install instead to install Horizon 7 version 7.2 or later in FIPS mode.
  • Linux desktops use port 22443 for the VMware Blast display protocol.
  • Starting with Horizon 7 version 7.2, it is possible that the ordering of cipher suites can be enforced by Connection Server. For more information, see the Horizon 7 Security document.
  • Starting with Horizon 7 version 7.2, Connection Server must be able to communicate on port 32111 with other Connection Servers in the same pod. If this traffic is blocked during installation or upgrade, installation will not succeed.
  • Starting with Horizon 7 version 7.3.2, TLS handshakes on port 443 must complete within 10 seconds, or within 100 seconds if smart card authentication is enabled. In previous releases of Horizon 7, TLS handshakes on port 443 were allowed 100 seconds to complete in all situations. You can adjust the time for TLS handshakes on port 443 by setting the configuration property handshakeLifetime. Optionally, the client that is responsible for an over-running TLS handshake can be automatically added to a blacklist. New connections from blacklisted clients are delayed for a configurable period before being processed so that connections from other clients take priority. You can enable this feature by setting the configuration property secureHandshakeDelay. For more information about setting configuration properties, see the Horizon 7 Security document.
  • When the Remote Desktop Services role is not present, the Horizon Agent installer prompts you to install Horizon Agent in RDS mode or desktop mode.

Top of Page


The Horizon Administrator and Horizon Console user interface, Horizon Administrator and Horizon Console online help, and Horizon 7 product documentation are available in Japanese, French, German, Spanish, simplified Chinese, traditional Chinese, and Korean. For the documentation, see the Documentation Center for VMware Horizon 7.