Omnissa Release Notes

The Omnissa Connect Release Notes outline 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. With Omnissa Connect, you can access your Omnissa solutions portfolio from a centralized location.

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 Connect 26.05.12

New Features

• In this release, we’ve made a few updates containing general quality and performance improvements with no new features.

Resolved Issues

• CXP-8182: Fixed an issue where the system was not enforcing an organization level IP Authentication Policy during login.

Known Issues

• We haven’t identified any notable known issues in this release. If you’re facing problems, reach out to the Omnissa Global Customer Support (GCS) Team.

Original source

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 Workspace ONE Content for Android Release Notes detail 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 version.

Workspace ONE Content 26.04 - March 2026

New Features

• Provision for users to view For You sections as per the order configured in Workspace ONE UEM.
• Seamless admin and user repository authentication experience when repository and enrollment credentials are the same.

Note

For information about new features and improvements on Workspace ONE UEM, see Workspace ONE UEM Documentation at Omnissa Docs.

Minimum Requirements

• Android 9+
• Workspace ONE UEM Console 2410+. For more information, see the Knowledge Base article Workspace ONE (WS1) UEM Console Release and End of General Support Matrix (2960922).

Resolved Issues

Note

The numbers included before the resolved issues are used for internal issue tracking.

• AST-18946: Print option not available in Android Content app for pdf file uploaded in UEM Console.

Known Issues

We have not identified any notable known issues in this release. If you are facing any problems, feel free to reach out to our support team.

Original source

We’re excited to share the new release of Workspace ONE UEM version 2506! Read on to learn about the new features and improvements in this 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 for more information.

What’s New in this Release

Android Management

Experience seamless single sign-in and sign-out with Microsoft Entra for shared Android devices

You now have the advantage of a smooth single sign-in and sign-out process for applications that support the Microsoft Authentication Library (MSAL) on shared Android devices using the Workspace ONE Launcher. This feature supports first-party Microsoft applications such as Teams and any third-party applications that integrate MSAL and support Microsoft’s Shared Device Mode.

To use this feature, organizations must configure devices to use Check-in/Check-out (CICO) with Workspace ONE Launcher. Users authenticate with Microsoft Entra to check out the shared device. Users only need to launch supported MSAL-enabled apps to start using them. When users log out of Workspace ONE Launcher, they are automatically signed out of these applications. Additionally, this feature provides an alternative to the Workspace ONE Mobile SSO for organizations that cannot federate Microsoft Entra with Workspace ONE Access or cannot use Workspace ONE Tunnel as their VPN client.

Remotely deliver certificates to your device using SCEP payload

A new SCEP payload is now available in Android Custom DPC profiles. Push this profile to enable the remote delivery of certificates to your device from your certificate authority using the SCEP protocol. The Intelligent Hub obtains an SCEP challenge from Workspace ONE UEM, securely generates a private key on the device, and acquires the certificate from your certificate authority. The Hub then adds the certificate to the Android Keystore, where other applications on the device can access it. Silently granting applications access to these certificates is supported. Workspace ONE UEM currently does not support the use of the SCEP payload for configuring Wi-Fi with certificate-based authentication.

Configure Access Point Names (APNs) for work managed Android devices

A new Access Point Name (APN) payload is now available in Android Custom DPC profiles. Push this profile to remotely add APNs for mobile networks to Android devices. Additionally, you have the option to mandate that your Work Managed devices utilize only managed APN settings. This allows organizations to easily deploy private APNs to better secure access to corporate resources over mobile networks. This is supported on Android 9.0 and higher that are enrolled in Work Managed mode.

Android Management Mode Filter for Smart Groups

You can now create Smart Groups that capture Android devices with a specific Android Management Type (Custom DPC vs AMAPI) and Android Management Mode (Work Profile, Work Managed, or COPE).

Note: This feature is available on demand in Workspace ONE UEM 2506. Please contact your Omnissa representative or submit a support request to enable this functionality. This feature will be generally available in Workspace ONE UEM 2509.

Certificate Management

Integrate OID-SID and SAN into certificate templates

To meet the updated certificate requirements, we have enhanced certificate templates within Workspace ONE UEM to include OID-SID Extension and support for SID values in the SAN field.

• When assigning a certificate to a user in Active Directory (AD), it is essential to format the certificate entry using one of the strong formats.
• Ensure that the Security Identifier (SID) is selected in the Active Directory Certificate Services (ADCS) certificate template. The Certificate Signing Request (CSR) must contain the OID-SID key-value pair and this extension is present in the generated certificates.
• Alternatively, the same value can be submitted in the SAN field and is the primary implementation for SCEP-based certificates.

For more information, see Certificate-based authentication changes on Windows domain controllers.

Integrate DigiCert ONE with Workspace ONE UEM for enhanced security

Workspace ONE administrators can now set DigiCert ONE as a trusted certificate authority within UEM. Following this, they can create a certificate template and utilize the profile’s credential payload to issue and deploy certificates. This integration significantly enhances stability, security, and authentication, facilitating the effective use of certificates across various domains, including Public Key Infrastructure (PKI) and S/MIME.

Freestyle Orchestrator

Streamline onboarding entitlements in workflows

Onboarding entitlements within workflows allow administrators to prioritize resources essential for onboarding, which take precedence over other resource assignments. This is available only for Windows. For more information, see Onboarding Workflows.

Enhance device onboarding through offline domain join within workflows

You can now incorporate the domain joining process into workflow systems, enhancing the onboarding process for devices and allowing devices to join a domain before other resources are deployed. This is available only for Windows. For more information, see Offline Domain Join in Workflows.

In-line Sensor evaluation: A better way to use Sensors within workflows

Sensors are now assessed at their step within the workflow rather than at the beginning of workflow execution. This approach enables administrators to monitor sensor values within the workflow as needed instead of re-using the value stored from evaluations done prior to the start of execution.

Enhanced reporting for application deployments within Freestyle Orchestrator

Gain better visibility into application deployment outcomes with improved reporting capabilities for Windows devices. When app deployments are triggered from Freestyle workflows, you’ll now receive detailed status updates, clear failure reasons, and timestamp enrichments.

Workflow Engine Enhancements

The workflow engine has undergone a significant backend enhancement with an upgrade to .NET 8.

iOS Management

Enhance device security with Managed Device Attestation

Managed Device Attestation is available for devices running iOS 16, iPadOS 16.1 or later with Apple Silicon or A11 Bionic chip or newer. This feature offers robust verification of the device’s properties, which are essential for trust evaluation. This cryptographic declaration of device properties is based on the security of the Secure Enclave and the Apple’s attestation servers. By leveraging attributes such as Serial Number, UDID, and OS version, Managed Device Attestation enhances trust evaluations for devices enrolled through Automated Device Enrollment or profile-based device enrollment. For more information, see Managed Device Attestation.

This feature is Generally Available from 2506 Patch 1.

After device wipe, return to service easily with automated reprovisioning process

With this exciting new feature, organizations can easily wipe all user data from a managed iOS device and get the device back into service without needing administrators to physically handle it. Workspace ONE UEM supports Return to Service functionality for iOS 17 devices, allowing MDM to add an enrollment and Wi-Fi profile to the device wipe command. This automated process eliminates the need for manual Wi-Fi configuration by administrators post-Device Wipe. For more information, see Return to Service.

Easily release a device from Apple Business Manager and Workspace ONE UEM

You can release corporate iPhones and MacBooks from Apple Business Manager or Apple School Manager if they’ve been sold, lost, are beyond repair, or when an employee moves on from your organization. With Workspace ONE UEM, you can now release devices using the Enterprise Wipe, Device Wipe, and Delete Device actions. By default, this capability is only available to administrators with the System Administrator role, with plans to extend access to Console Administrator and AirWatch Administrator roles in the near future. For more information, see Release a Device.

Enhance Apple Books delivery with Modern SaaS Architecture

The delivery of Apple Books (internal and public, not VPP books) now leverages our Modern SaaS Architecture to significantly improve delivery performance. Read more about our new architecture here.

Apple GitHub integration for DDM configurations is now available

Declarative Configurations was in limited rollout in 2410 release and is now Generally Available from 2506 Patch 3. Declarative Configurations now integrate directly with Apple’s GitHub-hosted MDM developer documentation. This integration streamlines how we implement and update DDM configurations, enabling significantly faster development cycles and improved alignment with Apple’s latest specifications. To explore Declarative Configurations in Apple’s GitHub MDM documentation, visit the GitHub Device Management repository.

The following new DDM configurations have been added with 2506 patch 3:

• Software Update: Settings
• Math Settings

Launcher

Custom XML Settings Integrated into the Console

Some settings introduced to Workspace ONE Launcher can only be configured through XML pushed through the Custom Settings profile. We have configured these settings as native features or settings in the Launcher profile payload.

The following features have been integrated into the Launcher profile:

• Speed Lock
• Dynamic App Availability
• Show Logout Button from Guest Mode
• Require Tunnel before Launcher

For more information, see Workspace ONE Launcher product documentation.

Linux Management

Easily implement firewall rules on Linux devices

In addition to the recent profile releases, including Date/Time, Proxies, Passcode, and Restrictions, we are excited to introduce support for a Linux Firewall Profile. This new profile allows users to configure firewall rules that will be enforced on the device once assigned and deployed. For more information on profiles, see Linux Profiles.

