check-circle-line exclamation-circle-line close-line

Release Notes for VMware Unified Access Gateway 3.3.1

Unified Access Gateway | Released on 16 August 2018

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New in This Release

VMware Unified Access Gateway 3.3.1 provides the following new features and enhancements:

  • Configure up to two Syslog servers for Unified Access Gateway from the admin interface
  • Supports editing of IPv4 netmask and gateway from the admin interface. 
  • Admin user password can be reset using the command-line interface.
  • Header-based authentication using SAML: Ability to set the variable attribute for headers for Identity bridging
  • Powershell scripts are included in the product build. uagdeploy.ps1 for vSphere and uagdeployhv.ps1 for Hyper-V. For more information, see the Product Download page.  Note: Hyper-V is for AirWatch only.

Internationalization

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 complete documentation, go to the Documentation Center.

Compatibility Notes

For more information about the VMware Product Interoperability Matrix, go to http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.

Installation and Upgrade

To download Unified Access Gateway, see Product Download page.

Resolved Issues

  • Horizon processes in Unified Access Gateway needed a restart on changing the Horizon configuration, which was causing existing desktop connections through Unified Access Gateway to disconnect.

  • Relay-endpoint configuration for Content Gateway used incorrect SNI rule for relay server. 

  • Intermittent account lockout errors were seen on Unified Access Gateway after Content Gateway service was manually stopped.

  • Unified Access Gateway Hyper-V deployment might fail to apply network settings.

Known Issues

  • VMware Tunnel settings are not automatically enabled when importing a JSON file that contains multiple Web Reverse Proxy settings and Content Gateway settings. While importing a large set of configuration involving web reverse proxy settings, Content Gateway settings, and VMware Tunnel settings, VMware Tunnel settings fail to get enabled on the admin interface.

    Workaround: After importing is complete, enable VMware Tunnel settings manually from the Admin UI. Save the settings.