Omnissa Access On Premises Release Notes

Workspace ONE Access 24.07 | 12 AUG 2024 | Build 9408d8c54af0e2ce6b36e2c437727d8425d79965

Workspace ONE Access Connector (Windows) 24.07 | 12 AUG 2024 | Workspace-ONE-Access-Connector-Installer-24.07.0.0.exe

Check for additions and updates to these release notes.

Omnissa Access 24.07

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.07 is a general maintenance release that includes security updates, connector updates, and other product fixes.

NEW, JULY 10, 2025 - Appliance Patch: A patch is available for CVE-2025-32463. See KB article 6000965 for more information.
In this release, the Omnissa Access virtual appliance has been upgraded to Photon 4.

IMPORTANT: Omnissa Access 24.07 is only available as an upgrade from previous versions. A new installation of the Omnissa Access 24.07 virtual appliance is not supported. See the Upgrade section for the versions supported for upgrade.

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.07 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.07 is compatible with the Omnissa Access Cloud service and with Omnissa Access virtual appliance version 24.07 and later versions.

Virtual Apps Compatibility

Omnissa Access connector 24.07 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, such as VMware vCenter Server and Omnissa Horizon® 8.

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

Installation

New installation not supported

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

The 24.07 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.07 (Photon Linux)

Versions supported for upgrade

To upgrade to Omnissa Access 24.07, the current version of the Omnissa Access virtual appliances must be 22.09.1.0 or 23.09.0.0. Versions prior to 22.09.1.0 must be upgraded to 22.09.1.0 or 23.09.0.0 first, then upgraded to 24.07.

Additionally, legacy connectors (version 19.03.0.1 and earlier) are not compatible and not supported with Omnissa Access virtual appliance version 24.07. Migrate your legacy connectors to version 23.09 (or an earlier, compatible version of the enterprise connector) before upgrading your Omnissa Access virtual appliances to 24.07. After upgrading the virtual appliances to 24.07, upgrade the connectors to 24.07.
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.
Configure existing version

Before you upgrade to version 24.07, make sure that you complete the initial configuration of the 22.09.1.0 or 23.09.0.0 appliance by going to the Omnissa Access URL and completing the Setup wizard. Set up the database connection. Verify that you can log into the Omnissa Access console and the configuration pages at https://accesshostnamefqdn:8443/cfg.
NEW - 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.07. 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.07 (Windows)

Upgrade to Omnissa Access connector 24.07 is supported from versions 23.09.0.0, 22.09.1.0, 22.09.0.0.

See the Upgrading Omnissa Access Connector guide for information.

Legacy Connectors

Omnissa Access 24.07 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-200932: Resolved an issue where Active Directory over IWA directory sync was failing with safeguard violations. A configurable option for comparing only attributes for updates during directory sync is now available.
HW-200972: Prevent parallel sync if both People Search photo sync and directory sync are configured for the same time.
HW-204691: Resolved an issue with directory sync exiting due to communication channel errors. A configurable parameter is available to set the number of hours after which scheduled sync starts automatically if the directory sync service exits due to unexpected communication channel errors.

Known Issues

This release has the following known issues:

horizon service does not start after upgrade

After the upgrade and virtual appliance reboot, the Omnissa Access console displays a 404 error. This issue occurs because the horizon service could not be started. The logs display an error such as the following: Caused by: liquibase.exception.DatabaseException: Cannot drop the sequence sequence_name, because it does not exist or you do not have permission.

NEW - Workaround: Patches are now available for this issue. See Omnissa Knowledge Base Article 6000354 for information on how to resolve the issue and to obtain the patches.
Connections using older versions of ssh and scp clients to the Omnissa Access appliance might not work.

With older versions of the clients, you might get an error such as PuTTY Fatal error: Couldn't agree on host key algorithm.

Workaround: Use the latest versions of the clients.
NEW - 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 For example: ./wizardssl.hzn --makesslcert server.example.com server2.example.com server3.example.com )
Connector services health might not display accurately after upgrading to version 24.07 [Comment]: HW-206749

After you upgrade to Omnissa Access 24.07, the connector services health status might be red on the Connectors page in the admin console.

Workaround: Restart the appliance service for the connector health to display correctly.
1. Log in to the Omnissa Access virtual appliance as the root user.
2. Run the following command:
  
  service horizon-workspace restart
RADIUS (Cloud Deployment) authentication not available for connector in FIPS mode
[Comment]: HW-201833

If Omnissa Access 24.07 connector is running in FIPS mode, the RADIUS (Cloud deployment) authentication method does not work.

Workaround: After upgrading or installing the connector, enable RADIUS (Cloud deployment) authentication in the User Authentication service.
1. In the INSTALL_PATH\User Auth Service\UserAuthService.xml file, add the following JVM argument:
  -Dorg.bouncycastle.jsse.enable_md5=true
  IMPORTANT: Add the line to the JVM arguments section, and not to any other location in the file.
2. Restart the User Authentication service.
3. Repeat these steps for all connector instances that run the User Authentication service.
People Search error after upgrade [Comment]: HW-208855

If People Search was not enabled in your existing installation and you enable it after upgrading to Omnissa Access 24.07, when you configure a directory for People Search and sync, you might get an error.

Workaround: This error occurs if you configure and sync a directory for People Search immediately after enabling People Search. It occurs only the first time that you enable People Search after upgrade. To avoid this issue, wait for 6 hours after enabling People Search before proceeding with configuring the directory.
People Search error Error searching for Sync Results from storage [Comment]: HW-209120

After you upgrade to Omnissa Access 24.07, configure People Search, and sync a directory and photos, you might see the following error on the People Search page: Error searching for Sync Results from storage.

Workaround: You can ignore this error as it might not reflect a real issue.
Step-up authentication for Citrix apps does not work on Windows Hub app [Comment]: HW-209224

If a step-up authentication policy is configured for a Citrix app, the policy does not work correctly while launching the app from the Windows Omnissa Workspace ONE® Intelligent Hub app. When a user clicks the app, the user is not redirected directly to the step-up authentication page, and is unable to launch the app.

Workaround: Users can try to launch the app from the Intelligent Hub web portal.

Documentation

Localized Content

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

Support Contact Information

Contact Support 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?