Omnissa Access On Premises Release Notes

Omnissa Access 24.12 | 19 DEC 2024 | Build db6ab20d5e13c21d85079bad1c65812558831f75

Omnissa Access Connector (Windows) 24.12 | 19 DEC 2024 | Access-Connector-Installer-24.12.0.0.exe

Check for additions and updates to these release notes.

Omnissa Access 24.12

Omnissa Access helps you provide your users faster access to SaaS, web, and native mobile apps with multi-factor authentication, conditional access, and single sign-on.

The Release Notes describe the new features, resolved issues, and known issues in this version of Omnissa Access.

What's New

Omnissa Access 24.12 is a general maintenance release that includes branding and security-related updates, connector updates, and other product fixes.

NEW - DEC 22, 2025: A patch to address CVE-2025-66516 in Apache Tika packages used in Omnissa Access is available.

We have determined that Apache Tika ships with Omnissa Access in a way that significantly mitigates the severity of CVE-2025-66516. Administrative credentials are required to attempt exploitation and there are other safeguards in place that make exploitation more difficult, resulting in a Medium severity CVSS 3.1 score of 6.4/10.

We have made a patch available to update Apache Tika packages to fixed versions in Omnissa Access. Download Patch HW-250276-Appliance-24.12.1.0.zip from the Omnissa Access 24.12 Download page on Customer Connect.
NEW - JULY 10, 2025 - Appliance Patch: A patch is available for CVE-2025-32463. See KB article 6000965 for more information.
NEW - APRIL 2025 - Connector patch: A patch is available for Omnissa Access Connector 24.12 to support the new application partition names in Active Directory Lightweight Directory Services (LDS) introduced with Horizon version 2503. See KB article 6000797 for more information.

The patch applies to Omnissa Access Connector 24.12, regardless of whether the connector is used with the on-premises Omnissa Access 24.12 virtual appliance or with Omnissa Access Cloud. You can download the patch from the Omnissa Access 24.12 page in Customer Connect.
IMPORTANT - Upgrade-only release: Omnissa Access 24.12 is only available as an upgrade from version 24.07. A new installation of the Omnissa Access 24.12 virtual appliance is not supported. See the Upgrade section for more information.
Horizon app launch URL change: As part of the transition to the new company, Omnissa, and related branding changes, the launch URL for launching Horizon apps from the Intelligent Hub portal or app has changed. To support this change, we have introduced a new option in the Omnissa Access console, Enable Horizon Client with Omnissa URL.

By default, the Enable Horizon Client with Omnissa URL option is deselected. The default setting supports both the old and new launch URLs, which means you can continue to use older versions of Horizon Client such as 24.06 in addition to the new 24.12 version.

When the Enable Horizon Client with Omnissa URL option is enabled, app launch uses the new launch URL. Only Horizon Client versions 24.12 and later support the new URL. App launch will fail with earlier Horizon Client versions.

Note: The Enable Horizon Client with Omnissa URL option applies to Horizon on-premises integrations with Omnissa Access.

For more information, see Using the New Omnissa URL for Horizon App Launch.
OS Update: The virtual appliance OS has been upgraded to Photon 5.

Before You Begin

Compatibility

VMware vCenter™ and VMware ESXi™ Compatibility

Omnissa Access appliance supports the following versions of vSphere and ESXi:

Note: For end of support information for vSphere 7.0, see Announcing End of Support Life for vSphere 7.0.

Windows Servers Supported

Omnissa Access connector 24.12 supports the following versions of Windows Server:

Windows Server 2022
Windows Server 2019
Windows Server 2016

Web Browsers Supported

Mozilla Firefox, latest version
Google Chrome, latest version
Safari, latest version
Microsoft Edge, latest version

Databases Supported

Microsoft SQL Server 2016, 2017, 2019, 2022

Directory Servers Supported

Active Directory - Windows Server 2022, Windows Server 2019, and Windows Server 2016, with a Domain functional level and Forest functional level of Windows 2008 and later

Omnissa Access supports a single AD domain, multiple domains in a single AD forest, or multiple domains across multiple AD forests.
OpenLDAP - 2.4
Oracle LDAP - Directory Server Enterprise Edition 11g, Release 1 (11.1.1.7.0)
IBM Tivoli Directory Server 6.3.1

Connector Compatibility

Omnissa Access connector 24.12 is compatible with the Omnissa Access Cloud service and with Omnissa Access virtual appliance version 24.12 and later versions.

Virtual Apps Compatibility