Enhancements to Workspace ONE Sensors

To provide greater flexibility and choice, administrators now have the option to write Workspace ONE Sensors using Python 3, in addition to the existing option of using Bash. For more information, see Sensors for Linux Based Devices.

macOS Management

Enhance device security with Managed Device Attestation

Managed Device Attestation is available for devices running macOS 14 or later with Apple Silicon or A11 Bionic chip or newer. This feature offers robust verification of the device’s properties, which are essential for trust evaluation. This cryptographic declaration of device properties is based on the security of the Secure Enclave and Apple’s attestation servers. By leveraging attributes such as Serial Number, UDID, and OS version, Managed Device Attestation enhances trust evaluations for devices enrolled through Automated Device Enrollment or profile-based device enrollment. For more information, see Managed Device Attestation.

This feature is Generally Available from 2506 Patch 1.

Easily release a device from Apple Business Manager and Workspace ONE UEM

You can release corporate iPhones and MacBooks from Apple Business Manager or Apple School Manager if they’ve been sold, lost, are beyond repair, or when an employee moves on from your organization. With Workspace ONE UEM, you can now release devices using the Enterprise Wipe, Device Wipe, and Delete Device actions. By default, this capability is only available to administrators with the System Administrator role, with plans to extend access to Console Administrator and AirWatch Administrator roles in the near future. For more information, see Release a Device.

Apple GitHub integration for DDM configurations is now available

Declarative Configurations was in limited rollout in 2410 release and is now Generally Available from 2506 Patch 3. Declarative Configurations now integrate directly with Apple’s GitHub-hosted MDM developer documentation. This integration streamlines how we implement and update DDM configurations, enabling significantly faster development cycles and improved alignment with Apple’s latest specifications. To explore Declarative Configurations in Apple’s GitHub MDM documentation, visit the GitHub Device Management repository.

The following new DDM configurations have been added with 2506 patch 3:

• Account: CalDav
• Account: CardDav
• Account: LDAP
• Account: Mail
• Account: Subscribed Calendar
• Math Settings
• Screensharing: Connection
• Screensharing: Host Settings
• Disk Management: Settings
• Software Update: Settings

Resource Management

Pending Actions visible for troubleshooting

When troubleshooting device issues, you now have the advantage of accessing Pending Actions. This feature provides a comprehensive list of planned resource installation and uninstallation commands for Apps, Profiles and Workflows on a device the next time it checks in. To view a device’s Pending Actions, go to Device Details, navigate to More > Troubleshooting, and then select the newly added Pending Actions tab.

Installation metrics now retained upon Resource and Smart group updates

When assignment or payload updates are made to apps and profiles, or when their assigned Smart groups are modified and republished, installation metrics achieved so far will now be retained and remain visible on the Deployment Tracking page as Currently assigned. It denotes all devices having a confirmed assignment to an app or profile at any given time. This enhancement is currently being rolled out on a Limited Availability basis starting with Patch 16. If you are interested in an early access, get in touch with your account team.

Faster resource delivery for larger device populations

Faster resource delivery is now supported for a larger device population when apps and profiles are published. This type of delivery is initiated whenever new apps or profiles are published, assignments for existing ones are updated, profile payloads are modified, or Smart Group rules change if the number of devices impacted by such updates is below a defined threshold. Devices impacted by these updates will check in immediately and install or remove the necessary resources instead of waiting for the standard check-in cycle. This enhancement is being rolled out on Limited Availability starting 2506 Patch 12. Contact your Account Team if you would like to participate in the Limited Rollout or have any questions regarding this enhancement.

Rugged Device Management

Relay Server Management enhanced with V2 APIs

As part of our continuous efforts to streamline and expand product provisioning, we are launching Relay Server V2 APIs. These are UUID-based endpoints supporting basic CRUD operations, advanced search(by name, type, status etc.), and a test connection API to verify relay server connectivity. The V2 APIs enable secure, fully automated, end-to-end management of relay servers. For more information, refer to the ‘RelayServersV2’ section of API help page.

tvOS Management

After device wipe, return to service easily with automated reprovisioning process

Workspace ONE UEM supports Return to Service functionality for tvOS 18 devices, allowing MDM to add an enrollment and Wi-Fi profile to the device wipe command. This automated process eliminates the need for manual Wi-Fi configuration by administrators post-Device Wipe. For more information, see Return to Service.

User Management

Streamline user group management using the latest REST APIs

A new set of REST APIs is now available to simplify group management. These APIs provide functionalities including creating user groups, updating their properties, and performing actions such as synchronization and merging, and deleting unwanted groups.

Directory Services migration to Omnissa Identity Service

With this Limited Availability feature, you can now integrate with the Omnissa Identity Service to migrate Directory Services from on-premises Active Directory (LDAP) to Entra ID (SCIM 2.0). The Omnissa Identity Service provides a seamless transition to Entra ID for user provisioning and authentication through a guided migration wizard. This is designed for users who are synced to UEM through LDAP-based integration with Active Directory.

visionOS Management

Overview of recently added profiles for visionOS

The following visionOS profiles have been introduced to the Workspace ONE Console UI. For more information, see visionOS Profiles.

• AirPrint
• CardDAV
• Certificate Transparency
• DNS Proxy
• Domains
• Email
• Global HTTP Proxy
• Passcode
• Subscribed Calendars
• VPN

Windows Management

Launch native and App Volumes MSI apps directly from Intelligent Hub for Windows

With this enhanced app catalog functionality, you can now launch native applications and App Volumes MSI apps directly from the Intelligent Hub app catalog in addition to the existing ability to launch Web and Horizon apps.

The key new features are as follows:

• App Launch Support: Native apps and App Volumes MSI apps can now be launched from within the Hub catalog.
• Admin Control: IT administrators can define custom launch commands for all applications in the app configuration within Workspace ONE UEM.
• Improved User Experience: You no longer need to manually locate and open native apps post-installation; you can now launch them directly from the Hub interface.

Previously, users could install native applications through the Intelligent Hub, but launching them directly was not possible. Now, with launch commands configured in UEM, the Hub executes the command defined by the user, providing a seamless experience to both install and launch apps from a single interface. This enhancement simplifies app access and enhances productivity by reducing the number of steps required to open frequently used apps. For more information, see Installing Native Apps.

Default User Mode configuration during Windows device enrollment

Workspace ONE UEM now supports configuring the default user mode (Single User Mode or Multi User Mode) at the Organization Group (OG) level. This setting is automatically applied to Windows devices during enrollment through the Intelligent Hub client.

• Configuration in UEM console (Requires UEM version 2506 or later): Administrators can define the default user mode in the UEM console under the OG settings. The available options include:
  • Single User Mode
  • Multi User Mode
• Hub behavior during enrollment (Requires Hub version 24.10.10+ or 25.06.x):
  • During the enrollment process, the Windows Intelligent Hub queries the UEM console for the default user mode setting.
  • The retrieved mode is validated and stored locally by the Hub.
  • Based on the setting, the Hub configures the Windows device accordingly.

Manage Intelligent Hub application versions on Windows devices

The Technical Preview feature, Intelligent Hub Application Version Control allows administrators to manage precise control over version of the Intelligent Hub is installed on Windows devices, supporting both Win32 and ARM platforms. You can now deploy Intelligent Hub updates independently of Workspace ONE UEM console upgrades and gain direct access to Beta builds without manual download or upload steps. Unified version control is available for both Intel/AMD (Win32) and ARM-based Windows devices.

Once enabled, the setting Intelligent Hub Automatic Updates will be renamed to Use Intelligent Hub Version Control, and a new section for Intelligent Hub Target Seeding will allow version assignment at the Organizational Group level. The key capabilities include:

• You can now assign specific versions to production OG to ensure consistency, while using the latest GA or Beta version in a test OG for validation.
• Instant application of changes to newly enrolled devices (including OOBE and Autopilot) with existing devices auto-updating within 48 hours.
• Downgrades are not supported for devices already running newer versions.

If Intelligent Hub Automatic Updates were previously enabled, the new setting defaults to Latest available. In contrast, if automatic updates were deactivated, the new version control setting will also remain in a disabled state.

Note: This feature requires Workspace ONE UEM version 2506 or later.

Faster SFD delivery and installation through the Intelligent Hub

Workspace ONE now supports a faster and more efficient installation of the Software Distribution Framework (SFD) by shifting the process from the traditional OMA-DM channel to a Hub-based installation. With this enhancement, SFD is bundled with Hub and is installed immediately after enrollment, enabling earlier application deployment and improving overall device readiness. We’ve made the following improvements:

• SFD is now installed through the Intelligent Hub, independent of the OMA-DM workflow.
• Installation occurs immediately after enrollment as the SFD package is part of the Intelligent Hub, reducing delays in the provisioning process.
• Applications can start installing sooner, accelerating time-to-productivity.
• Devices reach a usable state faster, enhancing the end-user experience.

Note: This feature requires Workspace ONE UEM version 2506 or later and Hub version 25.06.x.

Enhanced Offline Domain Join (ODJ) configuration

