Digital Employee Experience Release Notes

Release notes for digital employee experience (DEX) platforms

Get this feed:

Products (12)

Latest Digital Employee Experience Updates

Jul 14, 2026
Date parsed from source:
Jul 14, 2026

First seen by Releasebot:
Jun 30, 2026

Modified by Releasebot:
Jul 15, 2026
ControlUp

9.2.5

ControlUp adds major VDI monitoring and management upgrades, including Omnissa Unified Access Gateway visibility, host GPU and vGPU metrics, rule-driven Windows Event Log Monitoring, Azure Managed Identity support, and new Citrix Cloud Connector, FSLogix, Nutanix, and SBAs enhancements.
Release Date: July 14, 2026

Current Build: 9.2.5.634

Download Links

Console:
https://downloads.controlup.com/console/9.2.5.634/ControlUpConsole_Secure_SIGN-9.2.5.634.zip (opens in new tab)

Agent:
https://downloads.controlup.com/agent/9.2.5.634/ControlUpAgent-net48-x64-9.2.5.634-signed.msi (opens in new tab)

Monitor:
https://downloads.controlup.com/monitor/9.2.5.634/ControlUpMonitor_Secure_SIGN-9.2.5.634.zip (opens in new tab)

New Features

Monitor Omnissa Unified Access Gateway (opens in new tab)

You can now use ControlUp to monitor your Omnissa Unified Access Gateway (UAG) appliances directly, eliminating the need to log into individual gateways or rely on siloed tools to track DMZ health.

UAGs metrics (opens in new tab) display critical data in the Real-Time DX Console and a new cohesive UAGs dashboard in the VDI app.

This feature includes:

Comprehensive Real-Time Metrics: Track availability, session counts, session failures, and hardware resource utilization (CPU, memory, and disk) at a glance.

Historical Data Persistence: Metrics are automatically saved to your historical database with 5-minute, 1-hour, and 1-day aggregations for seamless trend analysis.

Native ControlUp Power: UAG appliances integrate fully with native triggers, Script-Based Actions (SBAs), and RTDX, allowing you to set up proactive alerts and accelerate troubleshooting workflows.

Monitor Host GPUs

ControlUp for VDI now collects host-level metrics for physical NVIDIA GPUs (opens in new tab) and assigned vGPU profiles (opens in new tab). We’ve added new views, widgets, and metrics to monitor the GPUs and vGPUs in your environment.

The new metrics are displayed across the VDI real-time topology in dedicated GPUs and vGPUs views, as well as in new metrics columns on the existing Hosts (opens in new tab) and Machines (opens in new tab) views grids. You can focus on a specific host or machine in the topology view (Details) or organization tree, and drill down directly to individual user sessions utilizing GPU or vGPU resources.

You can also use the new metrics to configure Stress, Scheduled, and Advanced triggers (opens in new tab), as well as Script-based Actions (opens in new tab), to help your organization get ahead of rising GPU costs.

Note that these features are available only for VMWare ESXi.

Monitor Windows Events (opens in new tab)

The legacy Events feature in the Real-Time DX Console is being succeeded by a scalable, rule-driven Windows Event Log Monitoring feature in DEX.

Rather than forwarding all events to the cloud, the ControlUp Agent evaluates Windows events locally against your configured rules, filtering by Log, Provider, Event ID, and Severity Level. The agent then forwards only matching events to the dashboard. This keeps data ingestion volumes and infrastructure costs predictable, while giving your team the flexibility to track any event across your environment.

Key Benefits:

Out-of-the-Box Intelligence: Ships with over 40 default rules organized by a standardized Vendor – Product – Subject naming convention (for example, Citrix - Broker - Registration Failure).

Comprehensive Coverage: Default rules monitor system health, authentication, Group Policy, Windows Update, Windows Defender, and core session lifecycles across RDS, Citrix, Omnissa, AWS, FSLogix/UPM, and Hyper-V/AVD.

Controlled Enablement: To prevent unexpected noise, the default ruleset is enabled automatically for new organizations. Existing organizations can opt in at any time.

Managed Identity for Azure (opens in new tab)

ControlUp for VDI now supports Managed Identity as a built-in alternative to standard Service Principal credentials, allowing you to configure Azure connections securely without providing a Client Secret. You can easily configure connections using either a system-assigned Managed Identity, which requires no additional IDs, or a user-assigned Managed Identity, which simply requires a client ID.

Your selected authorization method is strictly validated during setup, saved directly to the connection configuration, and seamlessly persists across all edit, reload, and update operations. Once configured, this authentication method is consistently utilized by the data collector runtime to ensure secure and uninterrupted data collection.

Azure Availability Zones (opens in new tab)

Availability zones metrics are now displayed for Azure virtual machines and disks in the Real-Time DX Console Machines and the VDI app Machines (Azure) views, providing clearer visibility into resiliency and placement. New metrics include:

AZ Logical Zones

AZ Physical Zones

New Health Metrics for Citrix Cloud Connector (opens in new tab)

From the Real-Time DX Console, you can now view all of your Cloud Connectors from any resource location.

From the VDI app, along with the common ControlUp metrics for any machine, you can view the following metrics specific to Citrix Cloud Connectors:

Cloud Connector Service Status displays the number of active Citrix Cloud Connector services currently running out of the total installed services (e.g., X/13).

Cloud Connector Stopped Service Names lists the specific Citrix Cloud Connector services that are currently stopped or missing.

Cloud Connector Stopped Services displays the total number of Citrix Cloud Connector services currently stopped on this machine.

Cloud Connector Running Services displays the total number of Citrix Cloud Connector services currently running on this machine.

Monitor FSLogix Dirty Bit Flag (opens in new tab)

The Storage > FSLogix Disks view now displays the following FSLogix Dirty Bits Flags metrics:

Dirty Bit Last Checked displays the timestamp for when the dirty bit state was last queried on the endpoint.

Dirty Bit Unknown Reason displays a translation of Win32 error code or context explaining why a definitive result could not be produced.

NTFS Dirty Bit State displays the state of the NTFS dirty bit: N/A, NotMounted / NonNTFS / Unknown, Clean, or Dirty.

Volume GUID Path displays the volume GUID used to perform the dirty bit query. Stored for traceability and troubleshooting.

Shared Credentials for Script-based Actions (opens in new tab)

You can now use Shared Credentials to configure arguments in Script-Based Actions (SBAs), reducing duplication and easing credential management across your organization’s automations.

Nutanix v4 and Prism Support (opens in new tab)

ControlUp has upgraded to the Nutanix v4 API and now supports direct connections to Prism Central, simplifying deployment within your Nutanix environment.

Bug Fixes

Real-Time DX (build 601)

282824: Built-in EUC Sync does not Crop machine Name to 15 characters (if longer than 15) and VDA Connection fails

292702: After upgrading your organization’s ControlUp Monitors, the local configuration cache loads successfully.

308158: Citrix environment EUC connections display data as expected.

310561: The NIC Usage column in the Hosts view displays “N/A” instead of “0” for Nutanix AHV hosts.

