Unified Access Gateway | Released on 17 November 2020
Check for additions and updates to these release notes.
What is in the Release NotesThe release notes cover the following topics:
- What's New in This Release
- Compatibility Notes
- Unified Access Gateway Lifecycle Support Policy
- Installation and Upgrade
- Sizing Options
- Technical Resources
- Resolved Issues
- Known Issues
What is New in This Release
VMware Unified Access Gateway 2009.1 includes bug fixes, which is documented in the Resolved Issues section.
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.
For more information about the VMware Product Interoperability Matrix, go to http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
Lifecycle Support policy
For information about the Unified Access Gateway Lifecycle Support policy, go to https://kb.vmware.com/s/article/2147313.
Installation and Upgrade
To download the Unified Access Gateway, see the Product Download page.
For the Unified Access Gateway sizing recommendations, go to VMware Configuration Maximums.
To learn and master Unified Access Gateway, go to https://techzone.vmware.com/mastering-unified-access-gateway
When Unified Access Gateway processes a huge number of DNS requests by Workspace ONE Tunnel service, a buffer overflow condition occurs in the Unified Access Gateway appliance. This issue has been fixed now.
If a backslash (\) character is used when setting an admin password, root password, or RADIUS shared secret, then it must be escaped by using an extra backslash character. So, the admin must specify a password like Secret\123 as Secret\\123.
Workaround: Prefix \ with an extra backslash \ (for example, \\u).
When Unified Access Gateway is deployed in Microsoft Azure using DHCP allocated IP addresses and there is a conflict between any custom static routes and DHCP assigned routes, then the static routes can be removed after they have been applied. This only happens if there is a mismatch between the Unified Access Gateway hostname and the hostname assigned by Azure based on the VM name.
Workaround: Ensure that the Azure VM name based hostname matches the uagName (hostname) set when Unified Access Gateway is deployed so that a hostname change is not performed.
The location of waagent.log is /var/log/waagent.log, which is a link to /opt/waagent/log/waagent.log. However, /opt/waagent does not exist and therefore a log file is not created.
Workaround: The log file is not needed, but if it is ever required, log into the Unified Access Gateway console as root and remove the link by using the following command: rm /var/log/waagent.log.
When Unified Access Gateway is deployed on Microsoft Azure, on first boot, the Microsoft Hypervisor is correctly detected by Unified Access Gateway and within the Hypervisor, based on a DHCP setting, Azure is correctly detected. However, on subsequent boot, Azure is incorrectly detected as Hyper-V and waagent is stopped. This is a minor issue as waagent is mainly used to apply configuration settings on first boot only.
When Horizon SAML 2.0 is used with Horizon True SSO to avoid the initial AD password prompt, if the session is manually locked or locks due to inactivity, the user must either enter their AD password to unlock the session or close the client and reconnect. The Horizon True SSO unlock mechanism currently depends on Workspace ONE Access.