The Offline Domain Join (ODJ) configuration process has been significantly enhanced to improve reliability and flexibility, particularly in Autopilot Hybrid Join scenarios. Configuring Offline Domain Join is no longer tied to the device enrollment process. It can now be applied at any time, significantly reducing the risk of failures caused by race conditions or timeouts during Autopilot enrollments. With this update, ODJ can also be configured as a step within the Freestyle workflows, especially the new Onboarding workflows introduced recently, enabling IT teams to properly sequence and stage devices before they reach end users. This ensures a smoother onboarding experience and more consistent device readiness. For more information, see Offline Domain Join in Workflows.

Administrators can now deploy ODJ even after a device has been moved to a different Organizational Group (OG), including child OGs. Additionally, to maintain naming consistency, a device’s computer name will only change if it is not already joined to a domain.

Note: This feature requires Workspace ONE UEM version 2506 or later and Hub version 25.06.x.

Improvements in logging and troubleshooting

This release introduces several powerful enhancements to improve visibility, streamline troubleshooting, and reduce time-to-resolution for both end users and administrators.

• Log submission from Intelligent Hub: Users can now send logs directly to Workspace ONE UEM from the Hub Support tab, with two new options added alongside the existing Collect Logs feature:
  • Send Hub Logs to UEM: Automatically uploads all Intelligent Hub-related logs to the UEM console. Logs are accessible under Device Details > Attachments > Documents.
  • Send Other Logs to UEM: Sends logs from DEEM, Workspace ONE Assist, and Workspace ONE Tunnel to the same location in the UEM console. Users receive a confirmation once the log upload is complete, improving transparency and support efficiency.
• Application deployment event logging: To enhance visibility into application deployment, Intelligent Hub now sends detailed application deployment event summaries to the UEM console under Device Details > Troubleshooting > Event Logs. These event logs include data on detection statuses, Pre-condition checks, Exit codes and more helping administrators quickly identify the causes of application installation and uninstallation failures.
• Filter logs by duration and component: Administrators can now filter collected logs based on timeframe and log source, making it easier to isolate relevant data during troubleshooting.
  • Timeframe Filters: All logs, or logs from the last 1, 3, 7, or 14 days.
  • Component Filters: Hub (Logs from Intelligent Hub, App Deployment Agent, Provisioning Agent, Factory Provisioning, and MDM), System (Windows and PCRefresh logs), Other (Logs from Assist, DEEM Telemetry Agent, and Workspace ONE Tunnel).

Note: This feature requires Workspace ONE UEM version 2506 or later and Hub version 25.06.x.

Enhanced processor architecture selection for app deployment

This new feature provides administrators with granular control over app distribution based on processor architecture. Previously, administrators could only select one option among 32-bit, 64-bit, and ARM64 as the ‘Supported Processor Architecture’ during app deployment. UEM will then determine the distribution to device architectures in the backend, limiting flexibility. Key capabilities include:

• Multi-Selection Option: Administrators can now select multiple processor architectures during app deployment. The available options include 32-bit, 64-bit, ARM32, and ARM64.
• Granular Control: This enhancement allows for more precise control over app distribution. For example,
  • Distribute a 32-bit app ‘X’ to devices with 32-bit and 64-bit architectures only, excluding ARM64.
  • Distribute a 64-bit app ‘Y’ to devices with 64-bit and ARM64 architectures, utilizing x64 emulation for compatibility.

Note: This feature requires Workspace ONE UEM version 2506 or later and Hub version 25.06.x.

Support for Administrative Template (ADMX) with profiles

With this Technical Preview feature, Workspace ONE UEM now supports Administrative Template (ADMX), providing a unified and scalable way to manage Windows policies across the device fleet. With this feature, you can manage all administrative templates for Windows 10, Windows 11, and Windows Server directly from the UEM console. You are provided with Pre-Uploaded ADMX templates for common applications, including those for Microsoft Office, Omnissa Horizon, Google Chrome, Mozilla Firefox, and more.

Note: Reapplying baselines will reset policies applied though the ADMX profiles. The capability for Baselines and ADMX profiles to coexist seamlessly will be introduced when this feature becomes Generally Available. If you currently have baselines configured, refrain from using this feature.

Windows Native Enrollment: Auto-Move Devices to Specified OG via Allowlist

Administrators can now assign a target Organisation Group (OG) while creating allowlist records for Windows devices. Upon enrollment, devices automatically move to the specified OG, streamlining device management without requiring prior user association. This feature is in Limited Availability for Windows Native enrollment (Out of Box Enrollment / OOBE and Autopilot). To enable this feature, reach out to your account team.

Original source

We are excited to share the first release of Workspace ONE Content Gateway Container version 2601! Read on to learn about learn about the new option to deploy Content Gateway independently.

What’s New

Starting with 2601, Content Gateway can be deployed as a containerized, independent service using Omnissa dux. Administrators can deploy and manage Content Gateway separately from Unified Access Gateway, enabling flexible and scalable architecture options for their environments.

Note

This release only introduces an additional deployment option for Content Gateway using containerized deployment with dux. The Content Gateway package remains functionally identical to the Content Gateway bundled with Unified Access Gateway 25.12.

Minimum Requirements

• Workspace ONE UEM Console 2410 or later
• Omnissa dux 3.1

Download Instructions

You can download the Content Gateway Container software from Customer Connect.

Product Documentation

Omnissa dux

Content Gateway Guide

Support Contact Information

To receive support, either submit a ticket through the Customer Connect portal or call your local support line. See Omnissa Support Phone Numbers (6000004) and Omnissa Customer Connect FAQs.

Original source

Omnissa App Volumes 2512 | December 16 2025 | Build 4.20.0.109

Omnissa App Volumes 2512.4 | March 11 2026 | Build 4.20.4.128

Check for additions and updates to these release notes.

Omnissa App Volumes is a real-time application delivery system that enterprises can use to dynamically deliver and manage applications.

Omnissa App Volumes Release Notes lists New Features, resolved Issues and Known Issues for this 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 KB article

What’s New

• General Availability: App Volumes Manager for Windows Endpoints

App Volumes Manager now provides full Application Lifecycle Management (ALM) for physical Windows endpoints, unifying packaging, delivery, rollback, markers, and version governance across both physical and virtual environments.

General Availability for Windows endpoints includes the following:

• VHD + MSI in App Volumes Manager, enabling consistent capture, replication across file shares and compressed delivery across endpoints.

• Local copy mode in the App Volumes Agent, ensuring reliable application delivery to physical devices while maintaining the App Volumes packaging and lifecycle model.

This release significantly expands the Apps Everywhere strategy, giving organizations a single platform to manage their entire Windows application portfolio.

Note:

• Advanced lifecycle capabilities for physical endpoints require the Omnissa Apps Essentials license.

• The VHD+MSI capability (and the related functionality such as Local Copy mode) requires App Volumes Manager to be configured with VHD In-Guest as machine manager. If your existing App Volumes Manager instance is configured with vCenter Server, you cannot perform an in-place upgrade and change the machine manager configuration to VHD In-guest.

  Instead, you must install a new App Volumes Manager instance and configure the machine manager as VHD In-Guest.

• App Volumes Agent Message for Background Package Delivery

When newly assigned application packages begin downloading, the App Volumes agent now displays a lightweight notification indicating that applications are being prepared in the background. This notification improves clarity during app delivery, reduces user confusion, and helps prevent unnecessary help-desk tickets while allowing users to continue working uninterrupted.

• Windows Update Detection Before Application Capture

App Volumes now checks whether Windows Update is enabled before application capture begins. If active, the administrator is alerted, preventing Windows Update artifacts from being included in the package. This results in cleaner, more predictable packages by avoiding OS-layer file contamination, metadata bloat, and version drift across Windows builds.

• Published Apps on Demand for Nutanix

App Volumes now supports Apps on Demand for Horizon deployments running on Nutanix. Applications can be assigned dynamically and launched instantly without pre-provisioning, improving resource efficiency and enhancing the published application experience in Nutanix environments.

• Configurable App Volumes Manager Log Levels

Administrators can now adjust App Volumes Manager logging levels without restarting services. This streamlines troubleshooting, reduces operational overhead, and maintains continuous service availability.

Resolved Issues for App Volumes 2512

The number included after each resolved issue is used by the internal issue tracking system:

• [AVM-45428] Applications with missing App Links do not get synchronized to the target App Volumes instance even after the Sync Integrations background job runs multiple times. The application status for these applications is either Syncing App Links or Syncing Properties.

• [AVM-45130] Applications with VHD+MSI packages are not delivered to Windows endpoints which are configured in the Shared Storage package access mode.

  However, these applications are delivered correctly to Windows endpoints which are configured in the Local Copy package access mode.

• [AVA-27205] Multiple shortcuts of an application having the same name are not displayed in the Start menu when the application is delivered as on-demand.

• [AVA-27166] When icon index is more than the number of RT_GROUP_ICON resources, App Volumes agent fails to extract the application shortcut icon. As a result, the application when delivered on demand has blank shortcuts.

  Note: When the application is launched for the first time, the application shortcut icon is correctly displayed.

• [AVA-27071] End user experiences a delay when logging in or logging out of a Windows endpoint which has no network connection. The action eventually succeeds but there is a delay of approximately 5 minutes and the following message is displayed: Please wait for the svservice.

  This issue occurs when the Windows endpoint is configured either in the Local Copy package access mode or the Standalone mode. For more information about these modes, see the Choose Your App Volumes Deployment Model and Application Delivery Modes with App Volumes Manager sections in the App Volumes Install Guide at Omnissa Product Documentation.