Web Interface (build 601)

305031: When you start a Remote Control session on a user device that has multiple monitors, the All Displays selector appears as expected.

306949: After upgrading your organization’s ControlUp Monitors, the Disk I/O Utilization widget doesn’t display an increase greater than expected in the Machine Trends report.

Real-Time DX (build 484)

295547: When you connect to a Citrix session from a Dell ThinOS thin client, the client device name displays correctly in the Sessions view.

275879: When you connect to an AVD session from a Windows App client, the client IP address (oClientIP) displays correctly in the Sessions view.

Original source
July 2026
No date parsed from source.

First seen by Releasebot:
Jul 11, 2026
Nexthink by Nexthink

Nexthink Infinity Standard edition 2026.6

Nexthink releases version 2026.6 of Infinity Standard with broader AI Drive filtering, richer Workspace Assist knowledge sources, new FSLogix insights, expanded Device View performance and activity data, Collector configuration profiles, and limited-view access to Applications insights.
AI Tools: Cascading filters

Navigate organizational data more efficiently with cascading filters in AI Drive. When you select a value in a higher-level organizational filter, related filter options are automatically narrowed while remaining fully accessible, making it easier to explore data across divisions, departments, and teams. This simplifies dashboard navigation, supports broader sharing, and helps you analyze AI adoption more effectively across your organization. Refer to the Monitoring AI adoption documentation for more information.

Workspace ✦: Expanded Assist knowledge sources

Access more relevant insights in Workspace with expanded knowledge sources and richer query capabilities:

Knowledge Base and ITSM insights: Enrich Assist responses with information from your organization's knowledge base articles and ITSM tickets, providing more relevant recommendations and analysis based on your own support content. You can also centrally manage knowledge bases in Administration. This feature requires configuration before use. Please see the Using Workspace and Knowledge Bases documentation for more information.

Support for custom data model fields: Generate context-aware NQL queries that use your organization's dynamic and custom fields, enabling more accurate analysis tailored to your environment. Refer to the Search and Workspace documentation for more information.

💡 Thanks for expressing your interest in this feature on our ideas portal!

These enhancements help Assist deliver more accurate, organization-aware responses and generate queries that better reflect your environment.

Desktop Virtualization: FSLogix insights

Monitor FSLogix container health with detailed insights into mount failures, load times, and storage metrics. You can now see exactly why containers fail to mount, together with usage, footprint, and free space, alongside other logon data. This helps you quickly identify root causes, address storage issues before they escalate, and keep virtual desktop performance reliable. Refer to the Using Session view documentation for more information.

Depending on your current licensing model, this capability may require an additional license. Contact your Nexthink representative for more information.

Device View: Enhanced performance and activity insights

Investigate Windows device behavior more effectively with new insights in Device View:

Application freeze events: Detect significant application freezes directly in Device View. You can now investigate individual freeze incidents with start time, duration, end reason, and process hierarchy, making it easier to identify and troubleshoot user-impacting application freezes. Requires Collector version 26.6 or later.

💡 Thanks for expressing your interest in this feature on our ideas portal!

CPU pressure metrics: Detect CPU throttling and kernel-level activity with new metrics, including CPU frequency ratio, how much processor time drivers consume outside normal applications, plus how long each device spends under heavy driver activity. These insights help distinguish throttling from genuine workload and reveal driver-level CPU activity that is not visible through per-process metrics. Requires Collector 26.5 or later.

GPU and NPU process visibility: Identify which applications are driving high GPU and NPU usage with binary-level insights, helping you correlate resource consumption with specific workloads. Requires Collector version 26.3 or later.

Power transition timeline: View all significant power transitions, including boots, shutdowns, and resumes from sleep states, providing a clearer picture of device activity and making power-related issues easier to interpret.

💡 Thanks for expressing your interest in this feature on our ideas portal!

These enhancements provide a more complete view of device activity and performance, helping you identify issues faster and troubleshoot with greater confidence. Refer to the Timeline and NQL data model documentation for more information.

Collector: Device configuration profiles

Configure and manage Collectors more efficiently with device configuration profiles. You can create and maintain profiles, apply settings consistently across device groups, and simplify Collector configuration management at scale. Refer to the Device configuration profiles documentation for more information.

For guidance on migrating existing Collector deployments to device configuration profiles, refer to the Migrating to Device configuration profiles documentation, available to Nexthink Community users.

💡 Thanks for expressing your interest in this feature and this related enhancement on our ideas portal!

Applications: Overview and adoption for limited view domains

Access Applications Overview and Applications Adoption with limited view domain permissions. You can now monitor application usage and adoption within your assigned scope, with metrics such as employee counts reflecting your view domain permissions. This enables teams with restricted access to benefit from application insights while maintaining appropriate data visibility.

This feature requires configuration or setting user permissions before use. Please see the Monitoring applications and View domain documentation for more information.
Original source
All of your release notes in one feed

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

Create account
Get updates with:
Jul 9, 2026
Date parsed from source:
Jul 9, 2026

First seen by Releasebot:
Jul 11, 2026
Omnissa

Horizon Web Client 2503.2

Omnissa releases Horizon Web Client 2503.2 with enhanced validation checks and workflow improvements for Lifecycle Management operations, improving reliability and user experience as part of the Horizon 8 2503.2 release.
Horizon Web Client 2503.2 | 09 JUL 2025

This page is revised periodically as needed with information about the Horizon Web Client 2503.2, which enables users to connect to and use remote desktops and published applications through a supported web browser. Check back regularly for additions and updates to these release notes.

What’s New

Horizon Web Client 2503.2 is released along with the Horizon 8 2503.2 release. This release includes enhanced validation checks and workflow improvements to Lifecycle Management (LCM) operations, improving reliability and user experience.

The Horizon Web Client 2503.2 release does not contain any Hot Patches that were provided in versions before 2503.2.

Before You Begin

For a list of the supported browsers, supported client operating systems, Web Client system requirements, and installation instructions, see the Horizon Web Client Guide.

Horizon Web Client 2503 supports Horizon Agent 2503.

Horizon Web Client is supported with the latest maintenance release of the following deployment types:

Horizon 8 version 2006 and later

Horizon Cloud Service - next-gen

Horizon Cloud in Microsoft Azure

With Horizon Web Client 2503 and Horizon 8 version 2503, if you connect to a server through a load balancer or a gateway, such as F5 or Unified Access Gateway, you must first configure a security setting in Horizon. For more information, see “Origin Checking” in the Horizon Security guide.

Resolved Issues

There are no major issue resolutions to report in this release.

Known Issues

The following sections describe known issues related to the operation and performance of Horizon Web Client.

For known issues specific to the use of Horizon Web Client in a Horizon Cloud Service - next-gen environment, see the Horizon Cloud Service - next-gen Release Notes.

Audio and Video

Lag in audio-video synchronization
Horizon Web Client might experience a lag in audio-video synchronization. The lag might be due to network conditions, hardware performance, device type, or another cause.
Workaround: None. This issue will be fixed in an upcoming release of Horizon Web Client.

