EnglishFrançaisDeutschEspañolItaliano日本語한국어NederlandsPortuguês (Brasil)中文 (简体)中文 (繁體, 台灣)
Skip to main content

September 1, 2026

Omnissa Workspace ONE Experience Management for Windows and Horizon

What's in the Release Notes?

Omnissa Workspace ONE® Experience Management for Windows and Horizon 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 in each release.

Experience Management 26.07 for Windows and Horizon

What's New

Windows and Horizon

  • Windows Service Inventory
    • IT admins can now inventory all Windows services across their device fleet, including service name, current status, and startup type.
    • Previously, the Experience Management agent only captured service start and stop events, leaving gaps when a service's state didn't change.
    • This feature gives admins continuous, accurate visibility into which services are running on every managed device.
    • For data definitions, access the Service inventory table on Omnissa Docs.
  • Enhanced OS Crash Analysis
    • OS crash events now include richer process-level and module-level diagnostics, identifying the actual root-cause driver or process behind a Windows Blue Screen rather than the generic kernel executor.
    • New attributes (Process Associated With, Caused By Module, Complete stack Trace) are added to the crash event schema, giving admins actionable crash data.
    • For setup details, access OS Crash Analysis on the Omnissa Docs site.
  • Experience Management Health Status Reporting to Hub
    • The Experience Management agent now reports its enablement state and health status directly to Workspace ONE Intelligent Hub.
    • You can see at a glance whether the agent is activated, connected, and collecting telemetry using the tlmtool command-line utility.
    • See Command line options for the utility tool on the Omnissa Docs site.
  • SSL Certificate Revocation Check Mode
    • Set the Experience Management agent to check if a previously valid certificate was recently revoked.
    • This check is an additional check to the certificate chain validation check that confirms that a trusted certificate authority (CA) issued the certificate, that it matched the hostname, and that it hasn’t expired.
    • For details, see Troubleshoot with SSL Certificate Revocation Check Mode.
  • High-Frequency 15-Second Telemetry Sampling (Limited Availability)
    • The agent now supports sending raw device and app performance data at a 15-second sampling frequency, enabling near-real-time visibility into CPU, memory, disk, and GPU metrics.
    • High-Frequency Performance Tracker
      • The Experience Management for Windows agent adds a High-Frequency Performance Tracker that collects raw application performance samples every 15 seconds and publishes aggregated events every 5 minutes, giving near-real-time visibility into CPU, memory, disk, and GPU metrics.
      • Included applications: Admins can specify individual applications to capture performance data for, in addition to what standard monitoring already covers.
      • Private Bytes attribute: Added to both standard and high-frequency performance events, to support memory-leak-detection analytics.
      • GPU data: Included when available on the device; omitted otherwise.
      • Single tracker subscription: A device can be subscribed to either the standard performance tracker or the High-Frequency tracker at a time, not both.
    • See the App performance table for applicable data definitions.
    • This feature is in Limited Availability (LA).
      • It's deactivated by default and isn't self-service - it's turned on via a local dynamic configuration file rather than an admin console toggle.
      • To activate it for your environment, reach out to your Omnissa account team to request access.

Windows only

  • Experience Management Telemetry Enablement (Limited Availability)
    • You can dynamically configure which telemetry event types are collected from devices directly through Experience Management.
    • Choose which events to collect for device and app performance data, and assign these policies to specific sets of devices.
    • Configuration changes propagate to all devices within 4 hours.
    • For details, see Experience Management Telemetry Enablement on the Omnissa Docs site.
    • Limited Availability: This feature is in Limited Availability (LA).
      • To activate it for your environment, reach out to your Omnissa account team to request access.

Minimum Requirements

Windows

