Released 16 March 2017 | Build 5202536 (Non-FIPS) | Build 5202538 (FIPS)
Last Updated: 31 MARCH 2017
These release notes include the following topics:
VMware Unified Access Gateway™ 2.9 provides the following new features and enhancements.
- Horizon BEAT Support
Supports BEAT (Blast Extreme Adaptive Transport), the UDP-based transport part of the Blast protocol specially designed for low bandwidth, high latency, and high packet loss networks, and the ability to choose between hybrid and UDP-only mode.
- Access to on-premise legacy apps
Supports Web Reverse Proxy to on-premise legacy apps using headers and Kerberos-based authentication. The Unified Access Gateway acts as an identity bridge to convert SAML to Kerberos or headers for back end resource access.
- FIPS OVA
Separate OVA for FIPS-140-2 mode. The FIPS-140-2 OVA is restricted to PCoIP in this release.
- Admin UI
Enhancements to the Admin UI, including:
- New health status for edge services and back end resources, making deployment and troubleshooting easier to perform
- Ability to change log levels to facilitate debugging
- Security Enhancements
Updates to SUSE Linux Enterprise Server (SLES), openssl and Java
The Unified Access Gateway user interface, online help, and product documentation are available in Japanese, French, German, Spanish, Brazilian Portuguese, Simplified Chinese, Traditional Chinese, and Korean. For the documentation, see the Documentation Center for VMware Unified Access Gateway 2.9.
For more information about the VMware Product Interoperability Matrix, see http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
Smart card authentication does not work while connecting to the Unified Access Gateway server if the alternate subject name has the email address for the certificate mapped with the domain account.
Workaround: In the wizard for creating a certificate template for the smart card user, on the Subject Name tab, deselect the checkbox "Include this information in alternate subject name:".
Unified Access Gateway session timeout does not disconnect the Blast Connection.
Client login fails after Unified Access Gateway session timeout.
- If this occurs when logging in to the Horizon Client, relaunch the client.
- This also occurs if a tunnel is disabled on the Unified Access Gateway. In this case, first disconnect from the Unified Access Gateway server, then reconnect and launch the desktop before the session timeout occurs.