Audio problems when switching media source in iOS Safari
On iOS Safari, if you connect to a remote desktop and play audio or video on the remote desktop, and switch to playing audio or video with a native application without disconnecting from a Connection Server instance, and switch back to the remote desktop on Safari, audio no longer works.
Workaround: Disconnect or log off from the Connection Server instance and connect to the remote desktop again.

Web Audio API support is required for optimal sound quality
Sound playback quality is best on browsers that have Web Audio API support. Chrome, Safari, and Firefox 25 and later browsers have Web Audio API support. Browsers that do not have this support include Firefox 24 and earlier.
Workaround: None

Audio processing becomes intermittent
On Chrome, Safari, and Edge browsers, if audio is playing and you switch to another tab in the browser or minimize the browser, audio processing becomes intermittent. After you re-focus on the remote desktop tab, audio might be out of sync with video for a few seconds.
Workaround: Refresh the page or pull the remote desktop’s tab out of the browser so that it has its own window.

Problems with repeat redirection in macOS Chrome
Occasionally, Real-Time Audio-Video (RTAV) video redirection does not work when you use it for a second time with Chrome on a macOS system.
Workaround: Refresh the browser.

Problems when exiting multiple-monitor mode
The Web browser from which you start a desktop might stop responding if you repeat the following steps multiple times: enter multiple-monitor mode, open Real-Time Audio-Video (RTAV), move the camera window to the second display, exit multiple-monitor mode, or start another remote desktop from the sidebar.
Workaround: None.

Problems when unplugging extended monitor
The sidebar, and sometimes the remote desktop, disappears after you unplug the extended display monitor while using the multiple monitor feature with a Chrome Web browser.
Workaround: Restart HTML Access, resize the application window, or re-plug the extended display monitor.

Warning message in Safari 12
In Safari 12, the first time you open a remote desktop or published application, a warning message instructs you to enable audio. This warning message appears again after you log out from the server, close or refresh the browser, and open a remote desktop or published application.
Workaround: None.

Teams Media Optimization becomes unavailable after a network interruption
The Media Optimization for Microsoft Teams feature is unavailable after a network interruption occurs on the client session. For details, see the Omnissa Knowledge Base (KB).
Workaround: None.

Browsers

Empty sessions when using Chrome
When using Chrome version 67 or later, you might receive an empty session after you start a remote desktop, enter multiple-monitor mode, move the mouse pointer to the second display monitor, and exit multiple-monitor mode.
Workaround: Manually resize the Chrome window or refresh the page.

Problems with Linkclump Chrome extension and right-click behavior
The Linkclump Chrome extension interferes with proper right-click behavior. If you right-click text in a remote desktop, the right-click might behave as a left-click-and-drag action.
Workaround: Disable the extension, or go into the Chrome Linkclump Options page and enter the address of the Connection Server instance in the Blocklist section.

Problems when using Chrome browser
When you use HTML Access in a Chrome browser, you might encounter the following problems:

Occasionally, when connecting to a remote desktop or published application after the session has timed out, a “Failed to connect the Connection Server” error message appears.

A session is not opened when you connect to a powered off desktop.
Both problems have the same root cause, which is a third-party issue.
Workaround: For the first problem, dismiss the error message and reconnect to the remote desktop or published application. For the second problem, reload the browser or reconnect to the remote desktop.

Connectivity

Desktop sessions are disconnected in Firefox
When using a Firefox browser, your Horizon Web Client remote desktop session is disconnected immediately after connecting.
Workaround: Verify that your Firefox browser proxy settings are configured correctly.

Suspension of remote desktops does not work
Do not configure remote desktops to be suspended after users disconnect. This setting does not work correctly with HTML Access.
Workaround: None

Blast Secure Gateway causes failed connection to remote desktop or published application
Connecting to a remote desktop or published application fails if Blast Secure Gateway (BSG) is enabled on both the Unified Access Gateway server and the Connection Server instance.
Workaround: Disable BSG on the Connection Server instance.

Problems when Enable Blast is set to False in Unified Access Gateway
In Unified Access Gateway, if you set the Enable Blast Horizon Edge setting to False, you cannot access remote desktops and published applications through Horizon Web Client. Generally, because Unified Access Gateway is deployed in a DMZ, the Enable Blast option is set to True and this issue does not occur.
Workaround: In Unified Access Gateway, if you set Enable Blast to False and also use Horizon Web Client, set the proxyPattern option to "/|/portal(.*)".

Unified Access Gateway server session timeout is not recognized
If you access a remote desktop or published application through HTML Access that is connected with a Unified Access Gateway server, the remote desktop or published application session is not disconnected after the Unified Access Gateway server session timeout is reached.
Workaround: None.

Security

Problems with RDS Per Device Client Access Licenses
Do not use RDS Per Device Client Access Licenses (CALs) for Horizon Web Client. If you do, the licensing mechanism treats each browser as a device, and, if cookies are cleared, the browser uses another license.
Workaround: Use RDS Per User CALs for HTML Access.

Unified Access Gateway server self-signed certificate does not work on Chromebook
On a Chromebook, when connecting to a Unified Access Gateway server that uses a self-signed certificate, HTML Access reports the error ERR_CERT_INVALID.
Workaround: Install a CA-signed certificate on the Unified Access Gateway server.

Self-signed certificates are not supported on iOS
On iOS, if you attempt to connect to a remote desktop by using a self-signed certificate, Safari reports the error “Your desktop has been disconnected. Unable to reconnect to desktop.” This problem occurs because self-signed certificates are not supported on iOS.
Workaround: An administrator must install a CA-signed certificate on the Connection Server, and you must trust the certificate on your iOS device. For information about installing certificates on Connection Server, see the Horizon 8 Administration guide. For information about trusting certificates on an iOS device, see the Horizon HTML Access Guide. If the Blast Secure Gateway is disabled on the Connection Server, an administrator must perform the following additional steps on the remote desktop to connect from iOS:

Use mmc to import the CA-signed certificate into the Windows certificate store.

Replace the sslHash key in HKEY_LOCAL_MACHINE\SOFTWARE\Omnissa\Horizon Blast\Config with the key from the thumbprint of the certificate issued to the Blast Agent Hostname or IP address.

Restart the Blast Agent virtual machine.

Cached credentials fail to clear
When the Clean up credential when tab closed for HTML Access global setting is enabled in Horizon, the cache is not cleared if a user closes a tab when the network connection is not available.
Workaround: None.

Application fails to restart automatically after password change
After an administrator sets the change password at next logon option for a user’s account, and the user’s idle session times out, the application that was active during the session timeout is not restarted automatically after the user reauthenticates and changes the password successfully.
Workaround: Refresh the page and launch the application again from the sidebar.

Problems with intermediate CA-signed certificates in iOS
Remote desktops and published applications cannot be started successfully from an iOS device if the iOS device uses an intermediate CA-signed certificate.
Workaround: Install a root CA-signed certificate on the iOS device.