• [AVA-26981] App Volumes applications using a local database and having intensive file open or file close operations might fail to run.

• [AVA-26750] The following error You cannot call a method on a null-valued expression is observed multiple times in the command prompt when the support.bat loglevels command is used. This issue occurs when only the App Volumes agent is installed in a virtual machine and not the Horizon agent.

• [AVA-25639] A file access or access denied error occurs when running a database-related application.

Resolved Issues for App Volumes 2512.4

• [AVM-46052] “A ConnectionTimeoutError: Could not obtain a connection from the pool within… all pooled connections were in use” might occur due to a database connection leak when a large number of ESXi hosts are used for direct mounting of App Volumes packages.

  Direct mounting occurs when a vCenter Server is configured as the machine manager with the Mount ESXi option enabled, or when an ESXi (Single Host) is configured as the machine manager. This issue is more likely when the number of ESXi hosts are high.

• [AVM-45808] An end user cannot log into any virtual machine if their VHD Writable Volume stays attached after a virtual machine crashes.

  In VHD In-guest mode if a Writable Volume is attached and the VM crashes, the following might happen: If a Writable Volume is in use during the failure, the file share might not release the file handle from the crashed virtual machine. As a result, the user is prevented from using the Writable Volume on other virtual machines. If the Exception Resolution setting of the Writable Volume is configured as Block user login, the user cannot login into other virtual machines.

  When the Writable Volume is requested for a user and the unused file handle is released, the Writable Volume attachment is updated in App Volumes. The user can then use the Writable Volume in any virtual machine they log into. Administrators can configure the file share to modify the behavior of unused file handles.

• [AVM-45692] The Browse button for selecting a custom location fails to work when installing App Volumes Manager in the custom location (other than the default location). As a result, App Volumes Manager cannot be installed in the custom location.

• [AVM-45652] The launch of an on demand published application, which is delivered by App Volumes, fails in Horizon 2512 with the following error message The application could not be launched, possibly because it is missing or misconfigured. Contact your administrator for more information. This issue is seen with App Volumes 2512 and earlier.

• [AVA-27442] In some environments like Hyper-V, application capture fails with the following error: virtual disk delete failed: The process cannot access the file because it is being used by another process.

Known Issues

The number included after each known issue is used by the internal issue tracking system:

• [AVM-46052] A ConnectionTimeoutError: Could not obtain a connection from the pool within… all pooled connections were in use might occur due to a database connection leak when a large number of ESXi hosts are used for direct mounting of App Volumes packages.

  Direct mounting occurs when a vCenter Server is configured as the machine manager with the Mount ESXi option enabled, or when an ESXi (Single Host) is configured as the machine manager. This issue is more likely when the number of ESXi hosts are high.

  Workaround: Configure vCenter Server as the machine manager inApp Volumes Manager and ensure that the Mount ESXi option is not enabled.

  Resolved: This issue is now fixed in App Volumes 2512.4.

• [AVM-45808] An end user cannot log into any virtual machine if their VHD Writable Volume stays attached after a virtual machine crashes.

  In VHD In-guest mode if a Writable Volume is attached and the VM crashes, the following might happen:

  If a Writable Volume is in use during the failure, the file share might not release the file handle from the crashed virtual machine. As a result, the user is prevented from using the Writable Volume on other virtual machines. If the Exception Resolution setting of the Writable Volume is configured as Block user login, the user cannot login into other virtual machines.

  Workaround: The user must log into the same VM to access the Writable Volume. When the user logs out of the virtual machine, the Writable Volume can be used on another virtual machine.

  Resolved: This issue is now fixed in App Volumes 2512.4.

• [AVM-45692] The Browse button for selecting a custom location fails to work when installing App Volumes Manager in the custom location (other than the default location). As a result, App Volumes Manager cannot be installed in the custom location.

  Resolved: This issue is now fixed in App Volumes 2512.4.

• [AVM-45652] The launch of an published application on demand, delivered by App Volumes, fails in Horizon 2512 with the following error message The application could not be launched, possibly because it is. This issue is seen with App Volumes 2512 and earlier.

  Resolved: This issue is now fixed in App Volumes 2512.4.

• [AVM-36787] The following error is logged in App Volumes Manager when session hosts in a host pool are shut down: Session: Request is missing session cookie. In the Azure Virtual Desktop environment, a session cookie is provided only when an end user logs into a computer. If a computer starts and shuts down without any end user logging in, then a session cookie is never set. This results in a 401 (unauthorized) error. This error does not affect the end user.

• [AVA-27442] In some environments like Hyper-V, application capture fails with the following error: virtual disk delete failed: The process cannot access the file because it is being used by another process.

  Resolved: This issue is now fixed in App Volumes 2512.4.

• [AVA-26831] If a packaged application launches many processes quickly, one after another, svservice.log might contain a large number of nearly identical lines related to User Sentiment.

  Workaround: None. Ignore these lines in the log file.

• [AVA-24547] .tmp files are seen in the install directory when an upgrade rolls back in a persistent machine with active entitlements. These files do not affect any App Volumes operations. By default, these files are automatically deleted after the machine restarts.

  Workaround: If they are not deleted due to any issue, then you can navigate to the install directory and manually delete the files.

• [AVA-24493] If the CURRENT marker of the application is modified after the user launches the application in a session, RemoteApp launch silently fails in Azure Virtual Desktop.

  Workaround: To use the RemoteApp, the end user must log out of the Remote Desktop client app and log back in again.

• [AVA-26351] An OS junction point from a native folder that belongs to a banned list to a non-virtualized folder (such as %APPDATA% in configurations that do no use UIA+Profile Writable Volume or a Profile-only Writable Volume) does not work properly. Files written to the junction source do not appear in the junction target.

• [AVA-26353] In a multi-session environment, the error associated with the Microsoft Office application is also visible to users who are not assigned this application package. While the application does not behave as expected for the users assigned to this package, the error has no effect on users who are not assigned to the package.

• [2791414] When a Writable Volume and FSLogix Office Container are deployed together in a VDI, the FSLogix Office Container VHD is not created on an SMB file share. This issue occurs only when the Cloud Cache feature is enabled.

  Workaround: Deactivate the Cloud Cache feature of FSLogix Office Container.

• [2624048] Sometimes, the applications that are packaged using App Volumes versions older than 2.18.2 have many redundant firewall rules. These rules can impact the end-user login time on agent computers where the application package is deployed. This issue is fixed in App Volumes 2.18.2 and later.

  Workaround: If you are migrating an application package created in an App Volumes version earlier than 2.18.2 with such an issue, repackage the application after migrating to the target version.

• [2845852] When a remote printer is defined on a UIA+Profile Writable Volume and the printer is attached to its print server through a USB interface, the printer definition on the Writable Volume might get deleted on the next non-persistent logon.

  Workaround: On the system volume, add the following two scripts to %SVAgent%\Config\Custom\uia_plus_profile :

  OnPreLoadApp.bat: sc config spooler start= disabled net stop spooler

  OnPostEnableApp.bat: sc config spooler start= auto net start spooler

  If you already have the same script names on the Writable Volume, add the spooler commands to the scripts.

  When a script is present on a Writable Volume and in the system volume at %SVAgent%\Config\Custom\uia_plus_profile , App Volumes agent runs the script present on the Writable Volume and ignores the script on the system volume. To ensure that the App Volumes agent runs both scripts, you can add the following to the script on the Writable Volume:

  if exist "%SVAgent%\Config\Custom\uia_plus_profile\%~nx0"
("%SVAgent%\Config\Custom\uia_plus_profile\%~nx0")

• [2115593] A Writable Volume move or copy operation might fail when bulk operations are performed on many volumes.

  Workaround: Retry the move or copy operation.

App Volumes Documentation

• For information about how to install, deploy, and upgrade Omnissa App Volumes see Omnissa App Volumes Installation Guide.
• For information about how to configure and use Omnissa App Volumes see Omnissa App Volumes Administration Guide.

Omnissa App Volumes documentation is available at Omnissa Product Documentation.

Internationalization

App Volumes content is available only in English.

Support Contact Information

To receive support, access Customer Connect.

To file a Support Request in Customer Connect and via Cloud Services Portal, see How to file a Support Request in Customer Connect and via Cloud Services Portal -6000005.

Original source

Omnissa Workspace ONE Tunnel Tunnel Container 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.

Omnissa Workspace ONE Tunnel Container 26.03

What’s New

New ARM64 build

Introducing a native ARM64 build, enabling support for ARM‑based systems alongside x86 and x64 systems.

Minimum Requirements

Workspace ONE UEM Console 2410 or later

Resolved Issues

We are always working to improve Workspace ONE Tunnel with every release. There are no major bug fixes to report.

Known Issues

We haven’t identified any notable known issues in this release. If you’re facing any problems, feel free to reach out to our support team.

Original source

We’re excited to share the new release of Workspace ONE UEM version 2604!

Read on to learn about the new features and improvements in this release.

Urgent Notification regarding legacy Domain End of Service

As part of the migration from legacy VMware-owned domains to Omnissa-owned domains, customer 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 this Release

Admin Experience

New Workspace ONE UEM Console experience

