Skip to main content

September 4, 2026

Omnissa Unified Access Gateway Release Notes

Unified Access Gateway 2606 | 24 AUG 2026

Unified Access Gateway appliances provide users with secure remote access to virtual desktops, internal sites, applications, and file repositories. To learn more, see Unified Access Gateway Documentation.

Omnissa Unified Access Gateway Release Notes provide information about the new features and enhancements in each release. This page contains a summary of the new capabilities, issues resolved, and known issues that are reported in each version.

What's New

Unified Access Gateway 2606 provides the following new features and enhancements:

General

  • AlmaLinux 9.6 Operating System upgrade
    The Unified Access Gateway appliance operating system has been upgraded from AlmaLinux 9.2 to AlmaLinux 9.6. The upgrade maintains full deployment compatibility across all supported hypervisors and preserves existing system hardening, authentication, password management, FIPS enablement, and STIG compliance behavior.

  • Enhancement to log rotation and disk space management
    Improved log management mechanisms to monitor disk utilization and trigger early log rotation, helping prevent storage from filling up in large-device environments.

  • Logging and troubleshooting improvements

  • Updates to OS package versions and Java component versions

Horizon

  • Update SSL Server certificate and key without service restart
    Unified Access Gateway now supports TLS certificate replacement without interrupting existing user sessions. Existing sessions remain connected while new sessions use the updated certificate. If a network interruption occurs after renewal, an automatic reconnect can fail because Horizon Client still expects the previous certificate. The Horizon Client user can reconnect by selecting the entitlement again. See TLS/SSL Certificates.

  • Native QCOW2 image for KVM-based hypervisors
    Unified Access Gateway is now available as a native QCOW2 image, eliminating the need for manual image conversion when deploying to KVM-based hypervisors. Nutanix AHV is qualified and supported in this release.
    Starting with UAG 2606, Nutanix AHV deployments use the QCOW2 image. Nutanix is no longer listed on the vSphere/AWS/Google Cloud OVA - existing AHV customers should switch to the QCOW2 artifact at their next deployment or upgrade. See PowerShell deployment to Nutanix AHV.

  • Support for ECC TLS certificates and ECDSA Cipher Suites
    Elliptic Curve Cryptography (ECC) TLS certificates together with ECDSA cipher suites are now supported, in addition to the existing RSA-based certificates.

  • Support for multiple signing certificates in IdP metadata
    When an external identity provider IdP metadata that includes more than one signing certificate is uploaded, all of them are now considered for SAML authentication during Admin UI login.

  • Dedicated SAML signing certificate configuration
    Added support for configuring a dedicated signing certificate for SAML authentication with an external identity provider (IdP). Using the TLS certificate for SAML signing remains supported when a dedicated certificate is not configured.

Content Gateway

In this release, we have made a few updates containing overall security and stability with no new features.

Before You Begin

Resolved Issues

  • PPAT-22168: Stop sending Tunnel-related logs to stdout and stderr in UAG.
  • PPAT-21439: Improved DTR validation workflow where a non-matching protocol specifier (such as UDP:*) stopped evaluation of the other domains in the same DTR rank.
  • AST-25524: Error "UAG settings imported partially due to one or more errors observed while trying to persist settings" is displayed when exporting a JSON configuration from UAG admin console and importing the same file back without any modifications.
  • UAG-13396: Stack trace disclosure from an API, under certain conditions.
  • UAG-13133: If certain configurations are updated in rapid succession, the health status might show an incorrect state.
  • UAG-13953: When UAG SAML configuration is read through certain APIs, the system triggers false-positive CONFIG_CHANGE audit log entries.

Known Issues

  • PPAT-21429: Syslog over TCP fails when sent directly from Tunnel service.
    Workaround:
    1. On Workspace ONE UEM console, go to Tunnel configuration and select the Syslog Hostname as localhost.
    2. On UAG Admin console, go to Advanced Settings > Syslog server settings and select the Protocol as TCP.

Documentation

Documentation for Unified Access Gateway is located at Omnissa Product Documentation.

Support Contact Information

To receive support, access Customer Connect.

For information about filing a Support Request in Customer Connect and using Cloud Services Portal, see the Knowledge Base (KB) article 6000005.

Localization

For details on Omnissa’s localization strategy, see Announcing Omnissa Localization Support.

Was this page helpful?

Provide feedback for this topic

Was this topic helpful?

Please do not include any personal or confidential information.

Generating link…