Minimum requirements for Experience Management 26.07 for Windows

  • A Microsoft supported Semi-Annual Channel Windows 11 Version 21H2 or later
  • Windows Server 2022 or later
  • Hardware Specifications:
    • 1Ghz processor with minimum of 4 cores
    • 8GB RAM
    • 256GB Hard disk space
  • Omnissa Workspace ONE Intelligent Hub for Windows 25.06.10 or later
  • Workspace ONE Experience Management for Windows package
  • Omnissa Intelligence tenant opted-in and the Desktop Advanced Telemetry integration card activated

Horizon

Minimum Requirements for Experience Management 26.07 for Horizon

  • Use the Experience Management agent for Windows and Horizon 26.07 on Windows Horizon (single-session or multi-session).
  • Use the Horizon Agent 2506.1 or later.
  • Use the Horizon Client 2506.1 or later.
  • Use Horizon Connection Server 2506.1 or later in Horizon Enterprise deployments.
  • Use Horizon Edge 2603.2.0.
  • Connect your Horizon deployment to the Horizon Cloud control plane.
  • Follow the tasks outlined in the topic Experience Management for Horizon.

Resolved Issues

Windows

  • DCP-8807 - Improved security by replacing the embedded OpenSSL library with the native Windows security library (Schannel) for network communications.
  • DCP-10290 - Replaced OpenSSL with the native Windows SChannel secure-channel provider on Windows.
  • DCP-11136 - Fixed a delay during Experience Management agent upgrade/uninstall caused by legacy file-in-use detection.
  • DCP-11182 - Fixed an issue affecting IPv6 connectivity detection.
  • DCP-11315 - Patched the OpenSSL library used by the Windows agent to address security vulnerabilities.
  • DCP-11433 - Fixed an issue in dual-domain configurations where a blocked primary server endpoint did not trigger fallback to the secondary endpoint.
  • DCP-11448 - Addressed known vulnerabilities in the bundled libcurl library.
  • DCP-11801 - Fixed an issue where some snapshot telemetry events were missing supplemental data.
  • DCP-11855 - Fixed an issue where device NIC type incorrectly showed as "Unknown" in filter options.
  • DCP-11875 - Fixed a crash that could occur during telemetry event processing when a tracker unsubscribed.
  • DCP-11893 - Addressed known vulnerabilities in the bundled libcurl and protobuf libraries.
  • DCP-11902 - Fixed a crash in the Telemetry Agent affecting both RDSH and standard Windows endpoints.
  • DCP-11906 - Fixed an issue where the agent's network layer could stop responding, interrupting telemetry uploads.
  • DCP-11911 - Fixed a delay in flushing cached telemetry events to the backend.
  • DCP-11912 - Fixed an issue with stale device data not being cleaned up correctly during device resync.
  • DCP-11917 - Fixed an issue where NIC type showed as "Unknown" for a large number of devices.
  • DCP-11918 - Fixed an issue where Wi-Fi signal quality was incorrectly reported as 0%.
  • DCP-11932 - Fixed an issue where a failed agent upgrade could remove the existing installation instead of rolling back safely.
  • DCP-11966 - Fixed a deadlock that could occur during agent startup, affecting app usage tracking.
  • DCP-12003 - Fixed a memory leak related to certificate/key handling.
  • DCP-12053 - Updated the bundled libcurl library to address critical and high-severity security vulnerabilities.

Horizon

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

Known Issues

Windows

  • DCP-12206 - There is a known issue where the Experience Management Telemetry setting persists when the device is enrolled to a new org which doesn't have the setting activated.

Horizon

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

Download Instructions

Windows and Horizon

Windows only

  • Experience Management for Windows is delivered with the Workspace ONE Intelligent Hub for Windows app. Direct users to download the Workspace ONE Intelligent Hub for Windows app from getwsone.

Experience Management 25.09.2 for Windows

What's New

This patch release concerns Experience Management for Windows and not Experience Management for Horizon.

Windows

  • In this release, we’ve made updates containing general quality and performance improvements.

Minimum Requirements

Windows

