Digital Employee Experience Release Notes

Release notes for digital employee experience (DEX) platforms

Get this feed:

Products (12)

Latest Digital Employee Experience Updates

May 28, 2026
- Date parsed from source:
  May 28, 2026
- First seen by Releasebot:
  May 28, 2026
ControlUp

Custom Hive 1248 (May 28)

ControlUp adds custom hive upgrade guidance and marks cloud hive compatibility for supported features starting with Custom Hive 1241.
Important

Upgrade: For details on downloading and upgrading your custom hive, see Upgrade Custom Hives.

Cloud hive compatibility: Some features also apply to our cloud hives and are marked accordingly, starting with Custom Hive 1241.

Original source
May 27, 2026
- Date parsed from source:
  May 27, 2026
- First seen by Releasebot:
  May 29, 2026
Omnissa

Omnissa Identity Service | MAY 2026

Omnissa Identity Service adds Google Workspace integration for automated user provisioning and SSO, expands SCIM 2.0 migration options across cloud identity providers, and improves identity management with common identifier selection, user notification settings, and broader workspace support.
Omnissa Identity Service | MAY 2026

Check for additions and updates to these release notes.

Urgent Notification regarding legacy Domain End of Service

As part of the migration from legacy VMware owned domains to Omnissa owned domains, customers’ network and security teams must make firewall changes to allow access to the new Omnissa owned domains by June 15th, 2025, to prepare and not block the new Omnissa domain network requests in upcoming product and service updates. This also impacts any API driven tasks or automation tasks created. Please see KB6000840 for more information.

What’s New in May 2026

Omnissa and Google Workspace Integration for New Environments

You can now connect Omnissa Identity Service directly to Google Workspace to automate user lifecycles and enable seamless federated authentication.

What’s Supported

Automated Provisioning (SCIM): Real-time, one-way sync from Google to Omnissa Identity Service. This automatically creates, updates, deletes, activates, and deactivates users to eliminate manual overhead and secure your perimeter.

Single Sign-On (SAML): Users log into Omnissa services instantly using their existing Google Workspace credentials.

Current Limitations

No Groups: Google Workspace does not support SCIM group provisioning, so sync is limited to individual users.

Protocols: Built strictly on SAML. OpenID Connect (OIDC) and Workspace ONE UEM Password Grant flows are not supported.

Migration to Google Workspace from your current Workspace ONE UEM and Omnissa Access integrations is not yet supported.

Setup Guides

Omnissa: Integrating Omnissa Identity Service with Google Workspace

Google: Google Workspace Help Center App Integration Guide

What’s New in March 2026

Migration to SCIM 2.0 for Workspace ONE UEM customers with Omnissa Access configured (Limited Availability)

Omnissa Identity Service now supports directory migration from on-premises Active Directory to cloud Identity Providers supporting SCIM 2.0 for existing customers with Workspace ONE UEM and Omnissa Access configured.

This feature allows organizations to centralize identity management, eliminate on-premises dependencies, and streamline user provisioning and authentication.

This feature has been added to the Limited Availability program. Use the Omnissa Beta Program to check requirements and apply.

Key Benefits for Workspace ONE UEM and Omnissa Access Customers

Cloud-Native Provisioning: Provision users and groups from your cloud IDP to Workspace ONE UEM using SCIM 2.0, replacing legacy Active Directory sync.

No On-Premises Components: Eliminate the need for AirWatch Cloud Connector and Omnissa Access Connector for authentication and user sync.

Centralized Management: Manage users and groups from Omnissa Connect, a unified web-based portal for all Omnissa services.

Federated Authentication: Enable seamless SSO into Omnissa services using your cloud IDP as the identity provider.

Migration Process

The migration process is guided by a wizard in Omnissa Connect and includes:

Completing prerequisites (such as IDP setup and attribute mapping)

Integrating your cloud IDP with Omnissa Identity Service

Comparing directory data between Workspace ONE UEM, Omnissa Access, and Omnissa Identity Service

Executing the migration in stages (authentication switch, provisioning cutover)

Minimum downtime is expected during the migration.

Unsupported Features and Limitations

Before migrating, review the following limitations:

No Rollback: Once provisioning is migrated to Omnissa Identity Service, rollback to Active Directory is not possible.

Immutable externalId: For Microsoft Entra ID, the externalId in Entra ID must match the original Active Directory value.

Feature Gaps- Workspace ONE UEM: Some Workspace ONE UEM features are not supported post-migration. See the Unsupported Features list for details.

Feature Gaps - Omnissa Access: Features that are not supported post-migration include the following.

Local users and administrators

Dynamic groups

Directory administrators (administrators are provisioned from Omnissa Connect)

Password (cloud deployment) and Password (Local Directory) authentication methods

People Search

See the Unsupported Features list for more information.

Sync via Airwatch Provisioning Adapter from Omnissa Access to Workspace ONE UEM is not supported.

Learn More

For detailed setup instructions, prerequisites, and best practices, see the documentation:

Migrating Directories to Omnissa Identity Service (Limited Availability)

Workspace ONE UEM: Omnissa Identity Service with Directory Services

What’s New in January 2026

Okta and generic SCIM Identity Provider migration to Omnissa Identity Service (Limited Availability)

Omnissa Identity Service (OIS) now extends Workspace ONE UEM directory migration support beyond Microsoft Entra ID to include Okta and generic SCIM 2.0–compliant identity providers, enabling Workspace ONE UEM customers to modernize identity architectures using their existing cloud IDPs. This enhancement allows organizations to migrate away from on-premises Active Directory while preserving their preferred identity provider for user lifecycle management and authentication.

This feature is in Limited Availability. Use the Omnissa Beta Program to review requirements and apply for access.

Key Benefits for Workspace ONE UEM Customers

Cloud-Native Provisioning: Provision users and groups from Okta or a generic SCIM IDP into Workspace ONE UEM using SCIM 2.0, replacing legacy Active Directory–based synchronization.

No On-Premises Components: Eliminate the need for AirWatch Cloud Connector and other on-premises directory infrastructure.

Centralized Identity Management: Manage users, groups, and directory integrations from Omnissa Connect, a unified web-based portal for all Omnissa services.

Federated Authentication: Enable seamless single sign-on (SSO) into Omnissa services using Okta or a supported SCIM-based identity provider as the authentication source.

Migration Process

The migration experience is guided by a wizard in Omnissa Connect and follows a consistent framework across supported identity providers. The staged approach is designed to minimize disruption, with minimal expected downtime during the migration window.

Note: By default, an email notification is sent to users when they are provisioned into Workspace ONE UEM through Omnissa Identity Service. You can customize or disable this notification. For details, see Workspace ONE UEM Directory Services Configuration for information.

Unsupported Features and Limitations

Before migrating, review the following limitations:

Omnissa Access Integration: If any directories or identity providers are configured in Omnissa Access, migration is not supported. Migration scenarios involving Workspace ONE UEM plus Access will be supported in a future release.

No Rollback: Once provisioning is migrated to Omnissa Identity Service, rollback to the previous directory (Active Directory or legacy sync) is not supported.

Immutable External Identifier: The SCIM externalId provided by Okta or the generic IDP must remain immutable and must match the existing directory identifier in Workspace ONE UEM.

Feature Gaps: Some Workspace ONE UEM directory-dependent features are not supported post-migration. Review the Unsupported Features list before proceeding.

Learn More

For detailed setup instructions, prerequisites, and best practices, see the following documentation:

Migrating Directories to Omnissa Identity Service (Limited Availability)

Integrating Omnissa Identity Service with Okta

Integrate Omnissa Identity Service with a Generic Identity Provider

Workspace ONE UEM: Omnissa Identity Service with Directory Services

Ability to select common identifier during migration to Omnissa Identity Service

Omnissa Identity Service now supports using an attribute other than distinguishedName as the unique, common identifier to match existing Workspace ONE UEM users and groups with those synced from your cloud identity provider. You can select the common identifier during Step 1: Complete Directory Prerequisites of the migration process. This feature is available for all supported cloud identity providers.

What’s New in December 2025

Support for Workspace ONE UEM Basic users in new environments

Omnissa Identity Service now supports Workspace ONE UEM Basic user accounts in Identity Service-integrated Workspace ONE UEM environments, extending the support to new organizations. Previously, Workspace ONE UEM Basic user accounts were supported only in migration environments.

To use this feature, enable the Basic user authentication for UEM option in Step 4: Select Authentication Protocol of the Omnissa Identity Service integration wizard. When this option is selected, federated users are authenticated by the third-party identity provider, while Basic users are authenticated by Workspace ONE UEM Basic user authentication.

For more information, see Configuring Authentication for Workspace ONE UEM Basic Users.

Extension of Platform SSO support in Workspace ONE environments with user sync through Identity Service (SCIM 2.0)

We are now extending support for Workspace ONE UEM to configure Platform SSO using Omnissa Access as an IdP for environments that sync users and groups via SCIM 2.0 with Identity Service.

Administrators use Workspace ONE UEM to configure and manage Platform SSO, deploying the necessary profiles and settings to Macs. Platform SSO extends single sign-on directly to the macOS login, meaning the user’s IdP password becomes synchronized with their Mac password. It can facilitate the creation of local macOS user accounts directly from the IdP and can also synchronize IdP password policies and enforce them on the local password.

Note: Omnissa Identity Service must be integrated with a third-party identity provider that supports the OpenID Connect (OIDC) protocol.

See Configuring Apple macOS Platform Single Sign-On with Omnissa Access for more information.

Support for Horizon 8 SSO to Azure VMs joined to Entra ID

Horizon 8 has added support for Single Sign-On to Entra ID-joined desktops and applications when the Windows client is launched using Omnissa Identity Service and Workspace ONE Access. Users are synced from Entra ID and authenticate through Omnissa Access. They can launch their Horizon desktops and applications without needing to re-enter Entra ID credentials inside the desktop. This streamlines access for environments built on Entra ID and gives on-prem organizations a smoother path when delivering Azure-based Horizon resources. See SSO to Microsoft Entra ID joined desktops and applications through Workspace ONE Access in the Desktops and Applications in Omnissa Horizon 8 documentation.

What’s new in November 2025

URL Migration Dashboard

As part of the migration from legacy domains to Omnissa domains, URLs are being updated in Omnissa Access and Omnissa Identity Service for customers in selected cloud regions. These changes require you to update your integrations with Identity Providers. A Migration dashboard is available in the Identity Service admin console for impacted regions to guide you through the migration process.

See KB article 6001062 for detailed information about the migration process and timeline.

Action Required:

Review KB article 6001062.

In the Identity Service console, select Migration Support to access the Migration dashboard.

Follow the instructions in the dashboard to complete the migration. See the KB article for additional information.