Problems with Unified Access Gateway self-signed certificate and Microsoft Edge
If you use a self-signed certificate with Unified Access Gateway, you might not be able to access a remote desktop when you use a Microsoft Edge Web browser for the HTML Access session.
Workaround: Use one of the following workarounds to resolve this issue.

Use a valid CA-signed certificate.

Do not use port 8443 for the Blast External URL property. Use port 443 instead.

Remote desktop connection fails with Microsoft Edge
If you configured Unified Access Gateway with a root certificate that is signed by a Certificate Authority (CA), and the Blast External URL property value is set to blank or to port 8443, you might not be able to connect to a remote desktop if you are using a Microsoft Edge browser. After the error occurs, all new connected sessions are not visible.
Workaround: Use one of the following workarounds to resolve the issue.

Set the Blast External URL property to port 443.

Close the Microsoft Edge browser, restart the HTML Access, and connect to the remote desktop.

Miscellaneous

ARM CPUs are not supported
HTML Access is not supported on client systems running on ARM-based CPUs, such as:

Mac system with M1 or M2 chips

Windows system with ARM-based CPU
An incompatibility warning appears if you attempt to use HTML Access from such a client system. Bypassing this warning is not recommended.
Workaround: Install and use a native client instead. URI launch from native clients is supported on systems with ARM-based CPUs.

Japanese keyboard mapping is incorrect
When you connect to a Linux desktop with the Japanese keyboard, the keyboard mapping might be incorrect. For example, the key positions | and _ will be incorrect.
Workaround: Keep the client input language as Japanese and switch the desktop input language to English for the two key positions | and _ only. Keep the desktop input language as Japanese and switch the client input language to English for all other key positions.

Keyboard input does not work in Linux desktop sessions
When connecting to a Linux desktop, some keyboard input does not work. For example:

The * key on the numeric keypad is displayed as 8.

English keyboard: the + key on the numeric keypad is displayed as =.

Non-English IME on both client and desktop: some non-English keys are not displayed correctly.
Workaround: For issues 1 and 2, use the typewriter keys * and + in the main keyboard area instead of the numeric keypad. For issue 3, set English IME in HTML Access and non-English IME on the remote desktop.

Autofit of published applications does not work
Intermittently, autofit of a published application does not work. This problem can happen if you start a published application and activate full-screen mode for the browser, start a published application from the sidebar and activate full-screen mode, or start a published application and enlarge the size of the browser window.
Workaround: Activate full-screen mode or resize the browser window before starting a published application.

Locked desktop session still allows file upload
Users can still upload files when the remote desktop is locked.
Workaround: None.

Problems with clipboard format restrictions
When an administrator enables a clipboard format restriction, the text in the Copy & Paste window does not describe the format limitation. For example, if an administrator enables the “Filter text out of the incoming clipboard data” clipboard policy setting, the Copy & Paste window does not notify the user that text cannot be transferred from the client to the remote desktop or application.
Workaround: None.

Double mouse cursors in multiple-monitor mode
In multiple-monitor mode, two mouse cursors appear when you click inside a remote desktop or published application session.
Workaround: None.

Scroll bars are hidden when using Session Collaboration on macOS
When you use a Web browser on a macOS 10.13 system in a Session Collaboration collaborative session, if Fit to Viewer is disabled and the collaborative session’s screen resolution is less than the primary session’s screen resolution, a scroll bar does not appear. This issue occurs because scroll bars are hidden by default in macOS 10.13 systems.
Workaround: Modify the System Preferences to always display scroll bars.

Choose Apple menu > System Preferences.

Click General.

In the Show scroll bars section, select Always.

Problems with H.254 decoding in Chrome
When the Allow H.264 decoding option is enabled, a newly started published application fails to open and the remote session shows a black screen.
Workaround: Resize the Chrome browser.

Problems when using software keyboard
When you start HTML Access from a Chrome Web browser on an Android 8.1 device, or from a Safari Web browser on an iOS 11 device, the remote desktop window sometimes disappears while you are using the software keyboard in a remote session. This issue often occurs when you are rotating the device and then closing and reopening the software keyboard. After the error has occurred, all subsequent remote desktop sessions opened are not visible.
Workaround: Reload the Web browser page.

Smart Policy changes fail to take effect upon reconnecting to session
Smart Policy changes do not take effect immediately after reconnecting to a remote desktop. After you change the Smart Policy Clipboard and File Transfer from Allow all to Disable, the functions are deactivated, but the text for the Copy & Paste window shows the incorrect text. Also, if you are connected to a remote desktop from an HTML Access session when the Smart Policy Clipboard and File Transfer setting is changed and you disconnect, the changes do not take affect after you reconnect to the remote desktop.
Workaround: Log off from the remote desktop and reconnect to the remote desktop, then disconnect from the remote desktop and reconnect to the remote desktop again.

Problems when switching between sessions with H.264 decoding
When H.264 decoding is enabled, if you use the sidebar to switch between remote desktops, or between remote desktops and published applications, the remote sessions become unresponsive. The remote sessions are still connected, but mouse clicks and other actions do not work.
Workaround: Close and reconnect to the remote desktop or published application sessions.

Documentation

Horizon HTML Access documentation is in the Omnissa Information Hub.

Localized Content for Omnissa Docs

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

Support Contact Information

To receive support and to learn more about support policies, see Omnissa Customer Connect.

For information on filing a support request in Customer Connect and through the Cloud Services Portal, see the Omnissa knowledge base article at https://kb.omnissa.com/s/article/2006985.
Original source
Jul 9, 2026
Date parsed from source:
Jul 9, 2026

First seen by Releasebot:
Jul 11, 2026
Omnissa

Omnissa Horizon 8 2503.2

Omnissa releases Horizon 8 2503.2 ESB with stronger Lifecycle Management validation and workflow improvements, a full transition to Omnissa licensing, removal of the VMware license modules and subscription grace period, plus updated Helpdesk entitlement and Imprivata compatibility.
Upgrading Changes

For upgrades to Horizon 8 2503.2, review these important considerations:

If you are running 2312.2 or a later version of 2312.x, please do not upgrade to 2503. Your upgrade path will be the follow-on maintenance version of 2503, i.e. 2503.2.

Beginning with the Horizon 8 2412 release, there is a new licensing module for term and perpetual licenses. Review the License Activation section in these release notes for details.

It is very important for you to thoroughly review KB 6000681 before starting your Connection Server upgrade. To ensure compatibility with existing system components, third-party integrations, and automated workflows, follow the recommendations outlined in that KB 6000681, and in Upgrading to Omnissa Horizon 8 2412 and Later.

Omnissa recommends that you validate the upgrade in a UAT environment before deploying it to your production environment.

Important Notes

Horizon 8 2503.2 is not supported with vSphere 6.5 or vSphere 6.7, which are both past the end of General Support. Horizon 8 2503.2 Instant Clones are incompatible with vSphere 6.5 and vSphere 6.7 so you must upgrade to vSphere 7.0 or later before upgrading to Horizon 8 2503.2 if you are using Instant Clones.