Minimum requirements for Experience Management 25.09.2 for Windows

  • A Microsoft supported Semi-Annual Channel Windows 11 Version 21H2 or later
  • Hardware Specifications:
    • 1Ghz processor with minimum of 4 cores
    • 8GB RAM
    • 256GB Hard disk space
  • Omnissa Workspace ONE Intelligent Hub for Windows 24.12 or later
  • Workspace ONE Experience Management for Windows package
  • Omnissa Intelligence tenant opted-in and the Desktop Advanced Telemetry integration card activated

Resolved Issues

Windows

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

Known Issues

Windows

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

Download Instructions

Windows

Windows

  • Experience Management for Windows is delivered with the Workspace ONE Intelligent Hub for Windows app. Direct users to download the Workspace ONE Intelligent Hub for Windows app from getwsone.

Experience Management 25.09 for Windows and Horizon

What's New

Windows and Horizon

  • App Network Monitoring
    • We've added a new data entity to help you detect with real-user monitoring of process level network related experience issues.
    • App Network works on both physical Windows machines (managed by Workspace ONE or managed by a third-party unified endpoint management system) and Horizon single session virtual desktops, including persistent and non-persistent virtual desktops.
    • Horizon multi-session and RDSH-hosted desktop and apps are not supported.
    • This data includes user or device initiated process level network communication and errors per target IP address and port. A network target is a communication endpoint from the point of view of the machine.
    • Important event data and metrics collected per process include:
      • Process Name/Version
      • Successful Connections
      • Failed Connections and Error Codes
      • Connection Statistics
        • Connection Establishment Time
        • Network Volume
      • Destination IP/Port
      • Destination Type (Internet/Intranet/Data Center)
    • For details on how to activate the feature, access App Network.
    • Access the data definitions for Windows and Horizon.

Windows

  • Boot Time and Shutdown Time Sub-Segments
    • We enhanced the existing Boot and Shutdown events by adding additional duration details for every part of the Boot and Shutdown processes.
    • These enhancements help to determine what part of the Boot or Shutdown process is abnormally slow or causing bottlenecks.
    • Access the data definitions for Windows.
    • For the Boot Event, details include:
      • Main Path Session Duration
        • Boot Kernel Initialization Duration
        • Other Kernel Initialization Duration
        • OS Loader Duration
        • Boot Driver Initialization Duration
        • Boot Device Initialization Duration
        • Boot PNP Initialization Duration
        • System PNP Initialization Duration
        • Boot Prefetch Service Duration
        • Autochk Duration
        • SMSS Initialization Duration
        • Critical Services Initialization Duration
      • Post Boot Duration
        • User Profile Processing Duration
        • Machine Profile Processing Duration
        • Explorer Initialization Duration
      • Boot Session Duration
        • Session 0 Initialization Duration
        • Session 1 Initialization Duration
        • Session Other Initialization Duration
    • For the Shutdown Event, details include:
      • User Policy Duration
      • User Profiles Duration
      • User Session Duration
      • Services Duration
      • Preshutdown Duration
      • System Session Duration
      • Kernal Load Duration
  • External IP Intelligence
    • We added a network event to report a device’s current Public IP Address (IPv4 or IPv6).
    • Within Intelligence, this data is translated into device geolocation attributes like Country, City, and Latitude and Longitude. It also includes the current connected Internet Service Provider (ISP).
    • This new data is controlled by Privacy Settings and you must manually activate it for the system to report it.
    • This feature works on physical Windows machines.
    • Ensure and verify that firewall rules allow network access to ts.awmdm.com, ts4.awmdm.com, and ts6.awmdm.com for this feature to work.
    • Consider using DNS-based allow lists, as these will significantly reduce administrative overhead and ensure seamless transitions for future changes and traffic security enhancements.
    • This feature is activated by default in Experience Management and doesn’t need additional registry settings for UEM deployments.
    • Access the data definitions for Windows.
  • Synthetic URL Testing Improvements
    • Synthetic URL testing now provides more accurate test success and failures during URL redirects by not converting URLs to all lowercase. The system leaves URLs as they are.
    • Synthetic URL testing more accurately marks all response codes with 4xx (starting from 400 to 499) as success when they were previously being reported as failed tests.