Experience a redesigned Workspace ONE UEM console featuring a modern layout, intuitive navigation, and a refreshed Device List View to improve admin efficiency. This feature is now Generally Available and is enabled as the default console experience. The Organization Group picker is now prominently accessible in the app header, making it easier to switch context across your deployment. Administrators can opt in to the new Device List View or continue using the legacy view. For more details, see KB Article.

Improved user detail visibility in Device List View

Administrators can now view accurate user details directly in the Device List View, even when encryption is enabled. Encrypted user detail fields (First Name, Email Address, etc.) previously displayed the placeholder text “Encrypted” and now show the correct user information, while the underlying data remains encrypted in the database.

Enhanced troubleshooting experience using Device Operations tab

The new Device Operations tab provides administrators a unified view of all device actions. This interface combines Legacy Commands and Modern stack actions into one consolidated timeline, allowing users to track operations from initiation to completion. By minimizing context switching, administrators can diagnose issues more quickly and efficiently. For more information, see Device Operations Tab.

Android Management

Mobile Network Slicing Support (Custom DPC)

Android 13+ supports mobile network slicing, enabling Custom DPC EMMs to configure how enterprise apps utilize carrier network resources. You can now assign network slices to specific applications or globally to all work applications. You may also restrict applications to only using the assigned network slice.

Enhanced Screen and Display Controls for Custom DPC

You now have more precise control over screen timeout and brightness, including the option to lock brightness at a fixed level on corporate-owned devices. Minimum OS version varies based on the device management mode:

• Work Managed mode on Android 9+
• Corporate Owned Personally Enabled (COPE) mode on Android 15+

For more information, see our Android Device Management documentation.

Certificate Management

Expanded Entrust Dynamic SCEP challenge support

Workspace ONE UEM now supports flexible parameter pass-through for Entrust Dynamic SCEP challenges, removing the previous three-parameter limitation (IGUsername, IGGroup, DeviceType). Administrators can now configure any parameters required by their Entrust certificate templates.

Key benefits:

• Prevents enrollment failures caused by missing Entrust-specific parameters
• Supports complex template configurations without predefined parameter restrictions

Freestyle Orchestrator

Streamline onboarding entitlements in Android workflows

Onboarding entitlements within workflows allow administrators to prioritize resources essential for onboarding that take precedence over other resource assignments. For more information, see Onboarding Workflows.

Upgrading the communication pipeline from UDS to gRPC for macOS

Administrators now have more consistent workflow executions with our replacement of the communication pipeline between the workflow engine and macOS intelligent hub. This ensures that workflow step statuses are sent reliably so that execution can proceed to the next step. This change is in Limited Availability and will require Workspace ONE Intelligent Hub for macOS version 26.04. To have this enabled for your environment, contact your Account team.

iOS Management

App preservation during MDM migration

The new Preserve Applications setting in ADE profile now provides enhanced control for preserving managed applications during MDM migration scenarios. Administrators can specify which apps must be preserved and available immediately after migration during the Setup Assistant phase—choosing to await all apps or selecting specific critical applications. This ensures essential apps are ready before devices reach end users, minimizing downtime and eliminating the need for manual app reinstallation. The enhancement streamlines migrations, reduces IT intervention, and delivers fully configured devices ready for immediate productive use. For more information, see App preservation during MDM migration.

DDM app status subscriptions for iOS

On supported iOS devices, app-related Declarative Device Management (DDM) status subscriptions are enabled automatically, so application state can flow through declarative reporting without additional admin setup.

Key features:

• Automatic enablement: App-related DDM status subscriptions activate automatically on compatible iOS devices with no manual setup required
• Real-time app inventory: Application state flows through declarative reporting, keeping managed app data current and aligned with device-reported information
• Enhanced visibility: Console displays more accurate, up-to-date information about installed applications as iOS surfaces it through DDM
• Improved troubleshooting: Reduced blind spots when auditing app deployments, verifying installations, or diagnosing assignment issues across your fleet.

Platform-based default ADE profiles for automated enrollment

Administrators can now configure separate default Automated Device Enrollment (ADE) profiles for iOS, macOS, tvOS, and visionOS. This makes mixed-fleet onboarding more predictable. Each platform can land on the right baseline profile automatically as devices sync, with less manual cleanup and fewer mismatched assignments when you expand ADE across your Apple estate.

Enhanced Apple App platform management - Universal App support

With this Limited Availability feature, the Workspace ONE UEM console now dynamically recognizes and manages supported platforms for apps imported from Apple Business Manager, replacing previous hardcoded logic. An admin can automatically sync and assign the same application for iOS, iPadOS, visionOS, macOS, and tvOS from ABM into the console without having to sync an app version for each individual operating system.

Key enhancements include:

• Dynamic platform detection: Automatically identifies supported platforms (iOS, iPadOS, visionOS, macOS, and tvOS) from Apple Business Manager metadata
• Flexible app assignment: Enhanced VPP app assignment page enables platform-specific deployment selection
• Universal app support: Streamlined deployment workflows for Universal Apps across all supported Apple devices

These updates ensure seamless app management, flexible deployment options, and alignment with organizational policies for Apple device ecosystems. For more information, see Universal Apps.

Automatic Apple OS version seeding

Workspace ONE UEM now automatically detects and seeds new Apple OS versions across all platforms (iOS, iPadOS, macOS, watchOS, and tvOS). When a new OS version is detected or when a device enrolls with an unseeded OS version, UEM automatically seeds it and makes it immediately available for use in Enrollment Restrictions, Smart Group Criteria, Compliance Policies, Add Device, and ADE/DEP profiles, without relying on manual seeding. Administrators receive a notification when a new Apple OS version is available.

Support for OS 26.4 MDM and DDM payload and key changes

UEM now includes Apple OS 26.4 updates for MDM payloads and DDM declarations. New 26.4 keys and declaration types appear in the Console as you roll out policies aligned with Apple’s current device management specifications.

Target policies and content by Apple device model

Smart Groups now allow you to filter by Apple device model, so you can assign configurations and apps to particular hardware types using the same model names found in Enrollment Restrictions. This update lets administrators deploy test builds to lab devices, apply camera policies only to supported models, or roll out updates by device generation, all without the need for manual device lists or error-prone naming.

Key features:

• Familiar model selection: Define audiences using the same clear Model names you already use in Enrollment Restrictions
• Multi-select capability: Multi-select option allows coverage of multiple models in a single group
• Dynamic membership: Group membership automatically updates based on device-reported models, ensuring accuracy as inventory changes
• Data quality protection: Devices without a reliable model value are excluded from model-based groups to prevent silent mis-application of criteria
• Rule compatibility: Model-based rules work alongside your other Smart Group rules

macOS Management

Simplified macOS application deployment and management

The Enterprise App Repository (EAR) for macOS eliminates manual app packaging and enables admins to deploy enterprise applications as easily as App Store apps—streamlining deployment and ongoing maintenance.

• Curated app catalog
  • Deploy enterprise apps directly from the repository without manual packaging
  • Add apps via Add > Enterprise App Repository > macOS to browse available applications
• Intelligent search & discovery
  • Search applications by name or vendor to quickly find what you need
  • Filter and browse the catalog efficiently
• Seamless upgrades
  • Apps with available updates will show the corresponding status in the Apps List View
  • Seamlessly update previously deployed apps, even if they were originally added manually

For more information, see Add macOS applications from the Enterprise App Repository.

Platform SSO with Automated Device Enrollment in macOS 26

With this Limited Availability feature, macOS 26 streamlines Platform Single Sign-On (PSSO) configuration by integrating it directly into Setup Assistant, enabling first-user account creation through Identity Provider authentication. This streamlined workflow delivers faster onboarding, improved security, and simplified deployment by replacing multi-step setup processes with one integrated flow.

How it works:

• During the Setup Assistant, users authenticate using their Identity Provider (such as Omnissa Access, Okta, Microsoft Entra ID, etc.).
• The Setup Assistant temporarily pauses while the Platform SSO application and necessary profiles are deployed to the device.
• macOS automatically completes the registration for Platform SSO.
• A new first-user account is created using the authenticated IdP credentials, which is then immediately registered with the Platform SSO frameworks.

Enhanced admin experience for macOS software distribution

Workspace ONE UEM now provides administrators with the ability to customize macOS application names using a new Display Name field. When adding macOS applications, admins can now assign custom display names for different versions of the same application while the parent application name remains unchanged. A future release of macOS Intelligent Hub will allow for this value to be displayed to users in the Hub Catalog. Additionally, the supported models and minimum OS fields have been removed from the macOS application workflow to streamline the app management process. This allows for applications to be deployed to macOS virtual machines. When adding new macOS applications, administrators will see an informational banner notifying them of these field removals to ensure awareness of the updated workflow.

Declarative Device Management Assets for macOS

Declarative Management for macOS now supports User Identity asset for eligible macOS devices. You can create a single User Identity asset, reuse it across declarative configurations, and manage it through the standard declarative profile workflow (add, edit, assign, and delete). That gives admins a consistent way to supply identity context for declarative scenarios without duplicating the same data across multiple declarations. For more information, see Declarative Device Management.

Enhanced Apple App platform management - Universal App support

With this Limited Availability feature, the Workspace ONE UEM console now dynamically recognizes and manages supported platforms for apps imported from Apple Business Manager, replacing previous hardcoded logic. Administrators can automatically sync and assign the same Application for iOS, iPadOS, visionOS, macOS, and tvOS from ABM into the console without having to sync an app version for each individual operating system.