Omnissa Access connector 24.12 supports Omnissa Horizon®, Omnissa Horizon® Cloud Service, Citrix, and Omnissa ThinApp integrations with the Virtual App service.

The following versions of Citrix are supported: Citrix Virtual Apps and Desktops 7 2203, Citrix Virtual Apps and Desktops 7 1912 LTSR, XenApp and XenDesktop 7.15 LTSR, and XenApp and XenDesktop 7.6 LTSR. The following versions of Citrix Gateway are supported: 12.1-62.27, 12.1-65.25, and 13.1-37.38. The connector supports the Citrix StoreFront API and does not support the Citrix Web Interface SDK.

For supported Horizon versions, see the Omnissa Product Interoperability Matrix.

Compatibility Matrix

The Omnissa Product Interoperability Matrix provides details about the compatibility of current and previous versions of products and components.

For system requirements, see the Omnissa Access 24.12 installation guides in the Omnissa Access documentation site.

Installation

IMPORTANT - New installation not supported

A fresh installation of the Omnissa Access 24.12 virtual appliance is not supported. You can only upgrade to version 24.12 from an existing installation. See the Upgrade section for the versions supported for upgrade.
No license required

The 24.12 version does not require a license. The Settings > Appliance > License page has been removed from the Omnissa Access console.

Upgrade

Upgrading to Omnissa Access 24.12 (Photon Linux)

Versions supported for upgrade

To upgrade to Omnissa Access 24.12, the current version of the Omnissa Access virtual appliances must be 24.07. Earlier versions must be upgraded to 24.07 first, then upgraded to 24.12.
Support for offline upgrade only

Online upgrade is not supported for the Omnissa Access virtual appliance in this release. You must use the offline upgrade process described in Upgrading Omnissa Access Offline.
After upgrade, leave the Customer Experience Improvement Program

If you previously opted in to the Customer Experience Improvement Program, you must leave the program after upgrading the virtual appliance to version 24.12. The legacy Customer Experience Improvement Program collected information about your organization’s use of Omnissa products.
1. In the Access admin console, select Settings > Appliance.
2. Select the Customer Experience Improvement Program tab.
3. Deselect the Join the Customer Experience Improvement Program option.

During the upgrade, all services are stopped; plan the upgrade with the expected downtime in mind.

See the Upgrading Omnissa Access guide for more information.

Upgrading to Omnissa Access Connector 24.12 (Windows)

Upgrade to Omnissa Access connector 24.12 is supported from versions 24.07 and 23.09.

See the Upgrading Omnissa Access Connector guide for information.

Legacy Connectors

Omnissa Access 24.12 does not support legacy connectors (version 19.03.0.1 and earlier). The Connectors (Legacy) page has been removed from the Omnissa Access console.

Resolved Issues

This release includes the following resolved issues:

HW-216896: Domain Name field missing from Database Connection Setup page
HW-212817: Client Access FQDN changed when a Horizon pod is removed from a pod federation
HW-215605: Improved error reporting while setting password with hznAdmintool
HW-216924: Resolved an issue that prevented SMTP mail server from being configured successfully

Known Issues

This release has the following known issues:

Unable to regenerate self-signed certificate for the Access virtual appliance from the admin console

After upgrade, you cannot regenerate the self-signed certificate for the virtual appliance from the Access console.

Workaround: Generate the certificate from the command line.
1. Using an SSH client, log in to the Omnissa Access appliance as the root user.
2. Update the ownership for the ssl directory and the root_ca_key.pem and root_ca.pem files:
  1. chown horizon-cfg:www /usr/local/horizon/conf/ssl
  2. chown horizon-cfg:www /usr/local/horizon/conf/root_ca_key.pem
  3. chown horizon-cfg:www /usr/local/horizon/conf/root_ca.pem
  4. cd /usr/local/horizon/conf/ssl
  5. chown horizon-cfg:www *
3. Change directory:
  cd /usr/local/horizon/scripts/secure
4. Run the following command to generate the self-signed certificate:
  ./wizardssl.hzn --makesslcert dnsname dnsname dnsname
  
  For example:
  ./wizardssl.hzn --makesslcert server.example.com server2.example.com server3.example.com

Documentation

Localized Content

See KB article 6000664: Announcing Omnissa Localization Support for information about localized content.

Support Contact Information

Contact Support at Omnissa Customer Connect when you need help with your Omnissa Access environment. See How to file a Support Request in Customer Connect and via Cloud Services Portal.

Was this page helpful?