IMPORTANT: We strongly encourage you to start migration as soon as possible. See KB article 6001062 for the cutover timeline.

What’s New in September 2025

Omnissa Identity Service opens in new tab

You can now launch Omnissa Identity Service directly from the Omnissa Connect menu in a separate tab to manage end-user directory configurations and view details. In Omnissa Connect, select Identity Management > End User Management, then click Launch End User Management.

Horizon 8 App Support

Omnissa Identity Service now supports Omnissa Access integration with Horizon 8, enabling users to access virtual desktops and published applications:

Natively with Horizon Client

Through Workspace ONE Intelligent Hub

This integration is only supported with Horizon 8 pods that have True SSO enabled.

Additional attributes are required for the Omnissa Access integration with Horizon 8. For more information, see:

User Attribute Mapping for Omnissa Identity Service

Set up Your Omnissa Access Environment for Horizon Integration - Omnissa Access tenants that have Omnissa Identity Service enabled

Note: If Okta is configured as the third-party identity provider in Omnissa Identity Service, Omnissa Access integration with Horizon 8 is not supported.

What’s New in July 2025

Active Directory Migration to Microsoft Entra ID (Limited Availability)

Omnissa Identity Service (OIS) now supports directory migration from on-premises Active Directory to Microsoft Entra ID, enabling a modern, cloud-first identity architecture for Workspace ONE UEM customers. This feature allows organizations to centralize identity management, eliminate on-premises dependencies, and streamline user provisioning and authentication.

This feature is in Limited Availability. Use the Omnissa Beta Program to check requirements and apply.

Key Benefits for Workspace ONE UEM Customers

Cloud-Native Provisioning: Provision users and groups from Microsoft Entra ID to Workspace ONE UEM using SCIM 2.0, replacing legacy Active Directory sync.

No On-Premises Components: Eliminate the need for AirWatch Cloud Connector.

Centralized Management: Manage users and groups from Omnissa Connect, a unified web-based portal for all Omnissa services.

Federated Authentication: Enable seamless SSO into Omnissa services using Microsoft Entra ID as the identity provider.

Migration Process

The migration process is guided by a wizard in Omnissa Connect and includes:

Completing prerequisites (such as Entra ID setup and attribute mapping)

Integrating Microsoft Entra ID with Omnissa Identity Service

Comparing directory data between Workspace ONE UEM and Omnissa Identity Service

Executing the migration in stages (authentication switch, provisioning cutover)

Minimum downtime is expected during the migration.

Note: By default, an email notification is sent to users when they are provisioned to Workspace ONE UEM through Omnissa Identity Service. You can customize the email or turn off the notification. See Workspace ONE UEM Directory Services Configuration for information.

Unsupported Features and Limitations

Before migrating, review the following limitations:

Omnissa Access Integration: If any directories or identity providers are configured in Omnissa Access, migration is not supported. Workspace ONE UEM plus Access migration will be supported in a subsequent release.

No Rollback: Once provisioning is migrated to Omnissa Identity Service, rollback to Active Directory is not possible.

Immutable externalId: The externalId in Entra ID must match the original Active Directory value.

Feature Gaps: Some Workspace ONE UEM features are not supported post-migration. See the Unsupported Features list for details.

Learn More

For detailed setup instructions, prerequisites, and best practices, see the documentation:

Migrating Directories to Omnissa Identity Service (Limited Availability)

Workspace ONE UEM: Omnissa Identity Service with Directory Services

User Notification Settings for Users Provisioned to Workspace ONE UEM

You can now configure whether end users receive an email notification when their accounts are provisioned in Workspace ONE UEM through Omnissa Identity Service. By default, a user activation email is sent upon provisioning. You can customize the email or turn off the notification. See Workspace ONE UEM Directory Services Configuration for information.

What’s New in January 2025

Integration with Horizon Cloud Service Next-Gen

Move to Omnissa Connect

Integration with Horizon Cloud Service Next-Gen

Horizon Cloud can now leverage Omnissa Identity Service to integrate with Microsoft Entra ID to sync users and groups and configure federation for end users. Omnissa Identity Service is available as another identity provider option in Horizon Cloud Service next-gen, in addition to the existing identity provider options. The service is available for tenants with no previous Identity Management configuration in the Horizon Cloud Control Plane next-gen.

In the Omnissa Connect console, select End User Management, configure the integration with Entra ID, select Horizon, and add the necessary information to your Horizon Cloud Control Plane next-gen to complete the integration.

The following configuration is supported:

Microsoft Entra ID as the third-party identity provider integrated with Omnissa Identity Service
Okta and generic SCIM 2.0 identity providers are not currently supported.

OpenID Connect as the authentication protocol

Enabling Intelligent Hub
However, the Enforce Intelligent Hub setting, which forces users to access their apps through Intelligent Hub, is not currently supported.

For more information, see:

Configuring User Provisioning and Identity Federation with Omnissa Identity Service

Using Horizon Control Plane next-gen - Horizon Cloud Service and Cloud-Connected Horizon 8

Move to Omnissa Connect

Omnissa Identity Service is now part of Omnissa Connect, a new web-based service that provides a centralized access point for all Omnissa services and solutions. In the Omnissa Connect console, select End User Management in the left pane to access and configure Omnissa Identity Service.

Your existing Omnissa Identity Service configuration has not changed with the move from Workspace ONE Cloud Admin Hub, the Workspace ONE Cloud console, to Omnissa Connect.

For more information, see:

Omnissa Connect: Designed to simplify your digital workspace

Omnissa Connect documentation

Omnissa Identity Service documentation

What’s New in December 2024

New provisioning app for Okta integration

New Status tab for provisioning errors

New provisioning app for Okta integration

We are excited to announce the availability of a new provisioning app, the Omnissa Identity Service app, in the Okta Integration Networks App catalog! The app makes it easier for you to set up user provisioning from Okta to Omnissa by including preconfigured settings.

To get started with your provisioning app, search for “Omnissa Identity Service” in the Okta App catalog, then select the app.

Read more about how to integrate Omnissa Identity Service with Okta in the Identity Service documentation.

New Status tab for provisioning errors

You can now use a new Status tab to monitor real-time provisioning errors. The tab displays information about the provisioning status from Omnissa Identity Service to the services that you selected to use with it (Workspace ONE UEM or Access), as well as error details for user, group, and membership objects.

We have also added an error banner on the Identity Service summary page that displays the total error count across downstream services.

For example:

What’s New in September 2024

Password Grant Flows

When an Omnissa Workspace ONE® UEM tenant is integrated with Omnissa Identity Service, end users are redirected to your Identity Provider (IdP) for SAML authentication when enrolling or checking out devices. A SAML-redirection is not possible on the device or client in some authentication flows. The Password Grant Flow feature, when enabled, allows SCIM-provisioned users to authenticate against your IdP when SAML-redirection is not available. Additionally, it enables certain basic user authentication flows. See Support for Certain Workspace ONE UEM Username and Password-based Flows for details of these flows. Also see Configure Workspace ONE UEM Settings for Omnissa Identity Service for information on how to configure the new Password Grant setting.

What’s New in April 2024

SAML Authentication Context for Generic Identity Provider Integrations

If you integrate a generic SAML 2.0 identity provider with Omnissa Identity Service and select SAML as the authentication protocol, you can now choose between the following authentication context types: unspecified, PasswordProtectedTransport, or a custom value.

The authentication context indicates how a user is authenticated at an identity provider. The identity provider includes the authentication context in an assertion at the request of a service provider or based on the configuration at the identity provider.

Note: You can change the authentication context for existing configurations.

What’s New in February 2024

Ability to deactivate Omnissa Identity Service from the console

We’ve now made it possible for you to deactivate Omnissa Identity Service from the Workspace ONE Cloud console. After deactivating Omnissa Identity Service, you can set up directory provisioning and federated authentication from Workspace ONE UEM and Omnissa Access directly. You might need to deactivate Omnissa Identity Service in the following scenarios:

Your use cases are not supported by Omnissa Identity Service.

You want to sync users and groups directly from Active Directory.

You want to configure directory services and identity federation in Workspace ONE UEM or Omnissa Access, instead of the Workspace ONE Cloud service.

Here’s how you do it: Deactivating Omnissa Identity Service

What’s New in December 2023

Omnissa Identity Service public APIs

Token expiry notification for administrators

Omnissa Identity Service public APIs

We are happy to announce the release of Omnissa Identity Service public APIs, bringing the power of automation to your Workspace ONE Cloud integration with cloud identity providers that use the SCIM 2.0 protocol.

The following use cases are available for the API integration:

Configure a provisioned directory of users and groups using the System for Cross-domain Identity Management (SCIM 2.0) protocol.

Manage identity provider configuration for federated authentication into Omnissa products and services.

Leverage centralized user management and authentication for Omnissa Access and Workspace ONE UEM.

You can create an OAuth 2.0 client in the Workspace ONE console to get API access to get started.

To learn more about the new APIs, see Omnissa Identity Service APIs.

Note: The Omnissa Identity Service APIs are available to new Omnissa Access or Workspace ONE UEM customers, and to existing customers that have already onboarded Omnissa Identity Service.

Token expiry notification for administrators

We now send notifications to administrators when the secret token used for directory synchronization is about to expire or has expired. Notifications are sent to the administrator by email and also appear as a banner in the Workspace ONE Cloud console.

Administrators can opt out from receiving email notifications.

What’s New in October 2023

New Flow for Okta Integration with Workspace ONE Cloud

We are excited to announce that a new Okta flow is now available in the Workspace ONE Cloud console to support integration with Okta! This flow makes it easier for you to provision users and groups from Okta to Workspace ONE Cloud and authenticate users using Okta. Prior to this release, Okta was tested and documented for the generic SCIM 2.0 Identity Provider flow.

Get familiar with the new flow by reading Integrating Omnissa Identity Service with Okta in the Omnissa Identity Service documentation.

Note: The Okta integration is available for new customers or customers that have already onboarded to Omnissa Identity Service.

What’s New in June 2023

Audit events for provisioning to downstream products and services

Omnissa Identity Service introduces audit events to track successes and failures in pushing data from Workspace ONE Cloud to downstream products and services such as Workspace ONE UEM and Omnissa Access. Admins can use the audited information to identify, track, and debug provisioning-based issues. Audit events support filtering based on the object name, object type, downstream service, and errors. A detailed view of audit events provides error states.

See Viewing Audit Events for Omnissa Identity Service for more information.

What’s New in April 2023

New provisioning app for Microsoft Entra ID integration

We are excited to announce the availability of a new provisioning app in the Microsoft Entra App Gallery! The app makes it easier for you to set up user provisioning from Microsoft Entra ID to Omnissa Identity Service by including preconfigured settings.