Microsoft security update (KB 5014754) will impact customers using certificate-based authentication to Horizon 8, such as smartcard authentication. Horizon 8 True SSO is not impacted by this security update. If you have applied this update to your Windows Domain Controllers but have not mapped certificates to one of the strong mapping types described in the Microsoft KB, then users will be denied authentication after Full Enforcement mode is activated by Microsoft in a future Windows Update. See the above KB for further details, including the expected Full Enforcement mode date. To address this issue, Horizon 8 2309 introduced the ability for administrators to configure strong certificate mappings from the Horizon console. If you are using certificate-based authentication, upgrade to Horizon 8 2309 or later in order to configure certificate mappings. See KB 91595 for details.

Horizon Agent no longer supports Windows Server 2012 R2 within a guest OS whether it be for new or existing deployments. Also starting with Horizon 8 2312, the use of Windows Server 2012 R2 is no longer supported for Horizon Connection Server and Horizon Enrollment Server deployments. Please use Windows Server 2016 or later. See https://learn.microsoft.com/en-us/lifecycle/announcements/windows-server-2012-r2-end-of-support for details.

Microsoft released security updates KB5008383 and KB5020276. While Omnissa has determined that KB5008383 does not impact Horizon Full Clones and Instant Clones, KB 5020276 does if you have selected “Allow Reuse of Existing Computer Accounts”. See KB 92214 for details.

What’s New

Horizon 8 version 2503.2 is an Extended Service Branch (ESB). This release includes enhanced validation checks and workflow improvements to Lifecycle Management (LCM) operations, improving reliability and user experience.

License Activation

To comply with the Broadcom divestiture agreement, all VMware (Broadcom) license modules will be removed from the Horizon Connection Server in this release. The system will fully transition to Omnissa License Module support, simplifying licensing and ensuring compliance. Updates will span LDAP, server code, license files, and the cart module.

The 15-day grace period for subscription licenses has been removed. If you activate a subscription license in Horizon 8 without Horizon Edge, you must reactivate it every 90 days to maintain full functionality. However, licenses will be automatically activated if you are using Horizon Edge.

The Licensing and Usage screen in Horizon Console includes a field for the Subscription End Date. When data becomes available from the Horizon Control Plane, this field will display the end date of the subscription license. Otherwise, this field will display “N/A”.

Horizon Connection Server

We’ve updated the feature comparison sheet to reflect an expansion of the Helpdesk feature entitlement. It is now included in the following SKUs: Horizon for Linux, Horizon Standard, Horizon Advanced, Horizon Apps Standard, and Horizon Apps Enterprise. Previously, this feature was limited to Horizon Enterprise and Horizon Apps Enterprise SKUs. You can view the updated comparison sheet here: Horizon Subscription Term Editions. Based on this update, we have made the necessary changes to enable the Helpdesk feature for all term licenses associated with the above-mentioned SKUs starting from the 2506 and 2503.1 ESB releases. For version 2503 and earlier, the Helpdesk feature remains available only for Horizon Enterprise and Horizon Apps Advanced term licenses, and not for other SKUs.

Horizon 8 2503.2 is supported with Imprivata Enterprise Access Management 25.2. This release resolves an issue with Imprivata compatibility.

Horizon 8 API

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

Horizon Edge and Horizon Cloud Connector

Applicable to customers with Horizon Universal Subscription, Horizon Enterprise Plus Subscription, Horizon Standard Plus Subscription, Horizon Apps Universal Subscription, or Horizon Apps Standard Subscription.

The Horizon Edge is a required component for connecting Horizon 8 to Horizon Control Plane next-gen for subscription licensing enablement and additional control plane SaaS services.

The Horizon Cloud Connector virtual appliance is a required component for connecting Horizon 8 to the first-gen Horizon Control Plane for subscription licensing enablement and additional control plane services.

Horizon 8 Deployed on Public Cloud SDDCs

For a list of Horizon 8 features supported on Azure Omnissa Solution (AVS), see KB 80850.

For a list of Horizon 8 features supported on VMware Cloud on AWS, see KB 58539.

For a list of Horizon 8 features supported on Google Cloud VMware Engine (GCVE), see KB 81922.

For a list of Horizon 8 features supported on Oracle Cloud Omnissa Solution, see KB 88202.

For a list of Horizon 8 features supported on Alibaba Cloud Omnissa Service (ACVS), see KB 92140.

Before You Begin

You cannot mix IPv4 and IPv6 pods in a single CPA federation. They have to all be IPv4 or IPv6.

Microsoft Internet Explorer is no longer supported for Omnissa Horizon Console from Horizon 2111 onward. As Horizon Console is migrating to clarity widgets which do not support Internet Explorer, we have removed Internet Explorer from the list of supported browsers for Horizon Console.

The Horizon Virtualization Pack for Skype for Business is no longer supported in this release. When using this release of Horizon Client with Horizon Agent 2212 or earlier, the Virtualization Pack for Skype for Business will continue to run in fallback mode.

Important note about installing VMware Tools: If you plan to install a version of VMware Tools downloaded from the product downloads page, rather than the default version provided with vSphere, make sure that the VMware Tools version is supported. To determine which VMware Tools versions are supported, go to the Omnissa Product Interoperability Matrix. (Supported versions: 11.1.0, 11.0.6, 10.3.22, 10.3.21). There are also performance issues with the 11.x versions of VMware Tools. For more information, see KB 78434.

Downgrading Connection Server instances is not supported. To revert to a previous version after an upgrade, restore from backup. For more information, see Create a Replicated Group After Reverting Connection Server to a Snapshot.

It is possible that the ordering of cipher suites can be enforced by Connection Server. For more information, see Horizon Security.

Connection Server must be able to communicate on port 32111 with other Connection Servers in the same pod. If this traffic is blocked during installation or upgrade, installation will not succeed.

TLS handshakes on port 443 must complete within 10 seconds, or within 100 seconds if smart card authentication is enabled. In previous releases of Horizon, TLS handshakes on port 443 were allowed 100 seconds to complete in all situations. You can adjust the time for TLS handshakes on port 443 by setting the configuration property handshakeLifetime. Optionally, the client that is responsible for an over-running TLS handshake can be automatically added to a blacklist. New connections from blacklisted clients are delayed for a configurable period before being processed so that connections from other clients take priority. You can enable this feature by setting the configuration property secureHandshakeDelay. For more information about setting configuration properties, see Horizon Security.

When you deploy an instant clone as a RDS host, do not reboot the RDS host directly from within the Windows Server OS. Instead, refresh the instant clone VM using the push image workflow.

In Horizon 8, internal validation checks determine if the instant clone and internal template have valid IP addresses and a network connection. If a virtual machine has a NIC that cannot be assigned an IP address during provisioning, instant-clone provisioning fails.

The forwarding rules for HTTP requests received by Connection Server instances have changed at this release. If you have defined custom frontMapping entries in locked.properties, you should remove them before upgrading. If you wish to disallow administrator connections to certain Connection Server instances, then instead of defining custom frontMapping entries, add this entry to locked.properties:

frontServiceWhitelist = tunnel|ajp:broker|ajp:portal|ajp:misc|moved:*|file:docroot

In Horizon 8, the HorizonDbChk tool will not have access to vCenter credentials and will prompt for this information when needed.

Microsoft Windows Server requires a dynamic range of ports to be open between all Connection Servers in the Horizon 8 environment. These ports are required by Microsoft Windows for the normal operation of Remote Procedure Call (RPC) and Active Directory replication. For more information about the dynamic range of ports, see the Microsoft Windows Server documentation.

Screen DMA is disabled by default in virtual machines that are created in vSphere 6.0 and later. Horizon 8 requires screen DMA to be enabled. If screen DMA is disabled, users see a black screen when they connect to the remote desktop. When Horizon 8 provisions a desktop pool, it automatically enables screen DMA for all vCenter Server-managed virtual machines in the pool. However, if Horizon Agent is installed in a virtual machine in unmanaged mode (VDM_VC_MANAGED_AGENT=0), screen DMA is not enabled. For information about manually enabling screen DMA, see KB 2144475.

To use View Storage Accelerator in a vSphere environment, a desktop virtual machine must be 512GB or smaller. View Storage Accelerator is disabled on virtual machines that are larger than 512GB. Virtual machine size is defined by the total VMDK capacity. For example, one VMDK file might be 512GB or a set of VMDK files might total 512GB. This requirement also applies to virtual machines that were created in an earlier vSphere release and upgraded to vSphere 5.5.

The Global Policy, Multimedia redirection (MMR), defaults to Deny. To use MMR, you must open Horizon Console, edit Global Policies, and explicitly set this value to Allow. To control access to MMR, you can enable or disable the Multimedia redirection (MMR) policy globally or for an individual pool or user. Multimedia Redirection (MMR) data is sent across the network without application-based encryption and might contain sensitive data, depending on the content being redirected. To ensure that this data cannot be monitored on the network, use MMR only on a secure network.

The USB Redirection setup option in the Horizon Agent installer is deselected by default. You must select this option to install the USB redirection feature. For guidance on using USB redirection securely, see Deploying USB Devices in a Secure Horizon Environment.

For information on security considerations and disallowing inter-virtual machine transparent page sharing, see KB 2080735.

If a PCoIP Secure Gateway (PSG) has been deployed for PCoIP connections, zero client firmware must be version 4.0 or later.

RC4, SSLv3, TLSv1.0 and TLSv1.1 are disabled by default in Horizon 8 components, in accordance with RFC 7465, “Prohibiting RC4 Cipher Suites,” RFC 7568, “Deprecating Secure Sockets Layer Version 3.0,” PCI-DSS 3.1, “Payment Card Industry (PCI) Data Security Standard”, and SP800-52r1, “Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations.” If you need to re-enable RC4, SSLv3, TLSv1.0 or TLSv1.1 on a Connection Server or Horizon Agent machine, see Older Protocols and Ciphers Deactivated in Horizon.

Horizon 8 uses version m86 of Microsoft WebRTC source code.

For best practices on using Carbon Black with Horizon 8, see KB 95512.

Horizon 8 supports vSAN 8 Express Storage Architecture (ESA) for both full and instant clones. For more information on vSAN 8 ESA, see https://techzone.omnissa.com.

Horizon 8 supports a maximum of 500 virtual machines per ESXi host when using vSAN 8 ESA datastore. The achievable maximum depends on the workload and specifics of the hardware. For information on all Horizon configuration maximums, see VMware Configuration Maximums.

Cross-origin resource sharing is enabled by default. If you experience connection issues from Horizon Web Client, you might need to add the connection URL to the known origins list. For more information, see KB 85801.

Upgrade

Check the Omnissa Product Interoperability Matrix before upgrading your Horizon deployment. Note the following guidance:

You can only upgrade to a version with a release date later than your current deployment.

When upgrading from a non-ESB version to an ESB version, the target ESB version must be later than your current non-ESB release. For example, you cannot upgrade from Horizon 8 2203 (non-ESB) to Horizon 8 2111.1 (ESB) even though 2111.1 was released after 2203 (or you will lose features). You can only upgrade to Horizon 8 2212 or later versions.

Important: Please allow for extra time and preparation when you upgrade from a VMware-branded Horizon version to an Omnissa-branded Horizon version. For more details, see KB 6000681 and Upgrading to Omnissa Horizon 8 2412 and Later.

Compatibility Notes

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

Resolved Issues

There are no major bug fixes in this release to report.

Known Issues

The numbers included before the known issues refer to the issues logged in the Omnissa internal issue tracking system.

Before upgrading to this release, please review the information in KB 6000681 and Upgrading to Omnissa Horizon 8 2412 and Later.

[The release notes continue with detailed known issues, workarounds, and additional technical information for various components such as Horizon Connection Server, Horizon Cloud Connector, Horizon Recording, Horizon Agent for Linux, Horizon Agent for Windows, Horizon Client, Windows OS Optimization Tool, APIs, On-Premises Environments, Use of Open Source, Documentation, Localized Content for Omnissa Docs, and Support Contact Information.]
Original source
July 2026
No date parsed from source.

First seen by Releasebot:
Jul 7, 2026
BigFix Enterprise Suite by HCL Software

BigFix Enterprise Suite Download Center 10.0.16

BigFix Enterprise Suite ships a release page for platform, server, relay, agent, console, and utility downloads.
General

What’s New in this release

Documentation in HCL Help Center

Technical Changelist

Download

SHA1SUMS

SHA256SUMS

GPG RPM Public Key

Installation Generator

Server

Platform API

Relay

Agent

Console

Utilities

QnA/Fixlet Debugger

RESTAPI Command-line interface (CLI)

Airgap Tool

BESRemove

BES Client Compliance SDK

BES xsd

BESAPI xsd

Versions

External Libraries

Library Version
OpenSSL 1.0.2zq
libcURL 8.17.0
Microsoft VC++ Redistributable 2012, 2015-2022

Internal

Name Version
DBINFO Enterprise 10.97

BigFix Support

Contact Support

© Copyright HCL 2019
Original source
Jul 6, 2026
Date parsed from source:
Jul 6, 2026

First seen by Releasebot:
Jul 7, 2026
HP Workforce Experience Platform by HP

Straight to Support: Use Remote Connect to Resolve Device Issues Faster

HP Workforce Experience Platform adds Remote Connect, bringing secure remote access and device analytics together for faster issue resolution. It supports in-band control and OS-down recovery, includes multi-vendor support, and helps IT teams reduce downtime, cost, and tool switching.

Remote Connect offers secure remote access directly from WXP with device analytics at hand, saving the hassle and cost of third-party tools for issue resolution.

We’ve consistently pointed out the limitations of reactive IT–even going so far as to call it ticket addiction. That said, incident management still forms a large part of IT teams’ responsibilities. In fact, our own research showed that 70% of enterprise IT organizations reported spending at least 40% of their time on reactive issue resolution.