Key enhancements include:

• Dynamic platform detection: Automatically identifies supported platforms (iOS, iPadOS, visionOS, macOS, and tvOS) from Apple Business Manager metadata
• Flexible app assignment: Enhanced VPP app assignment page enables platform-specific deployment selection
• Universal app support: Streamlined deployment workflows for Universal Apps across all supported Apple devices

These updates ensure seamless app management, flexible deployment options, and alignment with organizational policies for Apple device ecosystems. For more information, see Universal Apps.

Platform-based default ADE profiles for Automated Enrollment

Administrators can now configure separate default Automated Device Enrollment (ADE) profiles for iOS, macOS, tvOS, and visionOS. That makes mixed-fleet onboarding more predictable. Each platform can land on the right baseline profile automatically as devices sync, with less manual cleanup and fewer mismatched assignments when you expand ADE across your Apple estate.

Support for OS 26.4 MDM and DDM payload and key changes

UEM now includes Apple OS 26.4 updates for MDM payloads and DDM declarations. New 26.4 keys and declaration types appear in the Console as you roll out policies aligned with Apple’s current device management specifications.

Resource Management

Percentage based phased rollout for internal apps

Phased Deployment is now Generally Available for Internal apps. Additionally, you can now configure phases to target a specific percentage of your device pool. In the previous release, phased deployment required setting up specific Assignment Groups for each phase. This enhancement relieves you of the overhead of creating and maintaining custom Assignment Groups for each phase. It gives you greater flexibility and control over your rollout strategy. Moreover, for progressed phases, you’ll now see additional progression details captured at the moment the deployment has advanced. For more information, see Phased Deployment of Resources.

Vulnerability Defense

Vulnerability Defense integration with CrowdStrike

Workspace ONE UEM 2604 offers Limited Availability for Workspace ONE Vulnerability Defense, bringing seamless assessment, prioritization, and remediation directly into the Omnissa platform.

Key Capabilities

• CrowdStrike Falcon Integration: Seamlessly integrate Workspace ONE UEM with CrowdStrike Falcon Exposure Management to retrieve comprehensive vulnerability assessment data
• Automated Device Correlation: Automatically map CrowdStrike vulnerability data to your Windows devices in Workspace ONE UEM
• Risk-Based Prioritization: Access context-rich dashboards that enable rapid, data-driven prioritization of security risks
• Streamlined Remediation: Deploy remediations directly through Workspace ONE UEM’s native app and OS management capabilities to address vulnerabilities and reduce organizational risk

Windows Management

Windows server management: Enroll and manage Windows servers using Intelligent Hub

Windows Server management is now Generally Available. This feature was previously available under Limited Availability and is now enabled by default for licensed tenants. Administrators can enroll and manage Windows Server 2016, 2019, 2022, and 2025 devices, including Server Core, using Workspace ONE Intelligent Hub. Management is Hub-based.

Supported capabilities include:

• Hub-managed profiles: ADMX-backed, DDUI-backed, Certificate (SCEP not supported), Custom Settings, and Managed Resources
• Security Baselines enforcement and remediation
• Granular Patch Management with scheduled maintenance windows, zero-day patching, deferral notifications, and per-device patch lifecycle logging
• Internal application deployment via SFD with assignment-level retention control on enterprise wipe or unassignment
• Sensors and Scripts for custom data collection and on-demand or scheduled actions
• Roles and Features Sampling for automatic inventory of installed server roles and features
• Freestyle Orchestrator workflows with sequenced execution and conditional logic
• Workspace ONE Assist for remote view, remote control, file transfer, and remote shell

For more information, see Windows Server Management.

Granular patch management with on-demand update deployment

Administrators can now deploy specific Windows updates, such as critical security KBs to targeted Windows desktops and servers outside of their standard Windows Update for Business ring configuration. This capability enables a rapid response to urgent security patches without disrupting established update schedules. For more information, see Granular Patch Management.

Unified App Sampling: Remote application uninstallation

Administrators can now remotely trigger the uninstallation of applications collected through Unified App Sampling. This enhancement lets you control apps that are not managed, are unwanted, or not allowed on devices from the Workspace ONE UEM Console or through the supported APIs. For more information, see Assign Applications to your Windows Device.

Resolved Issues

Admin Experience

• FCA-212233: Settings Summary XML export fails when the Organization Group (OG) name contains a comma (,).
• FCA-212663: Images vanish from custom message templates after they are saved.
• FCA-213345: Incorrect devices scoped for bulk actions in the Device List View when filters are applied on Tags, Smart Groups or User Groups.

Android Management

• AGGL-20077: Managed config keys do not update when adding new version of internal app.
• AGGL-20435: Newly enrolled Zebra devices are showing up with the wrong oeminfo.

Common Services

• CMSVC-20840: OEM and model IDs are silently ignored during SG creation.

Core Platform

• CRSVC-62551: Script trigger updates on console is not synced to device.
• CRSVC-73705: Enhanced SCEP auto-renewal logic to support user-based profiles where signed user & enrollment user are not the same.

Content Management

• CMCM-191789: Content app on iPad and Android, displays duplicate of same folders.

iOS Management

• AAPP-21692: VPP apps are not receiving app settings, and users encounter an error stating, “no server has been configured for this app.”

Resource Management

• ARES-32880: Multiple profile removal failure events displayed in troubleshooting logs of mobile devices for profiles deleted from UEM.
• ARES-32876: Application removal protection triggered despite device threshold not being met within time window, causing false alarms.
• ARES-36784: Passcode not cleared from shared iOS devices when user logs out of it.
• ARES-37278: Incorrect app config delivered to newly enrolled devices assigned to future-dated Internal app assignments.
• ARES-19301: Profiles requiring WLAN MAC address lookup are delivered to iOS devices without the required value, resulting in authentication failures.

User Management

• UM-10208: Directory-type admin account is unable to modify roles while logged in at Partner-type OG.
• UM-10209: Inconsistent Full Name and Display name during OIS SCIM Provisioning.
• UM-10484: User Search option in Add Device Registration screen permits search for empty string.
• UM-10592: Admin Group Deletion Removes Roles from existing Admins.
• UM-11073: Enrollment to a child OG fails for basic users in OIS-enabled tenants.
• UM-11104: SSP authentication to a child OG fails for basic users in OIS-enabled tenants.

Windows Management

• AMST-44384: When ProfileDeliveryAtScaleFeatureFlag is enabled, nodes are absent from the profile syncML when resuming.
• AMST-46045: Apps installed on the Hololens are appearing as Not managed, which is preventing us from uninstalling them.

Known Issues

We haven’t identified any notable known issues in this release. If you are facing any problems, feel free to reach out to our support team.

Release Availability

We strive to deliver high-quality products, and to ensure quality and seamless transitions, we roll out our products in phases. Each rollout may take up to four weeks to accomplish and is delivered in the following phases:

• Phase 1: Demo, Shared SaaS UATs, and Latest Mode UATs
• Phase 2: Shared SaaS environments
• Phase 3: Latest Mode environments

Getting Ready for Major OS Releases

To prepare for the upcoming software updates from major device vendors, read through the Getting Ready for Major OS releases section of the Omnissa Product Documentation.

Documentation

To learn more about Workspace ONE UEM, browse Workspace ONE UEM Documentation.

Localized Content for Omnissa Docs

For details on Omnissa’s localization strategy, see the KB article: Announcing Omnissa Localization Support.

Support Contact Information

To receive support, access Omnissa Customer Connect. For information about filing a Support Request in Customer Connect and using Cloud Services Portal, see the KB article here.

Original source

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 Coming in May 2026

The following features are now in preview.

Email as a Notification Channel (BYO SMTP)

Administrators can now send Hub Services notifications via email in addition to push notifications, ensuring critical communications reach end users even when push notifications are disabled on their devices. This feature uses a Bring-Your-Own (BYO) SMTP configuration.

Send Notifications to Multiple Groups

Administrators can now select multiple target audience groups of the same type when creating a notification, eliminating the need to recreate the same notification for each group.

• When building a notification, administrators select a single target audience type (Omnissa Access user groups, Organization Groups, or Smart Groups) and then choose multiple groups within that type.
• The notification is sent to all selected groups in a single action.
• The Notification List is updated to reflect the multi-group notification.

Previously, administrators could only target one group per notification and had to use the “Edit and Send” workaround to reach additional groups.

Launch Hub Services Admin Console in a New Tab

When an administrator clicks Manage Hub Experience from the account icon in the Workspace ONE Intelligent Hub web portal, the Hub Services admin console now opens in a new browser tab instead of replacing the current tab. This allows administrators to keep the Hub web portal open while managing Hub Services settings.

Dark Mode for the Hub Services Admin Console

The Hub Services admin console now supports a dark mode UI theme, providing improved comfort in low-light environments and a modern visual experience.

Edit Default Categories in Hub Catalog (browser only)

Previously, the Hub Catalog always displayed certain default categories – including Workspace ONE UEM-provided categories and system categories such as All Apps, Web Apps, and Virtual Apps – with no way for administrators to hide or control them. This often resulted in the same app appearing multiple times across default and custom categories.

With this enhancement, Hub Services now allows administrators to control the visibility of these default categories in the browser-based Hub Catalog.