Read more about how to integrate Omnissa Identity Service with Microsoft Entra ID in the documentation.

Introducing Omnissa Identity Service - January 2023

We’re introducing a new service that makes user provisioning and identity federation easier for new customers of Omnissa Access and Workspace ONE UEM! You can now leverage Omnissa Identity Service to configure a provisioned directory of users and groups based on SCIM 2.0 in the Workspace ONE Cloud console. Omnissa Identity Service will then automatically provision the users and groups, as well as authentication settings, to your Workspace ONE UEM and Omnissa Access admin consoles.

While integrating with your third-party identity provider, you confirm the user attributes to synchronize into Omnissa Identity Service.

Take a look at some of the use cases:

Create and configure a provisioned directory of users and groups using the System for Cross-domain Identity Management (SCIM) 2.0 protocol.

Manage identity provider configuration for federated authentication into Omnissa products and services.

Leverage centralized user management and authentication across Omnissa products and services.

Currently, Omnissa Identity Service supports Workspace ONE UEM and Omnissa Access for centralized user management and authentication from the Workspace ONE Cloud console for newly-created environments.

Supported identity providers and directory sources:

Microsoft Entra ID, a cloud-based identity service in Microsoft Azure

Generic SCIM 2.0 identity source (tested for Okta)

Important:

Omnissa Identity Service is only available for new Workspace ONE Cloud environments.

Omnissa Identity Service is not available for Managed Services Provider customers at this time.

To get started with Omnissa Identity Service, log into your organization’s Workspace ONE Cloud Admin Hub, the Workspace ONE Cloud console, and select Accounts > End User Management.

Click Get Started and use the wizard to set up the integration with your identity provider.

Known Issues

Unsupported features

When Omnissa Identity Service is enabled, some features are not supported in Omnissa Access, Workspace ONE UEM, Omnissa Workspace ONE® Hub Services, and Omnissa Workspace ONE® Intelligent Hub and portal. See Configuring User Provisioning and Identity Federation with Omnissa Identity Service for more information.

After you select a service such as Omnissa Access or Workspace ONE UEM to use with Omnissa Identity Service and save your selection, you cannot deselect it.

Solution: Contact Support to reset the selection.

Deleting a user in Microsoft Entra ID does not delete the user from Omnissa Identity Service

When you delete a user in Microsoft Entra ID, the account is suspended for a specific period of time before being deleted. The user is deactivated in Omnissa Identity Service, too, for that period of time. In Microsoft Entra ID, the username of the deleted user is also modified, and the changes are reflected in Omnissa Identity Service. See How Microsoft Entra ID Users are Deleted for more information.

Deleting user and group attribute values in Microsoft Entra ID does not delete the values in Omnissa Identity Service

In Microsoft Entra ID, when you delete a user or group attribute value that was already synced to Omnissa Identity Service, the value is not deleted in Omnissa Identity Service and downstream services. Microsoft Entra ID does not propagate null values.

Solution: Instead of clearing the value completely, enter a space character.

Okta integration requires two apps

When you integrate Omnissa Identity Service with Okta, you must create separate apps in the Okta Admin console for user provisioning and identity provider configuration. You cannot use the same app for provisioning and authentication.

Login_hint feature does not work

When you integrate a third-party identity provider with Omnissa Identity Service using the OpenID Connect protocol, the login_hint feature does not work. If the relying party sends a login_hint, Omnissa Identity Service does not pass it to the identity provider.

Deleting an attribute mapping in Microsoft Entra ID or Okta does not remove the attribute from users in Omnissa Identity Service

When you delete an attribute mapping from the provisioning app in Microsoft Entra ID or Okta, the changes are not propagated to Omnissa Identity Service. The attribute is not deleted for users in Omnissa Identity Service and downstream services.

Documentation

See Configuring User Provisioning and Identity Federation with Omnissa Identity Service in the Omnissa Identity Service documentation site.

Internationalization

Omnissa Identity Service is available in the following languages:
Czech, French, Polish, Simplified Chinese (China), Danish, Italian, Portugese, Chinese (Taiwan), German, Japanese, Russian, English, Korean, Swedish, Spanish, Dutch, Turkish

To view the documentation in your preferred language, select the language icon at the top-right of the page.

Localized Content for Omnissa Docs

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 Identity Service environment. See How to file a Support Request in Customer Connect and via Cloud Services Portal.
Original source
All of your release notes in one feed

Join Releasebot and get updates from ControlUp and hundreds of other software products.

Create account
Get updates with:
May 21, 2026
- Date parsed from source:
  May 21, 2026
- First seen by Releasebot:
  May 22, 2026
SysTrack by Lakeside Software

DEX Pack Release Notes May 2026

SysTrack adds updates to DEX Packs for AVD Assessment and Management, Hardware Refresh, Proactive IT, Secure Boot Certificate, and Zoom Quality. The release refines dashboards, fixes data accuracy issues, improves filtering and performance, and introduces a new proactive Zoom Call Quality pack.

This release includes updates to DEX Packs.
Content name Content type Details of update AVD Assessment and Management DEX Assessment Summary:
- Changed - Dashboard removed.

Sizing Recommendation:
- Changed - Updated the dashboard widgets and workflow to align with the Hardware Analysis dashboard in the Hardware Refresh DEX Pack.
- Changed - Added suggested CPU and memory target ranges based on historical usage.
- Changed - Simplified recommendation categories to relevant VM options:
- Decrease resource
- Increase resource
- No change
- Changed - Application table now respects earlier dashboard selections, including recommendation category and system.
- Fixed - Fixed issues in the application table.

Session Host Dashboard:
- Optimized queries to improve performance.
- Updated column headers for clarity.
- Revised descriptions for improved accuracy and readability. Hardware Refresh DEX Fixed - Memory upgrades now display correct information for systems with 16 GB of installed memory. Proactive IT DEX Fixed - Software install counts now match between the Outdated Software Summary grid and the pie chart. (16260) Secure Boot Certificate DEX - Changed - Added indicators that show the number of systems checked and fixed by SysTrack.
- Changed - Added a pie chart that shows the number of systems in each state and filters the table based on the selected state.
- Changed - Moved the Group filter to the top so it filters the entire dashboard.
- Changed - Updated step filtering so the table shows all systems or only the selected step. Zoom Quality DEX New - This DEX Pack offers a proactive evaluation of Zoom Call Quality Original source
May 20, 2026
- Date parsed from source:
  May 20, 2026
- First seen by Releasebot:
  May 22, 2026
Omnissa

Experience Management 26.02 for macOS

Omnissa releases Experience Management for macOS 26.02 with an updated agent code base, new proxy awareness guidance for macOS devices, and refreshed minimum requirements for Workspace ONE, Intelligent Hub, macOS Sonoma, and Intelligence integration.
Experience Management for macOS Release Notes describe the new features and enhancements in each release. This page contains a summary of the new capabilities, issues that have been resolved, and known issues that have been reported in each release.

Urgent Notification regarding legacy Domain End of Service

As part of the migration from legacy VMware owned domains to Omnissa owned domains, customers’ network and security teams must make firewall changes to allow access to the new Omnissa owned domains by June 15th, 2025, to prepare and not block the new Omnissa domain network requests in upcoming product and service updates. This also impacts any API driven tasks or automation tasks created. Please see KB6000840 and KB6000802 for more information.

Experience Management 26.02 for macOS

New Features

We’ve updated the Experience Management for macOS agent code base.

If you use a proxy server in your Experience Management deployment, you must configure proxy awareness on the macOS device.

For details, access Use a proxy server? You must configure proxy awareness on the device.

Minimum Requirements

Minimum Requirements for Experience Management 26.02 for macOS

Omnissa Workspace ONE Experience Management for macOS package

Omnissa Workspace ONE Intelligent Hub for macOS 24.11.3 or later

macOS Sonoma, version 14 or later

Omnissa Intelligence tenant opted-in and Desktop Advanced Telemetry integration card activated

Resolved Issues

We are always working to improve Experience Management with every release. There are no major bug fixes to report.

Known Issues

DCP-11462: There is a known issue concerning the reporting of NIC models and manufactures as “unknown” in wi-fi network adapter events. For details, see the KB article Wi‑Fi NIC Model and Manufacturer Showing as “Unknown” on Apple Silicon (M1) macOS Devices.

Download Instructions

Omnissa Workspace ONE Experience Management 26.02 for macOS is available as a resource on Customer Connect.

Original source
May 20, 2026
- Date parsed from source:
  May 20, 2026
- First seen by Releasebot:
  May 22, 2026
Omnissa

Omnissa Access 24.12.1.0

Omnissa Access 24.12.1.0 adds security and branding updates, new patches, and product fixes. It also brings updated Access Connector and Access Desktop releases, plus resolved issues for directory sync and virtual app services.
Omnissa Access 24.12.1.0 | 11 SEP 2025 | Build 49efda362374f8d76a5a23fecc282b330acfe913

Omnissa Access Connector (Windows) 24.12.1.0 | 02 SEP 2025 | Access-Connector-Installer-24.12.1.0.exe

Omnissa Access Desktop 24.12.1.0 | 11 SEP 2025 | Omnissa-Access-Desktop-24.12.1.exe

Check for additions and updates to these release notes.

Urgent Notification regarding legacy Domain End of Service

As part of the migration from legacy VMware owned domains to Omnissa owned domains, customers’ network and security teams must make firewall changes to allow access to the new Omnissa owned domains by June 15th, 2025, to prepare and not block the new Omnissa domain network requests in upcoming product and service updates. This also impacts any API driven tasks or automation tasks created. Please see KB6000840 for more information.

Omnissa Access 24.12.1.0

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.

Note: Omnissa Access 24.12.1.0 is an update release, resulting in abbreviated release notes. The contents of the Omnissa Access 24.12 Release Notes apply to this version too.

What’s New

Omnissa Access 24.12.1.0 includes branding and security-related updates and other product fixes.

NEW - MAY 20, 2026: A new patch containing security updates is now available. HW-261052-Appliance-24.12.1.0.zip also includes all previously-released patches and can be applied on top of any existing patches.
Download Patch HW-261052-Appliance-24.12.1.0.zip from the Omnissa Access 24.12 Download page on Customer Connect. For detailed instructions, see KB article 6001156.

NEW - FEB 20, 2026: A new patch containing security updates is now available. HW-253749-Appliance-24.12.1.0.zip also includes all previously-released patches and can be applied on top of any existing patches.
Download Patch HW-253749-Appliance-24.12.1.0.zip from the Omnissa Access 24.12 Download page on Customer Connect.