Minimum Requirements

Windows

Minimum requirements for Experience Management 25.09 for Windows

  • A Microsoft supported Semi-Annual Channel Windows 11 Version 21H2 or later or Windows 10 Version 20H2 or later
  • Hardware Specifications:
    • 1Ghz processor with minimum of 4 cores
    • 8GB RAM
    • 256GB Hard disk space
  • Omnissa Workspace ONE Intelligent Hub for Windows 24.12 or later
  • Workspace ONE Experience Management for Windows package
  • Omnissa Intelligence tenant opted-in and the Desktop Advanced Telemetry integration card activated

Horizon

Minimum Requirements for Experience Management 2509 for Horizon

  • Use the Experience Management agent for Horizon 2509 on Windows Horizon (single-session or multi-session).
  • Use the Horizon Agent 2503 or later.
  • Use the Horizon Client 2503 or later.
  • Use Horizon Connection Server 2503 or later in Horizon Enterprise deployments.

Resolved Issues

Windows and Horizon

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

Known Issues

Windows

Horizon

  • There is a known issue where the Horizon VM and Session timelines display the CPU and memory trendlines as higher than 100%. This known issue is fixed in the 2412 and later Horizon Agents.
    • Fix: Update your Horizon Agent to the minimum version required for this release.

Download Instructions

Windows and Horizon

Windows

  • Experience Management for Windows is delivered with the Workspace ONE Intelligent Hub for Windows app. Direct users to download the Workspace ONE Intelligent Hub for Windows app from getwsone.

Experience Management 25.03 for Windows and Horizon

Experience Management 25.03 made updates for Windows and had nothing notable to report for Horizon.

What's New

Windows

  • Web App Monitoring is in general availability (GA).
    • IT administrators can use this Experience Management browser extension to monitor web application performance, including page load speeds, network connectivity bottlenecks, and app and browser errors.
    • This extension works with the Experience Management solution to proactively identify issues and to predict them before users notice.
    • IT administrators can also troubleshoot with in-context dashboards and reports to efficiently find the root cause.
    • For details, see Web App Monitoring.

Minimum Requirements

Windows

Minimum requirements for Experience Management 25.03 for Windows

  • A Microsoft supported Semi-Annual Channel Windows 11 Version 21H2 or later or Windows 10 Version 20H2 or later
  • Hardware Specifications:
    • 1Ghz processor with minimum of 4 cores
    • 8GB RAM
    • 256GB Hard disk space
  • Omnissa Workspace ONE Intelligent Hub for Windows 23.10.10 and Omnissa Workspace ONE Intelligent Hub for Windows 24.04.11 or later
  • Workspace ONE Experience Management for Windows package
  • Omnissa Intelligence tenant opted-in and the Desktop Advanced Telemetry integration card activated

Resolved Issues

Windows

  • DCP-9267: Fixed an issue with Hub connector and added a metric for the Hub online status.
  • DCP-9869: Fixed the missing version number that occurred after rebranding.
  • DCP-9876: Fixed an issue with the publishing location of the metadata.json file.
  • DCP-9981: Added a parameter for file size in the metadata.json file.
  • DCP-9989: Changed the metadata name of the Experience Management agent.
  • DCP-10411: Fixed an issue with net events for wireless adapters not getting reported when location services is inactive. For details, see the KB article Windows Location Service Impacts.

Known Issues

Windows

  • We haven't identified any notable known issues in this release. If you have any problems, reach out to our support team.

Download Instructions

Windows

Get Experience Management for Windows in two ways.

Documentation

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 Omnissa AI Features and Integrations.

Support Information

Localized Content for Omnissa Docs

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

Was this page helpful?

Provide feedback for this topic

Was this topic helpful?

Please do not include any personal or confidential information.

Generating link…