Original source

Workspace ONE Tunnel 26.03

New Features

Support zero-downtime Tunnel certificate rotation

Starting with Workspace ONE UEM 2602, Tunnel client on iOS supports zero-downtime server certificate rotation for both Workspace ONE CA and 3rd Party CA issued certificates.

New Custom Setting

Introducing Tunnel profile custom setting to manage Rapid DTR sync interval. The Tunnel client will periodically check-in with Workspace ONE APIs on this interval and locally update the DTR with changes, if any.

Add the following custom setting in the VPN-Tunnel profile > Custom Configuration section.

Key:

ClientSyncInterval

Value: Time in minutes (Default: 240)

Note

Starting with Tunnel for iOS 26.03, the client no longer supports the Tunnel server KVP (client_sync_interval). If the ClientSyncInterval custom setting is not configured, the client defaults to 240 minutes.

Minimum Requirements

• iOS 15+, iPadOS 15+
• Workspace ONE UEM 2402+
• Workspace ONE Unified Access Gateway 2406+ | Workspace ONE Tunnel Container 24.12+

Resolved Issues

We are always working to improve Workspace ONE Tunnel with every release. There are no major bug fixes to report.

Known Issues

We haven’t identified any notable known issues in this release. If you’re facing any problems, feel free to reach out to our support team.

Original source

Omnissa Workspace ONE® Assist allows Omnissa Workspace ONE® UEM administrators to remotely access and troubleshoot devices in real time while respecting end-user privacy.

Workspace ONE Assist for macOS Release Notes describes the new features and enhancements in each release. This page contains a summary of the new capabilities, issues resolved, and known issues reported in each release over the last 18 months.

Workspace ONE Assist 25.11.1 - April 2026

New Features

In this release, we’ve made an update addressing functionality and performance improvements with no new features.

Minimum Requirements

Listed are the minimum requirements:

• Workspace ONE Assist Console 25.11.1
• macOS 10.15 (Catalina) or later
• Workspace ONE Intelligent Hub 24.11 or later
• Workspace ONE UEM 24.06 or later
• Latest versions of Chrome, Edge, Firefox, or Safari browsers
• For macOS Ventura, Workspace ONE Intelligent Hub should be 24.11 or later
• macOS Ventura requires a Login Profile to be configured in UEM

Resolved Issues

• AET-23359: Advanced keyboard support fixes.
• AET-22770: Distorted image on remote connections in Safari with Assist v25.11 on macOS.

Known Issues

• AET-23387: Intermittently, Japanese input causes random applications to open instead of typing text.

Original source

Workspace ONE Tunnel for Android 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 over the last 12 months.

Workspace ONE Tunnel 26.03

New Features

Support zero-downtime Tunnel Server certificate rotation

Starting with Workspace ONE UEM 2602, Tunnel client on Android now supports zero-downtime server certificate rotation for both Workspace ONE CA and Third Party CA issued certificates.

New information added to Client Access Log

• Connections to the Web Proxy
• DNS Request and Response
• Tunnel Server configuration

Minimum Requirements

• Android 12 and later
• Workspace ONE UEM Console 2410 or later
• Workspace ONE UAG 2406 or later | Workspace ONE Tunnel Container 24.12 or later

Resolved Issues

We are always working to improve Workspace ONE Tunnel with every release. There are no major bug fixes to report.

Known Issues

We haven’t identified any notable known issues in this release. If you’re facing any problems, feel free to reach out to our support team.

Original source

Omnissa Workspace ONE Tunnel 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 over the last 12 months.

Omnissa Workspace ONE Tunnel 25.11

New Features

• Support for IPv6 CIDR notation in DTR.
• Ability to send Tunnel client log to Workspace ONE UEM.
  • Use the “Send logs to admin” option to upload the Tunnel client log to UEM.
  • Logs can be retrieved from the UEM console by navigating to Device → Details View → More → Attachments .

Client Versions

• 25.11 - macOS modern client delivered through the Customer Connect Portal
• 22.04.6 - macOS App Store Tunnel delivered through App Store

Minimum Requirements

• macOS version 12.0 or later
• Workspace ONE UEM 2402 or later
• Unified Access Gateway 2406 or later | Workspace ONE Tunnel Container 24.12 or later

Resolved Issues

Note

The numbers included before the resolved issues are used for internal issue tracking.

PPAT-20589: Improvements to Trusted Network Detection logic to better handle HTTP redirects during network validation.

Known Issues

We haven’t identified any notable known issues in this release. If you’re facing any problems, feel free to reach out to our support team.

Original source

We’re excited to share the new release of Workspace ONE UEM version 2410! Read on to learn about the new features and improvements in this 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 for more information.

What’s New in this release

Admin Experience

Intuitive page navigation for Workspace ONE UEM

Explore our new page navigation for Workspace ONE UEM. Similar functions are now categorized together in sub-menus, with updated labels. For more information, see the KB article.

Revamped UEM API Explorer page includes comprehensive API metadata and search features

We’ve built a new API Explorer to provide enhanced security, improved search functionality, and reduce page load times.

Overcome random MAC address challenges with Cisco Identity Services Engine (ISE) 3.1+ integration

The Workspace ONE UEM and Cisco Identity Services Engine (ISE) 3.1+ integration is now available to everyone. This allows end users’ devices to connect securely to network resources, even when they use randomized MAC addresses. For more information and integration instructions, refer to the Tech Zone article Integrating Workspace ONE UEM and Cisco ISE v3.1 and beyond.

Troubleshoot large device log files easily

You can now collect and access large device logs more efficiently. The previous process involved uploading multiple files from Workspace ONE Hub to UEM, requiring administrators to download and merge numerous separate files, which was time-consuming for troubleshooting large log files. Device logs are now uploaded and automatically merged into a single file (up to 200MB), reducing the effort and time needed to troubleshoot devices. This feature is supported only for Android and Windows platforms, starting from 2408 release of the Android and 2410 release for Windows Hub clients.

Modern SaaS Architecture is now available for MSP Partners

We are excited to extend the rollout of the Modern SaaS Architecture to Managed Service Provider (MSP) partner environments, which will be introduced to your environments in the coming months. With this rollout, MSP partner environments can leverage the next-generation Workspace ONE features that enhance performance, scalability, and management capabilities alongside the ongoing support for existing Partner Organization Group use cases.

Omnissa Branding Update

The Workspace ONE UEM console has been updated to align with the new Omnissa brand identity. We have made changes to all the login screens, message templates, URLs, and policy documents to conform to Omnissa standards. We have also replaced old logos, illustrations,and labels with the new Omnissa changes. For more information, see the KB article.

Workspace ONE Mobile Threat Defense Dual Enrollment Configuration by Smart Groups

We initially released support for the configuration of Workspace ONE Mobile Threat Defense (MTD) by Smart Groups in UEM 2406. Now, with Workspace ONE MTD, you can also configure Dual Enrollment support for Android devices by Smart Group. Android Dual Enrollment allows you to enable MTD in both the personal and work profiles of their users’ devices. You can also introduce a custom settings profile using the MTD configuration page for specific Smart Groups, enabling support for any future MTD custom settings. This requires Workspace ONE UEM version 2410 Patch 2 and Intelligent Hub 25.01+ on Android.

Faster resource delivery for Tag and Organization Group changes

Resource delivery now happens instantly whenever a tag is added or removed from a device, or when its Organization Group changes. Based on the updated tags or Organization Group, the device will check in immediately and receive the necessary installations or removals. This enhancement ensures faster updates for applications and profiles, reducing delays in bringing devices to their desired state in modern architecture enabled UEM environments.

Android Management

Support for Corporate Owned Personally Enabled mode with Android Management API

Organizations can now manage Android devices in Corporate-Owned Personally Enabled (COPE) mode using AMAPI. This mode was previously only supported with Android using the Custom DPC management type. The QR code generation wizard for corporate-owned Android devices has been enhanced to support generation of QR codes for AMAPI. Also, Android profiles for AMAPI feature new payloads and settings to support COPE devices. For more information on Android Management modes and AMAPI, see Integrating Workspace ONE UEM with Android.

This feature requires the UEM modern architecture and is enabled in Workspace ONE UEM 2410 patch 5.

Enhancements to Application Management for Android Management API

For devices managed using AMAPI, Workspace ONE UEM introduces multiple enhancements to application management that bring it to parity with Custom DPC Android device management. Administrators can now remotely configure applications using Application Configuration, which in turn enables organizations to deploy OEMConfig applications. A new Application Policy tab has been added to the application assignment flow for Android public apps that supports app-specific policies, such as managing runtime permissions. Finally, the Auto Update Priority setting is now supported for devices managed using AMAPI.

This feature requires the UEM modern architecture and is enabled in Workspace ONE UEM 2410 patch 12.

Support for Full-Device VPN with Workspace ONE Tunnel and Android Management API

Workspace ONE Tunnel is now supported on devices managed using AMAPI. Administrators can now configure Workspace ONE Tunnel through the Tunnel and Always-On VPN profile payloads for AMAPI. When assigning public Android applications, administrators can also select a Full-Device VPN profile for AMAPI devices. Support for Per-App Tunnel mode will be added in a future update.

This feature requires the UEM modern architecture and is enabled in Workspace ONE UEM 2410 patch 12.