NEW - JAN 21, 2026: A new patch, HW-251347-Appliance-24.12.1.0.zip, is now available for Omnissa Access 24.12.1.0. This cumulative patch combines all previously-released patches including HW-250276-Appliance-24.12.1.0.zip and HW-247745-Appliance-24.12.1.0.zip, and also includes additional fixes. You can apply this patch on top of any patches you might have already applied.
The older patches are no longer available for download separately.
You can download the new patch from the Omnissa Access 24.12 Download page on Customer Connect. For detailed instructions, see KB article 6001156.

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 - DEC 12, 2025: A new patch is now available for the Omnissa Access 24.12.1.0 virtual appliance. Patch HW-247745-Appliance-24.12.1.0.zip:

Contains a fix for Authenticator App based two-factor authentication failure

Resolves the issue of the TCP over TLS syslog configuration option not working

Includes multiple OS and package-level upgrades to the latest available versions
Download Patch HW-247745-Appliance-24.12.1.0.zip from the Omnissa Access 24.12 Download page on Customer Connect.

IMPORTANT Upgrade-only release for virtual appliance: Omnissa Access virtual appliance 24.12.1.0 is only available as an upgrade from the versions listed in the Upgrade section. A new installation of the Omnissa Access 24.12.1.0 virtual appliance is not supported. However, other components such as the Omnissa Access connector and Omnissa Access Desktop are available as new installations with this release.

New version of Omnissa Access Connector: Omnissa Access Connector 24.12.1.0 is available with this release and includes the fixes listed in Resolved Issues. You can perform a new installation of version 24.12.1.0, or upgrade from the versions listed in the Upgrade section.

New version of Omnissa Access Desktop: Omnissa Access Desktop 24.12.1.0 is available with this release and has specific compatibility requirements as listed in Omnissa Access Desktop Compatibility. Desktop 24.12.1.0 is available as a new installation only. Uninstall your old version, then install version 24.12.1.0.

Branding updates: The 24.12.1.0 release includes further rebranding changes related to the launch of Omnissa as a new company. Among other changes, a new option to renew Omnissa Access SAML signing and encryption certificates is now available. Renewing a certificate also updates the certificate to Omnissa branding.

Compatibility

Omnissa Access virtual appliance 24.12.1.0 is compatible with:

Omnissa Access Connector 24.12.1.0 and earlier versions. It does not support a later version of the connector.

Omnissa Access Desktop 24.12.1.0 and later versions. It does not support Workspace ONE Desktop Client 23.09 or earlier versions. (Omnissa Access Desktop was formerly named Workspace ONE Desktop Client.)

Omnissa Access Connector 24.12.1.0 is compatible with:

Omnissa Access virtual appliance 24.12.1.0 and later versions

Omnissa Access Cloud

Omnissa Access FedRAMP

Omnissa Access Desktop 24.12.1.0 is compatible with:

Omnissa Access virtual appliance 24.12.1.0 and later versions only. A workaround is available if you want to use it with virtual appliance version 24.12.0.0. See Omnissa Access Desktop Compatibility for information.

ThinApp packages created with Omnissa ThinApp 24.12 and later versions only. If you have ThinApp packages that were created with an older version, you must create new packages with ThinApp 24.12.

Installation

Omnissa Access virtual appliance: A new installation of the Omnissa Access 24.12.1.0 virtual appliance is not supported. You can only upgrade to version 24.12.1.0 from an existing installation. See the Upgrade section for the versions supported for upgrade.

Omnissa Access Connector: A new installation of Omnissa Access Connector 24.12.1.0 is supported, in addition to upgrade. You can download the connector from Omnissa Connect.

Omnissa Access Desktop: A new installation of Omnissa Access Desktop 24.12.1.0 is supported. You can download the Desktop from Omnissa Connect.

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

Upgrade

Upgrading to Omnissa Access Virtual Appliance 24.12.1.0 (Photon Linux)

Upgrade to Omnissa Access virtual appliance 24.12.1.0 is supported from the following versions:

24.12.0.0

24.07
Earlier versions must be upgraded to version 24.07 first, then upgraded to 24.12.1.0.

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.1.0 or 24.12.0.0. The legacy Customer Experience Improvement Program collected information about your organization’s use of Omnissa products.

In the Access admin console, select Settings > Appliance.

Select the Customer Experience Improvement Program tab.

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 information about the upgrade process.

Upgrading to Omnissa Access Connector 24.12.1.0 (Windows)

Upgrade to Omnissa Access Connector 24.12.1.0 is supported from the following versions:

24.12.0.0

24.07

23.09
See the Upgrading Omnissa Access Connector guide for information about the upgrade process.

Important: Omnissa Access Connector 24.12.1.0 is compatible with Omnissa Access virtual appliance version 24.12.1.0 and later versions, Omnissa Access Cloud, and Omnissa Access FedRAMP.

Legacy Connectors

Omnissa Access 24.12.x 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.

Connector - Directory Sync service:

HW-230769: Prevent directory sync failure when a deleted user continues to have group membership

HW-215396: Allow manual override of domain controller auto-discovery in krb5.conf file

HW-216294: During Active Directory password reset from Intelligent Hub, limit domain controller discovery retries

HW-201638: Add safeguards check to photo sync

HW-223982: Limit the number of directory sync alerts to 1,000

Connector - Virtual App service:

HW-222985/HW-225845: Support the new Omnissa-based application partition names in Active Directory Lightweight Directory Services (LDS) introduced with Horizon 2503 (see KB article 6000797).

Known Issues

This release has the following known issues:

Authenticator App based two-factor authentication might fail after upgrade to Omnissa Access 24.12.1.0
Solution: Patch HW-247745-Appliance-24.12.1.0.zip resolves this issue. Download the patch from the Omnissa Access 24.12 Download page on Customer Connect.

The TCP over TLS option in the syslog configuration in Omnissa Access does not work
Solution: Patch HW-247745-Appliance-24.12.1.0.zip resolves this issue. Download the patch from the Omnissa Access 24.12 Download page on Customer Connect.

Unable to reset the lost root or sshuser password for the Omnissa Access virtual appliance
Solution: If you have lost the root or sshuser password to the Omnissa Access virtual appliance, try to reset the password using the Photon OS instructions. In those instructions, replace the following command:

/sbin/pam_tally2 --reset --user username

with

faillock --user username --reset

where username is either sshuser or root.

Documentation

Omnissa Access documentation

Omnissa Workspace ONE® Hub Services 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.
Original source
May 17, 2026
- Date parsed from source:
  May 17, 2026
- First seen by Releasebot:
  May 17, 2026
Aternity

Release News for Aternity Sentiment Module for macOS

Aternity adds the Sentiment Module for macOS, giving organizations secure sentiment surveys for employees with customer branding and custom notifications for new surveys. It requires the Unified Agent and Aternity Module for macOS and is compatible with macOS 26.3 or later.
Aternity Sentiment Module for macOS allows organizations to create sentiment surveys and engage securely with the employees.

Deploy the tool AFTER installing the Unified Agent and Aternity Module for macOS. Make sure to follow the branding guidelines and the instructions on how to show the tool icon in the system tray.

Learn more about the tool.

What's New in Aternity Sentiment Module for macOS 26.3 (RC)

The Aternity Sentiment Module for macOS 26.3 includes several features, including:

Customer branding

Custom notifications for new surveys

Compatibility

Aternity Sentiment Module for macOS 26.3 is compatible with Unified Agent for macOS 26.3 or later and with Aternity Module for macOS 26.3 or later.
Original source
May 17, 2026
- Date parsed from source:
  May 17, 2026
- First seen by Releasebot:
  May 17, 2026
Aternity

What's New in Aternity Digital Assistant Client for Mac

Aternity launches Digital Assistant for Mac 1.0, bringing customizable employee sentiment surveys, custom branding, and custom notifications for new surveys. The Mac client supports secure IT engagement and works with Agent for Mac 4.4 or later.
The Aternity Digital Assistant for Mac allows organizations to create sentiment surveys for their employees. With the sentiment surveys organizations can ask employees questions on various topics including support. The surveys are customizable allowing organizations to tailor them to fit their particular requirements. The responses from employees are collected and analyzed to provide valuable insights into employee sentiment.

Aternity Digital Assistant for Mac requires Agent for Mac 4.4.0 or later. Deploy both Agent for Mac and the Digital Assistance Tool. Make sure to follow the branding guidelines and the instructions on how to show the tool icon in the system tray. This software lets the IT department engage securely with the organization's employees.

Learn more about the tool.

View resolved issues in this release.

To deploy the more advanced Aternity Sentiment Module for macOS instead of Aternity Digital Assistant Client, it is necessary to install the Unified Agent for macOS first (learn more).

What's New in Aternity Digital Assistant for Mac 1.0 (General Availability)

Released as General Availability in November 2025

The Aternity Digital Assistant for Mac Client 1.0 includes several features, including:

Customer branding

Custom notifications for new surveys

Note: Several features of the Aternity Digital Assistant for Windows client are not supported by the Mac client, including: custom proxy settings, log-level management, and hidden app bar icons.

Agent compatibility

Aternity Digital Assistant for Mac is compatible with the Agent for Mac 4.4 or later.
Original source
May 2026
- No date parsed from source.
- First seen by Releasebot:
  May 14, 2026
1E

9.2 release notes

1E releases the on-premises 9.2 update with a major accessibility overhaul for Section 508 compliance, including improved screen reader support, keyboard navigation, contrast, zoom and accessible charts, plus faster analytics and multiple reliability and security fixes.
Accessibility - Section 508 compliance

The on-premises 9.2 release is focused primarily on accessibility, delivering significant UI improvements to issue a Voluntary Product Accessibility Template (VPAT) attesting to Section 508 compliance.

These enhancements ensure that users with visual impairments or other disabilities can interact with the product as effectively as any other user. This release introduces support for a range of assistive technologies and best practices, including:

Screen readers (text-to-speech): UI elements are properly labeled so content can be accurately interpreted and read aloud.

Color contrast: Updated color usage meets contrast ratio standards for improved legibility.

Clear, consistent labeling: Form fields, buttons, and controls use unambiguous labels throughout the interface.

Optimized text spacing: Improved spacing and layout aids readability for users with cognitive or visual impairments.

Keyboard navigation: Full keyboard accessibility allows users to navigate and operate the product without a mouse.

Together, these changes provide a more inclusive experience, allowing all users to interact confidently and independently with the product. For more information, refer to Section 508 compliance.

To access the VPAT compliant version of the UI, users can use the following URL:

https://tachyon.sdl.local/Tachyon/AccessibleApp

To access the previous version, the URL remains unchanged. Both UIs are supported.

Type of accessibility | Summary