Part of the reason for this time sink is systematic inefficiency. Helpdesk technicians are often siloed and don’t have the insight they need to diagnose issues reliably. Even when they do have the information available, fleet management and support tools may reside in different platforms and provide no holistic view of device health without switching screens, slowing time to resolution.

The device health analytics within the HP Workforce Experience Platform (WXP)¹ can help detect device issues before they escalate and disrupt employee productivity. AI-powered remediation prioritization can quickly surface relevant, recommended interventions to prevent escalation. And now, with Remote Connect,² you can directly intervene and minimize downtime in responding to an active issue or trying to prevent one.

With a unique ability to handle both in-band support and OS-down recovery for critical system failures, Remote Connect enables IT teams to securely connect to and control an employee’s PC directly from WXP, with all the device data and analytics at their fingertips to provide the context for quick remediation. It offers multi-vendor support and can cover a full range of use cases, saving the cost of using a third-party remote support tool.

Put All Your Tools in the Same Toolbox

Helpdesk tickets frequently lack detail and context. People don’t always remember exactly what they were doing before the issue popped up, or they don’t know what information is relevant to solving their problem, so relying entirely on end-user reporting for remediation can prove frustrating.

This is where WXP shines, providing deep information about device health, including details about system changes, memory usage, application hangs, and blue screens leading up to the incident that may provide clues toward resolution.

Remote Connect enables an IT administrator to initiate a remote desktop control session directly from WXP to fix a problem. It provides the administrator with control of the keyboard and cursor, allowing them to navigate and control the desktop and settings to troubleshoot a machine on the fly using the device analytics WXP provides. With both in-band and out-of-band capabilities, IT teams gain a comprehensive solution that can save troubleshooting time as well as avoid the need to ship replacement devices or travel to the employee’s location.

In-band Remote Connect provides high-fidelity, remote access over a secure, encrypted display stream. This WXP feature provides a secure, efficient solution for IT interventions and eliminates the need to pivot to another tool, saving time, energy, and expense.

In more complex situations where the device is failing to boot, experiencing repeated blue screens, or requires interventions below the OS, such as firmware or BIOS updates, Remote Connect leverages Intel vPro Out-of-Band AMT Technology with full KVM control to remotely power cycle, diagnose, update, reboot, and reset devices. IT teams can switch easily between in-band and out-of-band support modes to quickly achieve issue resolution, all from within WXP.

Out-of-band Remote Connect is available for use with any Intel vPro enterprise AMT-enabled device, including Retail Point-of-Sale (RPOS) systems, making it extremely valuable in situations where even minutes of downtime can directly impact the bottom line.

Instill Trust in Employees and Clients

Importantly, employees remain firmly in control throughout the support process: explicit permission is required for access, confirmed through a secure token or passkey, and the technician handling their request is identified by name. Employees may terminate a session at any time, providing an extra layer of transparency and trust. These safeguards ensure that while IT teams deliver responsive and effective support, employee autonomy and privacy are always respected.

Additionally, combined with WXP’s ability to flag issues before they become device failures, IT service providers have an opportunity to proactively reach out and remedy potential issues remotely, preventing downtime, proving value, and building trust with clients.

Confidently close the loop in your workflow as well, from within WXP. After an issue is addressed with a Remote Connect session, you can use WXP to manually or automatically send the employee a follow-up survey, validating that the resolution has stuck and the employee is happy with their digital experience. Over time, this reduces recurring problems and contributes to employee satisfaction with their technology environment.

Learn more in the demo video below.

Learn More about Remote Connect and WXP

Remote Connect is included with Pro and Elite WXP plans, available as an add-on purchase for WXP Standard plans, or can be purchased as a standalone service for those who only require the connectivity functionality and want to integrate it with existing support tools. To learn more, or to discuss upgrading your WXP plan to include Remote Connect, contact your HP account manager or partner.

For HP partners and managed service providers, Remote Connect represents a significant step forward in service delivery and customer satisfaction. By streamlining the process of resolving IT issues, it enables tickets to be addressed with greater speed and efficiency, reducing downtime and ensuring a seamless user experience, while reducing costs and complexity for IT staff. For information about how partners can incorporate Remote Connect into their service offering, contact your HP account manager or complete the form below to set up a meeting.

Additional Resources

Knowledge Base | Remote Connect

¹ The Workforce Experience Platform (WXP) is available in various tiers and for multiple term license durations, and some features require optional add-on solutions. WXP is for commercial customers and some features and capabilities may require additional purchase of HP services and/or commercial hardware capable of supporting the HP Insights agent for Windows, Mac, & Android. WXP is ISO27001, ISO27701, ISO27017 and SOC2 Type2 certified for Information Security. Activation and restrictions may apply. Select HP solutions require an HP Insights agent for Windows, Mac, & Android, available for download at https://workforceexperience.hp.com/software. For full system requirements and services that require the agent, please visit https://workforceexperience.hp.com/requirements. The agent collects telemetry and analytics around devices and applications that integrate into the Workforce Experience Platform. Internet access required. WXP Collaboration license required for audio and video collaboration technology monitoring. HP Anyware license or compatible third-party virtual machine license required for virtual machine monitoring. WXP Print Management capabilities are available to select beta customers in the US only. WXP Print Management is planned to be available in a future release in various tiers as an add-on solution in various term licenses.

² HP Remote Connect is available as a license in varying term lengths and is vendor agnostic for supported PCs. Certain capabilities, including out of band remote access, require Intel® vPro® Enterprise hardware with Intel® Active Management Technology (AMT) enabled. HP Remote Connect is delivered through and administered by the HP Workforce Experience Platform (WXP). WXP Starter is included and required to administer the service. WXP is also available in various tiers and for multiple term license durations, and some features require optional add-on solutions. WXP is for commercial customers and some features and capabilities may require additional purchase of HP services and/or commercial hardware capable of supporting the HP Insights agent for Windows, Mac, & Android. WXP is ISO27001, ISO27701, ISO27017 and SOC2 Type2 certified for Information Security. Activation and restrictions may apply. Select HP solutions require an HP Insights agent for Windows, Mac, & Android, available for download at https://workforceexperience.hp.com/software. For full system requirements and services that require the agent, please visit https://workforceexperience.hp.com/requirements. The agent collects telemetry and analytics around devices and applications that integrate into the Workforce Experience Platform. Internet access required.
Original source
July 2026
No date parsed from source.

First seen by Releasebot:
Jul 4, 2026
1E

TeamViewer DEX 26.7 release notes

1E releases Platform, Solutions and Client updates with Tia Reporting Liveboards, single-device approval bypass for operational safeguards, device detail user info improvements, and a series of DEX Platform and Client fixes that improve reporting, stability, security, and usability.
Tia Reporting Liveboards

This release includes enhancements and fixes for the Platform, Solutions, and Client.

Tia Reporting Liveboards allow users to organize multiple reports into interactive dashboards for ongoing analysis and visibility. Liveboards make it easy to bring related reports together in a single view, helping users monitor trends, investigate issues, and revisit important insights over time.

Creating and using Liveboards

Liveboards are created directly from within a report to provide a more intuitive and guided reporting experience.