Updates to Android Public Application Management

In recent years, Google has revamped the Google Cloud APIs that Workspace ONE UEM leverages to provision public applications to Android devices through the managed Play Store. Workspace ONE UEM now supports the updated Google Cloud APIs. For more information, see the KB article Upcoming Changes to Android Public Applications.

Support for Root Certificates for enterprise WiFi profiles (Custom DPC)

Workspace ONE UEM now supports setting up to two trusted Root Certificates in WiFi profiles for Custom DPC devices. This allows administrators to set two trusted certificate authorities for a WPA2 Enterprise SSID. In turn, this allows organizations to update network servers to use a certificate issued by a new certificate authority without disrupting connected devices.

Freestyle Orchestrator

Freestyle for Mobile – Android and iOS Devices (General Availability)

Our powerful workflow orchestration solution is available for Android and iOS platforms. Create intuitive, conditional workflows using Freestyle’s drag-and-drop UI to sequence the deployment of applications and profiles to your mobile device fleet.

• Target devices based on Smart Group Membership
• Leverage device conditions for granular targeting
• Empower end users with on-demand workflows they can initiate through the Intelligent Hub app
• Configurable retry behavior
• Robust deployment tracking at both the workflow level and individual step execution level

Note: To use this feature, your environment must be Modern Stack-enabled. For information regarding the rollout schedule, view KB article.

Enhanced Reporting for Application Deployments within Freestyle Orchestrator

Gain better visibility into application deployment outcomes with improved reporting capabilities for Windows devices. When app deployments are triggered from Freestyle workflows, you’ll now receive detailed status updates, clear failure reasons, and timestamp enrichments. The minimum versions necessary to support this are UEM 2410, HUBW 2410, and SFD 2410.

Export evaluated devices within Freestyle Workflow details

Admins can now export evaluated (In Progress, Completed, Failed, Blocked) devices from within the Workflow Details page. Exporting the device table leverages the export framework within UEM Monitoring, so exported devices can be found there. Modern Stack is required for this feature.

iOS Management

Declarative Device Management

Workspace ONE UEM now supports 9 new status items via Declarative Device Management (DDM). For eligible devices, Workspace ONE UEM will automatically receive these attributes as they change on managed iOS devices.

New Declarative Configurations integrate with Apple’s GitHub MDM developer documentation enabling faster implementation and updates. Supported new configurations include Math Settings (iOS 18+) and Software Update Settings (iOS 18+).

Application Management

Workspace ONE UEM now collects and displays the Distributor Identifier application attribute on the Device Details > Apps tab. This attribute indicates where an application was downloaded from, including alternative app marketplaces available in the European Union.

Application configuration size limit increased to 30,000 characters

This enhancement allows configuration and deployment of applications requiring significantly larger configuration data, such as certificates.

Profiles

Enhanced existing Restrictions, VPN, Skip Setup Assistant, Web Clip, and Font payloads and added new payloads for ACME Certificate and Relay.

Linux Management

New Restrictions and Passcode profiles introduced for enrolled devices, enabling configuration of device restrictions and mandatory passcode restrictions.

macOS Management

Omnissa rebranding changes require user action due to changes in bundle identifiers for Intelligent Hub for macOS and other supporting software.

Declarative Device Management features introduced for macOS, including new Declarative Configurations for Software Update Enforcement and Passcode DDM Configuration.

Updated Payloads and New Payloads such as Relay Profile, ACME Certificate, DNS Proxy, and Font Payload added.

Download the rebranded Admin Assistant version 24.11 from the UEM dashboard.

Resource Management

Installation metrics now retained upon Resource and Smart group updates, visible on the Deployment Tracking page as Currently assigned.

Rugged Device Management

Deprecation of Sideloading and Barcode Mobile Staging features for Android devices; QR Code and Stage Now Barcode features remain supported.

Support for Zebra LifeGuard OTA for applying LifeGuard updates to Zebra Android devices.

Tunnel

Updated Tunnel administration for enterprise management and monitoring capabilities, allowing setup and management of multiple Tunnel environments in a single organization group (Limited Availability).

visionOS Management

Support for enrolling and managing Apple Vision Pro devices with visionOS 1.1 and higher.

Supports Automated Device Enrollment (ADE) for visionOS 2.0+ and Account Driven User Enrollment (ADUE) for visionOS 1.1+.

Added profiles for visionOS: Wi-Fi, Restrictions, Credentials, Custom Settings.

Added commands for visionOS: Query, Lock, Clear Passcode, Enterprise Wipe, Device Wipe, Custom Command.

Windows Management

Enhanced certificate template for OID-SID extension support to meet certificate requirements enforced by February 11, 2025.

Intel’s Chip to Cloud capabilities enabled through Workspace ONE UEM Integrations panel, supporting Intel vPro Enterprise remote manageability.

New Windows Security Baseline Templates for Windows 11 24H2.

Support for push notifications in the new WinUI-based Hub.

Workspace ONE Mobile Threat Defense Dual Enrollment Configuration by Smart Groups now supported with 2410 patch 2.

Resolved Issues

Extensive list of resolved issues and patches from 2410 Patch 1 through Patch 43 addressing various bugs, improvements, and security fixes across all platforms and features.

Known Issues

List of known issues including MacOS Hub App loading state issue, Freestyle for Mobile limitations, and Apple Vision Pro DEP enrollment authentication issue with workarounds.

Release Availability

Products are rolled out in phases over up to four weeks: Phase 1 (Demo, Shared SaaS UATs, Latest Mode UATs), Phase 2 (Shared SaaS environments), Phase 3 (Latest Mode environments).

This version is initially available to SaaS customers on the latest mode; features will be available to on-premises or managed hosted customers with the next on-premises release. Modern SaaS Architecture features are not available in on-premises releases.

Getting Ready for Major OS Releases

Guidance provided in the Getting Ready for Major OS releases section of Omnissa Product Documentation.

Documentation

Links to Workspace ONE UEM Documentation and Omnissa localization strategy.

Support Contact Information

Access to Omnissa Customer Connect and information about filing Support Requests.

Original source

Omnissa Workspace ONE Intelligent Hub for iOS 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 version.

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.

Workspace ONE Intelligent Hub 26.03 - April 2026

• New Features
• Minimum Requirements
• Download Instructions
• Resolved Issues
• Known Issues

New Features

Login Hint for Conditional Access Registration

Post enrollment, when users log in to register for conditional access, user UPN will be fetched from UEM and will the pre-populated on the Microsoft prompt so they will have to enter the password only.

Improvements to CICO

Users can now send logs when Check Out fails and in Access Error Screens. This option is available in the overflow menu under Send Feedback.

Minimum Requirements

• iOS 17+, iPadOS 17+
• Workspace ONE UEM Console 2206+

Download Instructions

• Prior Version is Installed:
  Direct end users to update the app when prompted. The application seamlessly updates over the existing application version without disrupting device’s enterprise functionality.
• Prior Version is Not Installed:
  Direct end users to download it from the App Store.

Resolved Issues

• HUBI-13082: Conditional Access registration button is not visible on ADUE-enrolled iOS devices.
• HUBI-13089: Improvements to the translation of the quick action “make noise” to translate to “let it ring”.
• HUBI-12090: Duplicate Devices are seen after multiple check-ins and check outs.
• HUBI-13089: Improvements to the German translation for the Make noise Quick Action.
• MTD-3253: Multiple MTD background operations causing device to overheat.

Known Issues

We haven’t identified any notable known issues in this release. If you are facing any problems, feel free to reach out to our support team.

Original source

Omnissa Intelligence Release Notes describe the new features and enhancements in each release. These notes contain a summary of the new capabilities, issues that have been resolved, and known issues that have been reported. Use Intelligence for enterprise mobility management (EMM) planning and automation, to optimize resources, strengthen security and compliance, and to enhance user experience across your environment.

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.

Intelligence 26.04.20

New Features

• Introducing HP Warranty integration in Omnissa Intelligence.
  • You can now integrate your HP warranty and service entitlements information with Omnissa Intelligence so that you can build dashboards, reports, and workflows using HP warranty data.
  • For integration details, access HP Integration.
  • For data definitions, access Warranty Management - HP.

Resolved Issues

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

Known Issues

• We haven’t identified any notable known issues. If you’re facing problems, reach out to the Omnissa Global Customer Services (GCS) team.

[The release notes continue with detailed new features, resolved issues, and known issues for multiple previous versions of Omnissa Intelligence, including SDK releases, workflow enhancements, new Freestyle Orchestrator actions, network connectivity map features, Device Timelines, User Session Timelines, Virtual Machine Timelines, and more.]

Documentation

• Admin Documentation - For the latest content, access the Omnissa Intelligence Documentation.
• API Documentation - Use Omnissa Intelligence API documentation to find details on how to query and extract data for use in other business intelligence tools.
• Developer Documentation - You can find developer information for the Intelligence SDK on the Omnissa Intelligence SDK Developer Portal.

AI Policy at Omnissa

For details on Omnissa AI’s adoption of its own set of internal Ethical Principles that govern the development, deployment, and use of AI systems, see Understanding AI policy at Omnissa.

Support Information

• Access the Customer Connect site for help with your product.
• For details on filing support requests, access How to file a Support Request in Customer Connect portal.

Localized Content for Omnissa Docs

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

Original source