Color contrast | Enhanced contrast across UI elements ensures text and visual components are clearly distinguishable from their backgrounds, improving readability and meeting accessibility standards for users with visual impairments.

Keyboard accessibility | All UI elements can now be fully navigated using a keyboard alone, with no mouse required. Navigation follows a logical, predictable sequence across components, reducing cognitive load and ensuring a consistent, confusion-free experience for keyboard-dependent users and those using assistive technologies.

Screen reader accessibility | The UI has been enhanced for full compatibility with leading screen readers, including JAWS and NVDA. All interactive elements and images include consistent, descriptive labels and alternative text across every screen, enabling accurate auditory output for visually impaired users. Charts displaying dynamic data now additionally expose their underlying data as a readable table, ensuring no information is lost for screen reader users. These improvements allow visually impaired users to interact with the application effectively and independently, without reliance on sighted assistance.

Zoom levels | The UI adapts across a range of zoom levels, ensuring all content remains fully visible and functional without loss of information or usability. This reduces cognitive strain and allows users with visual impairments to read and navigate the application with confidence.

Charts | Every chart used to visualize or summarize data now includes an alternative tabular view, ensuring the underlying data is fully accessible. The tabular view is navigable via keyboard and compatible with screen readers, providing an equivalent experience for users who cannot interact with graphical representations.

Versions and support

The Client has not been released as part of the 9.2 release. It is recommended to use the Client 25.5 Long-Term Service Branch (LTSB) for this release. The next Client LTSB version is planned for the Platform 26.5 release, and it will be supported. To download the latest toolkit, please use the Support Portal.

It is recommended that customers using version 9.1 should upgrade to 9.2. The only supported upgrade path to 9.2 is from 9.1 SP2.

Operating system | 1E Client build version

Windows | 26.3.0.19

macOS | 26.3.0.19

Linux:

Redhat Enterprise Linux 8

Redhat Enterprise Linux 9

SLES 15

Ubuntu 22

| 26.3.0.19

MSVCRT version is 14.44.35208.0 for this 1E Client release.

Improvements and fixes

New and updated product packs are available in the TeamViewer DEX Hub.

Fixes include:

Experience Analytics device event logs load significantly faster due to optimized database indexing (PLAT-15361).

Fixed pagination issue in User Engagement Surveys list view (PLAT-15986).

Patch Insights search box now displays KB number/Title options faster with correct pagination (PLAT-16967).

Endpoint Automation dashboard rendering improved for large device counts (PLAT-16405).

Business Intelligence Consolidator processing time significantly reduced by stored procedure optimization (PLAT-20440).

User device data now displays correctly for users with multiple primary devices in Experience Analytics (PLAT-21251).

Tachyon Sync connector SQL syntax error fixed to prevent sync failures (PLAT-22055).

HTTPOnly flag added to cookies containing sensitive authentication information in web application (PLAT-22430).

Instructions targeted at many devices now reliably delivered (PLAT-22686).

Catalog sync reliability improved for large datasets during Global Catalog resync (PLAT-25799).

ServiceNow CMDB Gateway Connector device sync timeout errors fixed with new database indexes (PLAT-26170).

Content Distribution fixed to handle long OS names exceeding column limits (PLAT-27659).

Announcements with management group filters now load engagement data correctly (PLAT-26776).

Fixed issue allowing users with input privileges to bypass client-side validation and execute elevated commands (PLAT-23395).

Original source
May 13, 2026
- Date parsed from source:
  May 13, 2026
- First seen by Releasebot:
  May 15, 2026
Omnissa

Omnissa Horizon 8 Release Notes

Omnissa releases Horizon 8 2512.1 as a maintenance update that expands Nutanix AHV support and adds new controls, security, and admin tooling across Connection Server, Horizon Console, Windows and Linux agents, plus Amazon WorkSpaces Core and remote desktop features.

With Horizon 8, IT departments can run remote desktops and applications in the data center and deliver these desktops and applications to employees. End users gain a familiar, personalized environment accessible from any number of devices, anywhere within the enterprise or home. Administrators gain control, efficiency and security by centralizing data in the data center.

Important Notes
• The Horizon 2512 Agent is now supported with both the 2503 ESB Server and the 2512 Server versions. See Compatibility Matrix for Various Versions of Horizon 8 Components for more details.
• Horizon 8 2512 with Nutanix automated pools or farms: A pairing mechanism change in 2512.1 requires that Connection Servers and Agents must both be updated to 2512.1 for ongoing provisioning operations to work. To prepare your environment for limited backward compatibility, see KB article 6001315.
• Horizon 8 is not supported with vSphere 6.5 or vSphere 6.7, which are both past the end of General Support. Horizon 8 Instant Clones are incompatible with vSphere 6.5 and vSphere 6.7 so you must upgrade to vSphere 7.0 or later before upgrading to Horizon 8 if you are using Instant Clones.
• For information about the combined offering of Omnissa Horizon with VMware vSphere Foundation for VDI, including licensing, packaging, and frequently asked questions, see KB article 6000381.

What’s New - 2512.1
Horizon 8 2512.1 is a maintenance release.

What’s New - 2512
Support for Nutanix AHV
Horizon 8 support for Nutanix AHV is now generally available. This release also adds the following features to Horizon’s support for Nutanix AHV:
• Support for Automated RDSH Farms, including published applications and desktops
• App Volumes published apps on demand
• ClonePrep customization for Pools and Farms
• Sysprep profile management through Horizon Console
• Overlay network support
• VM Hosted Apps (published Apps against Nutanix single-session Desktop pools)
• Horizon in FIPS-enabled mode
• Horizon Recording
• Workspace ONE Intelligence Horizon monitoring
• Horizon Cloud Help Desk
• DEX for Horizon

Note: Customers upgrading from Horizon 8 2506 with Nutanix Limited Availability functionality enabled will need to upgrade Horizon Agents immediately after upgrading Horizon Connection Server, due to changes in communication between Server and Agents:
• Non-persistent pools: Upgrade (or create new) Golden Image with 2512 Agent, initiate a Push Image task to update the pool
• Persistent pools: Upgrade Horizon Agent from 2506 to 2512 on each deployed VM. Upgrade (or create new) Golden Image with 2512 Agent for future pool expansion.

Horizon Connection Server
• This release includes Workspace ONE Assist integration for Horizon 8 with Horizon Cloud-connected customers. Administrators can now initiate secure remote support sessions directly from the Horizon Cloud Universal Console to an active Horizon 8 VDI desktop. This enhancement streamlines troubleshooting, eliminates the need for third-party tools, and boosts support efficiency across all environments.
• This release enhances the Helpdesk REST API to return detailed log-on segment metrics in a structured format. The updated endpoint provides breakdowns for Authentication, Brokering, Protocol Connection, GPO Load, Logon Script, Profile Load, and Interactive Session. This enables you to better monitor, diagnose, and reduce VDI log-on delays.
• This release adds per-Pod SAML configuration in Horizon, allowing administrators to define SAML settings at the Pod level instead of for each individual Connection Server. This enhancement increases flexibility, supports tenant- or Pod-specific identity requirements, and maintains full backward compatibility. It also strengthens security, improves customization options, and better aligns with varied enterprise authentication needs. Additionally, this release now fully supports the use of special characters in Dynamic Metadata URLs.
• Starting with Horizon 8 2512, encrypted backup files are not recoverable by earlier installations once the data recovery password has been modified. When upgrading to 2512 or later, it is important to ensure that all Connection Servers in the pod or cluster are upgraded before changing the data recovery password.
• This release improves accessibility compliance in Horizon 8 Connection Server in alignment with DCSA and WCAG 2.0 standards. Enhancements address previously unmet guidelines to raise the VPAT compliance score above 50%. This work supports an inclusive user experience, ensures continued eligibility for federal use, and meets mandated requirements from the CIO and federal agencies.
• The installer now automatically transfers the Schema Master FSMO role to the local LDAP instance before uninstalling existing Connection Server services during an upgrade. This prevents upgrade failures that could otherwise leave the server unresponsive. If the Schema Master role cannot be transferred, the installer aborts safely and preserves the existing services, ensuring stability during parallel upgrades.
• Favicon health checks have been moved from Tomcat to a secure gateway, providing a more efficient process. Originally, /favicon.ico polling was being processed by Tomcat, which increased load during frequent health checks. By implementing this change, overall response times are faster, back-end load is reduced, and load balancers can now poll more frequently without the previous constraint of two balancers at 30-second intervals.
• Horizon 8 now supports the policy Access Based on User Location for Automated Desktop, Manual Desktop, RDS Desktop, and Application Pools. Administrators can configure settings for Internal Access (via Horizon Connection Server), External Access (via UAG), or both. For instance, bank users on the office network may access all banking applications, whereas those connecting from home have access to email only.
• This release enhances Horizon logging for client restrictions. New audit events are recorded in the Events DB and forwarded to Syslog for SIEM visibility. Logs capture client block/warn actions details with version, IP, policy, and reason metadata. Event types include version recommendations, unsupported clients, and certificate policy outcomes.
• The default lifetime of the vdm certificate is now set to 6 months. This change enhances security by requiring certificates to be renewed more frequently, reducing the risk associated with long-lived credentials. This update aligns with current industry trends favoring shorter certificate lifetimes.
• Added role-based access control (RBAC) feature to Horizon Recording, to help admins to configure who can access Horizon Recording Console and what tasks different user groups are authorized to perform. With role-based access control, you can create roles and selectively assign privileges and create permissions and access level to specific Active Directory user groups.
• This release adds support for Single Sign-On to Entra ID joined desktops and applications when the Windows client is launched using Omnissa Workspace ONE Access. Users authenticate through Omnissa Access and can launch their Horizon desktops and applications without needing to re-enter Entra ID credentials inside the desktop. This streamlines access for environments built on Entra ID and gives on-prem organizations a smoother path when delivering Azure-based Horizon resources. Awaiting Microsoft GA rollout (tentative: By end of Jan 2026). See SSO to Entra ID joined desktops and applications through Workspace ONE Access section in the Desktop and Applications Guide.
• Broker-Managed Client Upgrade: Horizon Connection Server now supports the management of client upgrades for Windows and Mac clients. Administrators can enforce version policies, host installer files for desktop clients, and prompt users to update when their client version is blocked.
• This release introduces the ability to Find Machines with the grid showing the assigned users of a particular group based on group ID. Filtering and sorting is not available across columns in the Find Machines grid for the REST API in the Users and Groups workflow.

