Released 17 May 2017 | Build 5562999 (Non-FIPS) | Build 5563000 (FIPS)
Last Updated: 02 JUNE 2017
These release notes include the following topics:
VMware Unified Access Gateway™ 3.0 provides the following new features and enhancements.
- Hyper-V support
Provides additional flexibility for Unified Access Gateway deployment by supporting Microsoft Hyper-V as an alternative hypervisor to vSphere. Currently Hyper-V is only supported for the VMware Tunnel use cases.
- Ability to specify default gateway in OVF properties
In UAG 3.0, a default gateway can be specified. This is useful in cases where the default gateway specified in the associated network protocol profile (NPP) in vSphere is missing. It is also useful in cases where multiple NPPs are present in multi NIC deployments and where there is ambiguity caused by multiple default gateways. The single default gateway specified for UAG overrides any default gateways specified in associated vSphere NPPs.
- Ability to delete entities in the Admin UI
Provides the option to delete Reverse Proxy settings and Realm settings in the Admin UI.
- Support for .pfx format for certificates
Automatically puts the certificate and private key into the correct format and validates the certificate.
- FIPS OVA
Separate OVA for FIPS-140-2 mode.
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.