After generating a report with Tia Reporting, you can add that report to a new or existing Liveboard, allowing related reports and visualizations to be organized into a centralized dashboard. This workflow helps you move seamlessly from asking questions and generating insights to building reusable reporting views.

Once created, Liveboards provide an interactive dashboard experience where you can view and explore multiple reports in one place, making it easier to track digital experience trends and investigate areas of interest over time.

Liveboards support reports built on any available reporting data model. At this time, the Experience data model remains the only model available for reporting. Additional data models will be introduced in upcoming releases, expanding reporting and dashboarding capabilities across the platform over time.

New Liveboards must be created from within a Report. To create a Liveboard, first generate a report using Tia Reporting, then add the report to a new or existing Liveboard.

Operational safeguards: Instruction approval bypass for single devices

Operational safeguards provide organizations with an approval mechanism to mitigate unexpected behaviour during instruction execution. However, we have heard from multiple customers that in cases of single device investigation, the approval process can delay ticket resolution and cause frustration for service desk teams.

To address this, we have introduced an option (within security settings) to bypass instruction approvals when only a single device is targeted. As detailed in the settings text, adding scope via a device filter will still go through the standard approval process.

When an approval has been bypassed, it will be recorded in the audit logs as shown in the example below.

Primary user and last logged in user information

Within the activity sub-section of the specific device detail page, information on the Last Logged in User has been added. What was previously referred to as User has also been updated to Primary User on this device details page. These updates are available on the new UI only.

Other improvements and fixes

Enhancement - DEX Platform - PLAT-28198: Device Insights now uses normalized data. The individual device insights page has been updated to use normalized insights data, providing more accurate and consistent device-level analytics.

Fix - DEX Platform - PLAT-30041: We fixed an issue where, when selecting a device under Inventory Insights, the Connectivity section did not correctly display the Connection state and MAC address. This information now matches the data shown in Device Pillars.

Fix - DEX Platform - PLAT-30438: We fixed an issue with missing scrollbars on the License Information advanced view. Horizontal and vertical scrollbars now appear correctly on the License Information advanced view page, ensuring all product features and details are fully visible.

Enhancement - DEX Platform - PLAT-29393: Table-level actions such as Refresh and Export now use standardised icon buttons instead of text buttons across all pages using the new UI stack. Icons are logically grouped, with tooltips on hover for accessibility, and the layout is optimized for both desktop and mobile viewports.

Enhancement - DEX Platform - PLAT-30189: The User Engagements page now supports searching and filtering by additional columns including survey type, description, notes, link, created by, priority, status, and deadline. Results are also now sorted newest first by default, improving discoverability of surveys.

Fix - DEX Platform - PLAT-30029: We fixed an issue where the Exoprise iframe failed to load when the configured URL contained an SSO path. The iframe URL is now correctly derived by extracting the origin from the Exoprise URL and appending the expected iframe path, ensuring the integration loads reliably regardless of the URL format stored in the license configuration.

Fix - Client - PLAT-29191: We fixed an issue that could allow local privilege escalation via filesystem redirection attacks. The Client and its associated binaries (Performance Metrics, WuaSearch, Reclaimer, TIMS) now enforce PROCESS_MITIGATION_REDIRECTION_TRUST_POLICY, preventing non-admin users from exploiting junction points, symlinks, or mount points to redirect file operations to unintended system locations.

Fix - Client - PLAT-29583, PLAT-29183: We fixed issues with the macOS uninstall script. The uninstall.sh script now correctly reads the configuration file for any custom log path and removes the associated log files during a full uninstall. Additionally, when uninstalling via the DMG package, the uninstall script located in /Library/Application Support/1E/Client is now correctly deleted.

Fix - Client - PLAT-30921: We fixed an issue where the 1E Client could crash when receiving an invalid HTTP header from a server. The client now handles malformed HTTP headers gracefully instead of crashing, improving overall stability and resilience.

Original source
July 2026
No date parsed from source.

First seen by Releasebot:
Jul 4, 2026
ControlUp

Custom Hive 1232

ControlUp fixes minor bugs and improves system logging.
Bug Fixes

Fixed various minor bugs.

Improved system logging.

Original source
July 2026
No date parsed from source.

First seen by Releasebot:
Jul 4, 2026
ControlUp

Custom Hive 1230

ControlUp improves agent deployment and adds new monitoring metrics.
Enhancements

Improved agent deployment process.

Added new monitoring metrics.

Original source
July 2026
No date parsed from source.

First seen by Releasebot:
Jul 4, 2026
ControlUp

Custom Hive 1229

ControlUp fixes alerting issues and improves data accuracy.
Bug Fixes

Fixed alerting issues.

Improved data accuracy.

Original source

Digital Employee Experience Release Notes

Products (12)

Latest Digital Employee Experience Updates

9.2.5

Release Date: July 14, 2026

Current Build: 9.2.5.634

Download Links

New Features

Monitor Omnissa Unified Access Gateway (opens in new tab)

Monitor Host GPUs

Monitor Windows Events (opens in new tab)

Managed Identity for Azure (opens in new tab)

Azure Availability Zones (opens in new tab)

New Health Metrics for Citrix Cloud Connector (opens in new tab)

Monitor FSLogix Dirty Bit Flag (opens in new tab)

Shared Credentials for Script-based Actions (opens in new tab)

Nutanix v4 and Prism Support (opens in new tab)

Bug Fixes

Real-Time DX (build 601)

Web Interface (build 601)

Real-Time DX (build 484)

Nexthink Infinity Standard edition 2026.6

AI Tools: Cascading filters

Workspace ✦: Expanded Assist knowledge sources

Desktop Virtualization: FSLogix insights

Device View: Enhanced performance and activity insights

Collector: Device configuration profiles

Applications: Overview and adoption for limited view domains

Horizon Web Client 2503.2

Horizon Web Client 2503.2 | 09 JUL 2025

What’s New

Before You Begin

Resolved Issues

Known Issues

Audio and Video

Browsers

Connectivity

Security

Miscellaneous

Documentation

Localized Content for Omnissa Docs

Support Contact Information

Omnissa Horizon 8 2503.2

Upgrading Changes

Important Notes

What’s New

License Activation

Horizon Connection Server

Horizon 8 API

Horizon Edge and Horizon Cloud Connector

Horizon 8 Deployed on Public Cloud SDDCs

Before You Begin

Upgrade

Compatibility Notes

Resolved Issues

Known Issues

BigFix Enterprise Suite Download Center 10.0.16

General

Download

Installation Generator

Server

Platform API

Relay

Agent

Console

Utilities

Versions

External Libraries

Internal

BigFix Support

Straight to Support: Use Remote Connect to Resolve Device Issues Faster

Put All Your Tools in the Same Toolbox

Instill Trust in Employees and Clients

Learn More about Remote Connect and WXP

Additional Resources

TeamViewer DEX 26.7 release notes

Tia Reporting Liveboards

Creating and using Liveboards

Operational safeguards: Instruction approval bypass for single devices

Primary user and last logged in user information