Horizon Console
• Administrators can now disable/enable load index-based RDSH session load balancing at an RDSH Farm level through Horizon Console or Horizon REST API. Previously, administrators could only disable load index-based RDSH session load balancing at a Pod level via an ADAM DB change. Additionally, the RDSH session bucketing attributes now adapt as required to ensure an even load distribution during both low and high usage periods. See Load Balancing Settings for more details.
• This release introduces server-side column-level filtering and sorting support for grid views, replacing the previous global client-side filter. The enhanced REST API now enables accurate filtering and sorting across individual columns in workflows such as Machines and Inventory. This improves data clarity, usability, and consistency as more workflows transition to server-driven UI operations.
• Administrators can now select a vGPU profile directly in the Horizon console during Instant Clone desktop pool creation or push image workflows. Previously, vGPU profiles were inherited from snapshots. This enhancement adds a vGPU profile dropdown as part of the compute profile definition when creating an Instant Clone pool, or when preparing a push image operation. This allows a single vGPU golden image to be used with different pools whilst allowing for different vGPU profiles, and removes the need to update golden images just to change vGPU profile.
• Administrators can now enable Workspace ONE UEM management directly from the Horizon Console when creating persistent (dedicated) desktop pools. This enhancement extends Workspace ONE UEM across physical devices, mobile endpoints, and Horizon VDI, delivering a unified Day-2 management experience through a single console. The integration ensures consistent policy application from day one, simplifies operations, enhances compliance and security, and reduces total cost of ownership.
• Auto Agent Upgrade is now available with expanded agent source support. In addition to Omnissa-hosted CDS and full URLs, administrators can define a UNC path to use an SMB file share for agent delivery. The Horizon console allows downloading the agent, selecting the share, and configuring it as the upgrade source.

Horizon Agent for Linux
• Support for NVIDIA Blackwell GPUs: The Horizon Agent for Linux now supports NVIDIA Blackwell GPUs in all Linux distributions. This means that Linux VDI workloads can use the latest GPU architecture.
• This release includes the URL redirection feature for the Linux Agent. Now, URLs opened in the Omnissa Horizon Linux agent’s browser can be redirected to open on the Omnissa Horizon client machine, based on user-configurable settings.
• Updated NVIDIA vGPU Support: Horizon Agent 2512 adds support for NVIDIA vGPU versions 16.12, 18.5, 19.3, and 19.4.

Horizon Agent for Windows
• Passwordless installation: Unmanaged agents can now be installed on domain-joined machines without Horizon Administrator credentials, using pre-allocation. The agent installer can also discover its pre-allocated pod or cluster.
• Horizon clients can now get and report their public IP addresses. The Horizon Agent for Windows now gets and reports the client machine’s public IP address as part of the DEX telemetry. The Horizon Client DEEM plug-in obtains the public IP from the DEEM agent when a user connects to a remote session and forwards it to the agent, which then reports it to Workspace ONE Intelligence (INTEL/WS1). Administrators gain improved visibility into connection sources, helping them monitor user activity, respond to incidents, and maintain compliance requirements.
• Windows 10 End of Support: Microsoft ended mainstream support for Windows 10 in October 2025 and now offers Extended Security Updates (ESU). Horizon extends its support for Windows 10 from release 2512 through Agent 2603, but only when the operating system is covered by Microsoft ESU. For more information, see KB 6001105.
• Agent Auto Upgrade: Agent Auto Upgrade now includes pre-flight validation checks. If a pre-flight check fails, both the agent update and the VM update are marked as failed. Pre-flight checks include:
◦ Insufficient disk space detection
◦ Windows Update in-progress check
◦ Pending reboot validation
◦ Invalid or unreachable UNC path checks
• Support for NVIDIA Blackwell GPUs: The Horizon Agent for Windows now supports NVIDIA Blackwell GPUs on Windows 10, Windows 11, and Windows Server guest operating systems. This allows high-performance graphics workloads on the latest GPU generation.
• Horizon V2 Agent now supports the ability to run a post-customization script. Administrators can configure a script to run after the Agent has completed customization, including Azure AD join, on-prem AD join, hybrid join, Instant Clone domain join, and LCM “skip domain join” scenarios. This capability is controlled using new JSON configuration fields and registry values for execution and status tracking.
• Enhanced USB Redirection for RDS Hosts: The Horizon Agent for Windows (RDSH) now supports redirecting multiple USB devices that share the same Vendor ID (VID) and Product ID (PID). Previously, only a single device with a matching VID/PID pair could be redirected to a session. This enhancement allows environments using identical USB hardware (such as scanners, HID devices, or custom peripherals) to attach multiple instances simultaneously.
• Updated NVIDIA vGPU Support: Horizon Agent 2512 adds support for NVIDIA vGPU versions 16.12, 18.5, 19.3, and 19.4.
• Windows 11 25H2 and Windows Server 2025 Support: Full support has been added for Windows 11 25H2 and Windows Server 2025, including Single-Session Desktops, Multi-Session Farms, and App Mode configurations. Support for Windows 11 22H2 has ended.

Horizon 8 on Amazon WorkSpaces Core
• Provisioning operations have been enhanced to deliver significantly faster pool creation times. In some cases, provisioning time has been reduced by as much as 60%, improving efficiency and scalability. See KB 600123 for additional information.
• Agent Auto Upgrade for Horizon 8 on Amazon WorkSpaces Core dedicated pools is now supported. This feature allows administrators to automatically update the Horizon agents on WorkSpaces instances. The WorkSpaces instances need to be in the available state to use this feature. See Auto Upgrade Horizon Agent for more information.
• Administrators can now configure Power Optimized - Hourly Pools with zero online spares to reduce costs. By setting the spare count to “0” and selecting the option to provision all machines up front, all machines will be provisioned and then suspended to minimize ongoing expenses. When a user entitlement is launched, the WorkSpaces instance is powered on and delivered to the user on demand, ensuring cost efficiency without compromising availability. Power Scheduler is no longer needed and your entitlements are available whenever required.
• Administrators can now enable Workspace ONE UEM management and enroll machines directly from the Horizon Console when creating dedicated desktop pools.
• Helpdesk Remote Assistance is now available with Horizon 8 on Amazon WorkSpaces Core. You can generate remote assistance tickets for connected desktop or application sessions. Administrators can use remote assistance to take control of a user’s desktop and troubleshoot problems.
• Omnissa Horizon 8 on Amazon WorkSpaces Core now supports hybrid Microsoft Entra deployments in both Federated and Managed modes

Remote Desktop Features
• This release introduces GPO-based control to map URL redirection to an existing connected VDI session. URLs redirect to the most recently connected VDI when multiple sessions exist, or fall back to a defined default VDI when none are active. If no default applies, users can choose to launch in a VDI or local browser.
• Enhanced BENIT Transport Switching: The enhancement of BENIT switching to maintain performance amidst fluctuating network conditions.The BENIT transport switching logic can use the TCP connection quality to help it switch the active transport between TCP and BEAT. This approach allows for a more flexible adaptation of the Blast transport to the current network conditions, enhancing the end-user experience in varying network environments. This enhancement applies only to Windows Horizon Agent and All Clients.
• Blast Compatibility with NVIDIA GPUs on vSphere/VCF 9.x: Horizon now supports Blast connections using NVIDIA vGPUs on vSphere and VMware Cloud Foundation (VCF) 9.x. This update enables GPU-accelerated Blast performance across supported guest operating systems, including Windows 10, Windows 11, Windows Server, and supported Linux distributions.
• Horizon now supports Blast Extreme Adaptive Transport (BEAT) over Reverse Connection. Previously, Reverse Connection supported only TCP-based Blast. BEAT now works in Reverse Connection deployments without requiring any additional configuration, aside from ensuring outbound UDP connectivity from the agent to the UAG.
• Updated NVIDIA VideoSDK Support and Enhanced Blast Encoding Capabilities: Blast now upgrades to NVIDIA VideoSDK 13, replacing the legacy SDK 8 support and enabling use of both SDK 12 and SDK 13. This update includes improvements to encoder presets and tuning profiles as recommended by NVIDIA, resulting in improved compression efficiency to deliver higher video quality at lower bitrates.
• Dynamic Time Zone Redirection for RDSH: Added support for dynamic time zone redirection in RDSH (multi-session) environments to ensure the user’s client time zone, including dynamic DST rules, is accurately applied in the session. (This is already supported in VDI single session.)
• Vvc Raw Channel support for Blast MKS/Audio is now supported on Mac and mobile clients, and in deployments using UAG.
• Some of the performance enhancements in Vvc Raw Channels have been extended to all other Vvc-based features on TCP.
• Support for MS Teams Zoom Feature: Horizon Agent now supports the Zoom feature when using the Omnissa WebRTC Teams Optimization.
• Manual Noise Suppression Control: Horizon now adds support for manually disabling Noise Suppression when using Horizon Teams Optimization (WebRTC 1.0).

Windows OS Optimization Tool for Omnissa Horizon
• This release adds support for Windows 11, version 24H2 and later.

Resolved Issues - 2512.1
The numbers included before the resolved issues refer to the issues logged in the Omnissa internal issue tracking system.
• AST-8489: Addressed an issue where certain UWP applications, including Microsoft Photos, HEVC Video Extensions, and HEIF Image Extensions, could take up to 15–20 minutes to register after user logon when the Windows image was optimized using the “Keep all Store apps” option.
• HZN-7784 - vCenter managed manual desktop pools could not be created with the 3D Renderer set to NVIDIA GPU because the virtual machine grid did not display any vGPU-compatible VMs. Also, editing and saving an automated pool (Instant Clone or Full Clone) with vGPU enabled could fail, resulting in the error “max_number_of_monitors cannot be set if grid_vgpus_enabled is set to true,” even though the Max number of monitors field was grayed out and could not be changed in the UI.
• HZN-7808 - Horizon Connection Server, operating in Workspace ONE, incorrectly reported the error “Your Horizon Client version does not support the features of this Horizon Connection Server. Please upgrade your Client.” Subsequent desktop or application launches were blocked after the user’s SSO credentials became locked following the initial launch.
• HZN-7810 - In the Admin Console, unable to sort machines by the Pending Image column on the Machines tab for Instant Clone pools.
• HZN-7844 - Published Apps on Demand from App Volumes 2512 failed to launch and displayed the error message, “The application could not be launched, possibly because it is missing or misconfigured.”
• HZN-7478 - Nutanix FIPS mode desktop pools fail to customize resulting in timeout errors.
• VCART-10256 - Nutanix Clone Prep desktop pool was getting stuck in “Hybrid domain join in progress”.

Resolved Issues - 2512
The numbers included before the resolved issues refer to the issues logged in the Omnissa internal issue tracking system.
• HZN-7190 - Horizon Connection server may experience high CPU usage caused by SamlReconfigure.
• HZN-5129 - Unable to change AD container from default of CN=Computers in Horizon Console when creating a Nutanix pool.
• HZN-5146 - Spare VMs are generated during the reprovisioning phase following a push operation in an on-demand instant-clone pool.
• HZN-5409 - Users may observe that machine assignments changed from readable username to GUID.
• HZN-5591 - Slow loading of user sessions in the Admin UI is significantly impacting helpdesk staff productivity and user access.
• HZN-5776 - Users may experience intermittent issues with on-demand power on/off functionality within their Horizon VDI sessions.
• HZN-6120 - Unable to save vTPM flag value set during push operation scheduled through REST API.
• HZN-6137 - The Helpdesk tool is failing to properly disconnect VMs between pods, resulting in session errors.
• HZN-6202 - Some users experienced upgrade failures requiring replica server removal and subsequent standard server upgrades.
• HZN-6331 - Provisioning error banner not cleared on admin console though provisioning was sucessful later after fixing provisioning error.
• HZN-6444 - An instant clone becoming unavailable and reporting as “Agent Disabled” in the Horizon console, even though the VDI appears to be functioning correctly
• HZN-6726 - Cluster Identity certificate shows not in use in the Horizon console even after replacing it with a CA-signed cert.
• HZN-6733 - A maximum of 10 networks are shown for selection during Nutanix pool creation workflow.
• HZN-6734 - RDS servers with active user sessions are moved into disabled state when push operation is performed with “wait for users to log off”; however, their status continues to appear as “Available” in the Horizon admin UI.
• HZN-6911 - The pool power policy is configured to power off; however, when users log off, the VDI desktops remain powered on instead of shutting down.
• HZN-6931 - Some users may have experienced difficulties associating network labels with Full Clone desktops during pool creation.
• HZN-6958 - New full-clone persistent VDIs created through API or Network Label Tool deploy on the master template’s VLAN instead of the pool’s updated VLAN.
• HZN-7024 - Logon segment metric data may intermittently disappear within a few minutes, impacting reporting accuracy.
• HZN-7053 - The Horizon Admin console incorrectly displays no events, preventing users from quickly identifying issues within the cluster.
• HZN-7075 - Despite Password Cache being enabled and TrueSSO mode being disabled in Workspace ONE, TrueSSO login is still being initiated.
• HZN-7189 - When administrators search for users and try to select the user’s VM session, they may encounter an error if the VM is running RHEL 9.6.
• HZN-7275 - Users reported a slow System Health Dashboard after upgrading to 2503.1.
• HZN-7356 - Some users are unable to reset their desktops from the Workspace ONE Access Hub Console.
• HZN-7365 - Connection via F5 to connection server is not working after upgrade to 2503.
• UBI-585 - Refresh OS disk after n days setting for Nutanix pools causes refresh after logoff.
• UBI-680 - Unable to re-register a Nutanix golden image with Connection Server.

Known Issues
The numbers included before the known issues refer to the issues logged in the Omnissa internal issue tracking system.
Before upgrading to this release, please review the information in KB 6000681 and Upgrading to Omnissa Horizon 8 2412 and Later.

Horizon Connection Server
• HZN-5160: Sorting and filtering capabilities have been removed for specific columns in administrative grids. This results in a loss of functionality compared to previous releases and may impact administrative workflows.
Workaround: None
• HZN-7443: If a VM is stuck in Customization state, delete the VM from Horizon Admin Console or Horizon REST API. Horizon will then recreate the VM.
• When there are more than ten global dedicated entitlements available to a user, the machine host name will sometimes not be visible in global entitlements if the “Show assigned host name” option is enabled.
• Scheduling an upgrade for an RDS host may complete successfully, but the upgrade itself can fail when the scheduled time is reached.
Workaround: See KB article 6000992.
• If Horizon Events Database is hosted by an instance of Microsoft SQL Server (any version), do not disable TLS 1.2. This connection cannot be made over TLS 1.3.
• HZN-2542: When changing the browser locale and refreshing the Horizon Console UI, error alerts fail to display for the newly selected language.
Workaround: Log in to Horizon Console in a new browser tab.
• HZEC-2336: View API consumers like the MP4H Adapter invoke MachineDetailsView. This API fails intermittently with user data not found error.
Workaround: None
• HZEC-2873: Number of issues reported for ESXi Hosts in the dashboard summary may not match with number of issues reported in the dedicated ESXi Host issues section in the dashboard. If NVIDIA vGPU support detects a mismatch with the supported vGPUs for the given host, the issue count should be incremented but the count may not display in the UI.
Workaround: View the warnings in Dashboard > System Health > View > vSphere > ESX Hosts.

Horizon Agent for Windows
• HZN-8997: The Admin UI displays an incorrect GOS type for the Agent VM following the upgrade from Windows 10 to Windows 11.
Workaround: Remove the machine from the Admin UI (under Registered Machines > Others), then reinstall the unmanaged agent. After completing these steps, the Admin UI correctly displays the operating system as Windows 11.

Horizon Agent for Linux
This section describes issues that might occur with Horizon Agent for Linux or when you configure a Linux desktop.
• VCART-9593: Linux VDI sessions fail to launch when FIPS mode is enabled on RHEL 8.10. There is no workaround for this issue.
• VCART-1502: The Session Collaboration icon disappears from the system tray after resizing a Debian 12.x desktop.
Workaround: Disconnect from and reconnect to the desktop. The Session Collaboration icon usually appears after reconnection to the desktop. Alternatively, you can try restarting GNOME Shell with the following steps:
1. Press Alt+F2 to display the Run a Command dialog box.
2. Type “r” in the dialog box.
3. Press Enter.
• VCART-9623: Sometimes the Collaboration window might not appear after you connect to a remote desktop and click the Collaboration UI icon.
Workaround: Resize the desktop window or reconnect to the remote desktop.
• VCART-9624: The Linux agent’s keyboard layout and locale do not synchronize with the client if the Keyboard Input Method System is set to fcitx.
Workaround: Set the Keyboard Input Method System to iBus.
• VCART-9625: If you configure two monitors with different resolutions, and the resolution of the primary screen is lower than that of the secondary screen, you might not be able to move the mouse or drag application windows to certain areas of the screen.
Workaround: Make sure that the primary monitor’s resolution is at least as large as the secondary monitor’s.
• VCART-9626: If a client user minimizes the window of a Linux published application using the Minimize command and then selects the Maximize command, the window is restored to its previous size instead of changing to full-screen mode as expected.
Workaround: To change to full-screen mode, select the Maximize command again.
• VCART-9627: Linux published applications do not support using the window taskbar to divide the work area in a multiple-monitor display. For example, suppose a client user has two monitors arranged side by side. If the user moves the taskbar to the right side of the left monitor’s screen or the left side of the right monitor’s screen, the work area is divided into two parts. However, if the user then maximizes the application window, the window is displayed incorrectly in relation to the taskbar.
• VCART-9638: When connecting to a Linux published application from Horizon Client for Mac, the application window is displayed with square corners instead of rounded corners.
• VCART-9639: If a client user leaves a nonmodal dialog box open in a Linux published application and then makes active a native application on the client system, part of the dialog box will appear to be missing when the user returns to the published application.
• VCART-9640: If the client user minimizes a Linux published application window or brings another application in front of the published application window, the taskbar fails to display the thumbnail preview of the published application window. Hovering over the published application icon in the taskbar displays a blank thumbnail instead of the contents of the published application window.
• VCART-9641: Linux published applications do not support the Aero Snap feature on Windows client systems. Users connecting to a Linux published application from Horizon Client for Windows do not have the capability to snap or fix windows to the edges of the computer screen using the keyboard or mouse.
• VCART-9642: Linux published applications do not support the jump list feature on Windows client systems. If a user connects to a Linux published application from Horizon Client for Windows and right-clicks the taskbar icon for the application, no jump list is displayed.
• VCART-9643: Due to a limitation in the work area, Linux published application windows cannot be moved partially off the edge of the client’s screen or work area. If the user attempts to move a published application window past the edge of the screen, the window will bounce back inside the screen’s boundaries.
• VCART-9644: If the client user opens a modal dialog box from a Linux published application, that dialog box might not appear in front of native windows.
• VCART-9645: When connecting to a published application from a Windows client system, there are some differences between the context menus of the Windows taskbar and the application window’s title bar. Shift + right-clicking the application icon in the Windows taskbar displays a menu with the items: Restore, Move, Size, Minimize, Maximize, Close. Right-clicking the application window’s title bar displays a menu with the items: Minimize, Maximize, Move, Resize, Close.
• VCART-9646: Published applications do not support the Move and Size context commands for the taskbar on Windows client systems. When a user Shift + right-clicks the published application icon in the Windows taskbar, Move and Size appear in the menu but neither command has any effect if selected.
• VCART-9647: Published applications do not support the Size command from the application window’s context menu. When a user right-clicks the title bar of the application window, Size appears in the menu of commands but has no effect if selected.
• VCART-9648: When a user opens multiple session windows for the same published application on a Windows client system, the Cascade all windows command has no effect.
• VCART-9649: If a Windows client user with a dual monitor configuration maximizes a published application in the lower-resolution monitor’s work area, the Windows taskbar turns black.
• VCART-9650: After publishing a LibreOffice application as an application pool, duplicate LibreOffice icons might appear in Horizon Client.
Workaround: From the Connection Server, manually assign the icon for the LibreOffice application.
• VCART-9651: Linux published applications do not support the Multi-Session Mode option in the application pool settings in Horizon Console.
• VCART-9652: When connected to a Linux published application, if the user opens a dialog box related to user account controls (such as when editing firewall settings), the desktop will not show.
• VCART-9653: Horizon Agent for Linux does not support session stealing between published desktops and published applications. For example, if a user has opened a published desktop session and then attempts to open an application session based on the same farm, the desktop session remains active and the application session is not established. Likewise, if the user has opened an application session and then attempts to open a published desktop session based on the same farm, the application session remains active and the desktop session is not established.
• VCART-9628: If a user types an entry into the Session Collaboration invitation text box and moves the cursor away from the text box, the original entry is cleared.
• VCART-9629: If a client user with a multi-monitor system opens a published application in seamless window mode, display problems might occur when moving the application window between monitors.
Workaround: Shift + right-click the application icon in the client’s task bar and select Maximize to enlarge and refresh the window display.
• VCART-9644: Display problems might occur when a client user opens published applications in seamless window mode on a multi-monitor system where some monitors have portrait orientation and other monitors have landscape orientation. If the user maximizes the application windows in all the monitors, the task bar appears black in the landscape monitors.
• VCART-9630: When client users copy content containing images in rich text format and then paste the content into an application on a remote Linux desktop, the images might be missing from the pasted content. This issue is caused by a limitation in certain third-party applications such as OpenOffice or LibreOffice, not by Horizon Agent for Linux.
Workaround: Use a clipboard manager to retrieve the missing content from the clipboard.
• VCART-9632: The Enter Ctrl + Alt + Del control in Horizon Client does not take effect when connected to a RHEL 7.9 desktop with MATE desktop environment.
Workaround: Use the default keyboard shortcut for logging out of a MATE desktop. Or, define a custom keyboard shortcut for logging out.
• VCART-9633: A small blank recording (2-3 kb) is sometimes created when a blast session running on Linux agent is being recorded by the Horizon Recording solution.
Workaround: None. There is no adverse effect on the functionality except that a small recording can be seen in the recordings page for some of the sessions during a fresh logon.

Horizon Agent for Windows
• VCART-7428: Scheduling an upgrade for an RDS host may complete successfully, but the upgrade itself can fail when the scheduled time is reached.
Workaround: See KB article 6000992.

Horizon Client
This section describes problems that end users might encounter when using Horizon Client or Horizon Web Client to connect to remote desktops and applications. For problems that occur only in a specific Horizon Client platform, see the Horizon Client release notes in the Omnissa Product Documentation portal.
• VCART-9656: When you connect to a Linux desktop, some keyboard inputs do not work. For example, if you are using a non-English IME on both the client device and the remote desktop, some non-English keys are not displayed correctly.
Workaround: None.
• VCART-9655: When you use the Ambir Image Scan Pro 490i to perform a scan on a remote desktop or application, the dialog box always displays “Scanning…” and does not complete.
Workaround: Perform a scan on the client. The client scan calibrates the scanner. After the calibrate operation is finished, save the calibration file and deploy it in ProgramData\AmbirTechnology\ImageScanPro490i.
• VCART-4245: HDR support for full screen mode is limited to a scenario where the selected monitor is the primary monitor.
Workaround: None.

Windows OS Optimization Tool
• When the exported analysis report is exported to the same VM where you’re running the Optimization Tool EXE, the report is auto-deleted after running the tool’s Generalize task. Even though you’ll still be able to view the report inside the Optimization Tool user interface, the exported report is deleted after Sysprep runs (Sysprep runs as part Generalize).
Workaround: Export the analysis report to another location on the network instead of saving the report into the current user folders on the same VM. Because those user folders get deleted as part of Sysprep, if saved in those folders on the VM, the report is deleted during the Generalize run. If you specify to redirect the report to another location on the network, the report will be retained after running Generalize.

APIs
• HZN-3296: REST API ObjectGUIDs change after certain events, such as disaster recovery and pod rebuilding.
Workaround: Do not rely on ObjectGUIDs as persistent identifiers. After an event such as disaster recovery and pod rebuilding, resync any third-party applications to the new ObjectGUIDs.

Nutanix
• HZN-6730: Desktops are not able to refresh when the connection server is down and the replica server is up.
Workaround: None
• HZN-6964: Registered machines can be deleted when pools exist.
Workaround: None
• HZN-7169: Farms can be created using the Windows 10 GI template.
Workaround: None

Horizon 8 API
For the latest set of Horizon 8 APIs, see Omnissa Developer Portal and navigate to the current release in the drop down. Click on the Documentation tab for more details and examples on how to use the API.

Horizon Edge and Horizon Cloud Connector
Applicable to customers with Horizon Universal Subscription, Horizon Enterprise Plus Subscription, Horizon Standard Plus Subscription, Horizon Apps Universal Subscription, or Horizon Apps Standard Subscription.
The Horizon Edge is a required component for connecting Horizon 8 to Horizon Control Plane next-gen for subscription licensing enablement and additional control plane SaaS services.
The Horizon Cloud Connector virtual appliance is a required component for connecting Horizon 8 to the first-gen Horizon Control Plane for subscription licensing enablement and additional control plane services.

Horizon 8 Deployed on Public Cloud SDDCs
For a list of Horizon 8 features supported on Azure Omnissa Solution (AVS), see KB 80850.
For a list of Horizon 8 features supported on VMware Cloud on AWS, see KB 58539.
For a list of Horizon 8 features supported on Google Cloud VMware Engine (GCVE), see KB 81922.
For a list of Horizon 8 features supported on Oracle Cloud Omnissa Solution, see KB 88202.
For a list of Horizon 8 features supported on Alibaba Cloud Omnissa Service (ACVS), see KB 92140.

Before You Begin
• Important note about installing VMware Tools: If you plan to install a version of VMware Tools downloaded from the product downloads page, rather than the default version provided with vSphere, make sure that the VMware Tools version is supported. To determine which VMware Tools versions are supported, go to the Omnissa Product Interoperability Matrix. (Supported versions: 11.1.0, 11.0.6, 10.3.22, 10.3.21). There are also performance issues with the 11.x versions of VMware Tools. For more information, see KB 78434.
• When you deploy an instant clone as a RDS host, do not reboot the RDS host directly from within the Windows Server OS. Instead, refresh the instant clone VM using the push image workflow.
• To use View Storage Accelerator in a vSphere environment, a desktop virtual machine must be 512GB or smaller. View Storage Accelerator is disabled on virtual machines that are larger than 512GB. Virtual machine size is defined by the total VMDK capacity. For example, one VMDK file might be 512GB or a set of VMDK files might total 512GB. This requirement also applies to virtual machines that were created in an earlier vSphere release and upgraded to vSphere 5.5.
• For best practices on using Carbon Black with Horizon 8, see KB 95512.
• Horizon 8 supports a maximum of 500 virtual machines per ESXi host when using vSAN 8 ESA datastore. The achievable maximum depends on the workload and specifics of the hardware. For information on all Horizon configuration maximums, see VMware Configuration Maximums.

Upgrade
Check the Omnissa Product Interoperability Matrix before upgrading your Horizon deployment. Note the following guidance:
• You can only upgrade to a version with a release date later than your current deployment.
• When upgrading from a non-ESB version to an ESB version, the target ESB version must be later that your current non-ESB release. For example, you cannot upgrade from Horizon 8 2203 (non-ESB) to Horizon 8 2111.1 (ESB) even though 2111.1 was released after 2203 (or you will lose features). You can only upgrade to Horizon 8 2212 or later versions.
• Important: Please allow for extra time and preparation when you upgrade from a VMware-branded Horizon version to an Omnissa-branded Horizon version. For more details, see KB 6000681 and Upgrading to Omnissa Horizon 8 2412 and Later.

Compatibility Notes
The table below contains specific compatibility information as well as links to information located elsewhere.

Use of Open Source
As part of the installation process, an open_source_licenses.txt file is written to the file system. Key open-source components included in this release are:
• Horizon Connection Server 2512 is built on the Apache Tomcat implementation of Jakarta EE, version 10.1.49.
• Horizon Agent for Linux 2512, Horizon Agent for Windows 2512, and Horizon Connection Server 2512 all utilize the BellSoft Liberica distribution of OpenJDK, version 17.0.16.0.1 (CPU).

Documentation
Horizon 8 documentation is in the Omnissa Product Documentation portal.

Localized Content for Omnissa Docs
For details on Omnissa’s localization strategy, see Announcing Omnissa Localization Support.

Support Contact Information
To receive support and to learn more about support policies, see Omnissa Customer Connect.
For information on filing a support request in Customer Connect and via Cloud Services Portal, see KB 6000005.
Original source
May 2026
- No date parsed from source.
- First seen by Releasebot:
  May 12, 2026
ControlUp

Synthetic Monitoring

ControlUp adds Synthetic Monitoring for tracking app performance and availability.

Synthetic Monitoring
Original source

Digital Employee Experience Release Notes

Products (12)

Latest Digital Employee Experience Updates

Custom Hive 1248 (May 28)

Important

Omnissa Identity Service | MAY 2026

Omnissa Identity Service | MAY 2026

Urgent Notification regarding legacy Domain End of Service

What’s New in May 2026

Omnissa and Google Workspace Integration for New Environments

What’s New in March 2026

Migration to SCIM 2.0 for Workspace ONE UEM customers with Omnissa Access configured (Limited Availability)

What’s New in January 2026

Okta and generic SCIM Identity Provider migration to Omnissa Identity Service (Limited Availability)

Ability to select common identifier during migration to Omnissa Identity Service

What’s New in December 2025

Support for Workspace ONE UEM Basic users in new environments

Extension of Platform SSO support in Workspace ONE environments with user sync through Identity Service (SCIM 2.0)

Support for Horizon 8 SSO to Azure VMs joined to Entra ID

What’s new in November 2025

URL Migration Dashboard

What’s New in September 2025

Omnissa Identity Service opens in new tab

Horizon 8 App Support

What’s New in July 2025

Active Directory Migration to Microsoft Entra ID (Limited Availability)

User Notification Settings for Users Provisioned to Workspace ONE UEM

What’s New in January 2025

Integration with Horizon Cloud Service Next-Gen

Move to Omnissa Connect

What’s New in December 2024

New provisioning app for Okta integration

New Status tab for provisioning errors

What’s New in September 2024

Password Grant Flows

What’s New in April 2024

SAML Authentication Context for Generic Identity Provider Integrations

What’s New in February 2024

Ability to deactivate Omnissa Identity Service from the console

What’s New in December 2023

Omnissa Identity Service public APIs

Token expiry notification for administrators

What’s New in October 2023

New Flow for Okta Integration with Workspace ONE Cloud

What’s New in June 2023

Audit events for provisioning to downstream products and services

What’s New in April 2023

New provisioning app for Microsoft Entra ID integration

Introducing Omnissa Identity Service - January 2023

Known Issues

Documentation

Internationalization

Localized Content for Omnissa Docs

Support Contact Information

DEX Pack Release Notes May 2026

Experience Management 26.02 for macOS

Urgent Notification regarding legacy Domain End of Service

Experience Management 26.02 for macOS

New Features

Minimum Requirements

Resolved Issues

Known Issues

Download Instructions

Omnissa Access 24.12.1.0

Omnissa Access 24.12.1.0 | 11 SEP 2025 | Build 49efda362374f8d76a5a23fecc282b330acfe913

Omnissa Access Connector (Windows) 24.12.1.0 | 02 SEP 2025 | Access-Connector-Installer-24.12.1.0.exe

Omnissa Access Desktop 24.12.1.0 | 11 SEP 2025 | Omnissa-Access-Desktop-24.12.1.exe

Urgent Notification regarding legacy Domain End of Service

Omnissa Access 24.12.1.0

What’s New

Compatibility

Installation

Upgrade

Upgrading to Omnissa Access Virtual Appliance 24.12.1.0 (Photon Linux)

Upgrading to Omnissa Access Connector 24.12.1.0 (Windows)

Legacy Connectors

Resolved Issues

Known Issues

Documentation

Localized Content