Omnissa Release Notes

Resolved Issues

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

• MSIX application packages fail to attach to a different OS even when the Allow package delivery to any operating system, an advanced setting, is enabled and the following error can be seen in System Messages in the App Volumes Manager admin UI:

  MSIX Package _name_of_the_package locked to name_of_package_OS was not attached to name_of_the_computer because it is not allowed on User’s Machine’s OS_

  [AVM-33322]

• Administrator (Read Only) account can neither expand the + button of each application and package on their respective summary pages nor able to view their respective details in the App Volumes Manager admin UI though they are able to view the list of applications and packages on the summary pages. [AVM-33408]

• When replicating packages or AppStacks from a vSAN datastore, the replication fails to copy these files to the destination storage. In the App Volumes Manager log file, the packages and AppStacks meant for replication are skipped. [AVM-33446]

• App Volumes Manager FQDN is shown as Unknown in the CONFIGURATION > Managers > App Volumes Manager Servers page in the App Volumes Manager admin UI. [AVM-33399]

• Due to an internal issue in the LDAP Base field, accessing the AppStacks > Volumes (2.x) tab displays the App Volumes server error, and the tab is not accessible. This issue occurs when the LDAP Base field contains a value. [AVM-33108]

In the App Volumes Manager logs, the following error can be observed:

[2024-02-02 19:50:43 UTC] P4672R1802 ERROR Manager: Inspecting Array (195620) (from log block)
[ 0] "D:/CloudVolumes/Manager/vendor/bundle/ruby/3.2.0/gems/actionview-6.0.6.1/lib/action_view/helpers/translation_helper.rb:60:in \translate'" , [ 1] "D:/CloudVolumes/Manager/app/views/appstacks/index.html.erb:217:in`

The LDAP Base field is present in the Register Active Directory Domain page in the App Volumes Manager admin UI.

For a description about the LDAP Base field, see Register an Active Directory Domain topic in the Omnissa App Volumes Administration Guide.

• Unable to replicate packages if the folder structure provided in the Default Storage Path field in the CONFIGURATION > Storage tab of the App Volumes Admin UI (for example: /appvolumes/packages) is not present on the datastore during the replication of packages. [AVM-33431]

The following error is reported in the log:

ERROR RvSphere: Fault in folder_exists? #<Thread:0x000000010559b130 run> (exception NoMethodError): undefined method \include?’ for nil:NilClass`

• When accessing DocuSignPrintDriver, delivered as an application package, the printer becomes unavailable due to issues in registry virtualization. If trying to view the printer properties then the following DocuSignPrintDriver Printer Properties error message is displayed:

  The DocuSignPrintDriver printer driver is not installed on this computer. Some printer properties… . [AVA-23718]

• “new Microsoft Teams” application fails to launch when Profile-only or UIA+profile Writable Volume is attached to the agent computer.

  NOTE: When this issue occurs, no error message is displayed by the application. [AVA-23756]

• Microsoft Teams icon is not visible in the Start menu when delivered as an on-demand MSIX application package. [AVA-23761]

Known Issues

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

• Published applications on demand fail to launch when App Volumes 2603.1 or earlier versions are used with Horizon 2606. [AVA-28403]

  Workaround: Upgrade to App Volumes 2603.2 and later.

  Resolved: This issue is now resolved in App Volumes 2603.2 and later.

• Applications such as Google Chrome Portable (installed per user) display a blank window or an Aw, Snap! error at first launch when using a UIA+profile Writable Volume. [AVA-27476]

• Horizon Agent 8.14 (2412) and 8.15 (2503) processes crash during a Horizon Client reconnect if the Horizon configuration includes an App Volumes package which contains Visual C++ x64 runtime version 14.36.32532.0 or earlier. [AVA-25969]

• App Volumes redirection of the search index from a folder on the system volume (C:\ProgramData\Microsoft\Search\Data) to a folder on the Writable Volume (C:\SnapVolumesTemp\writable\persistent\Search\Data) does not occur on Windows 10 with App Volumes 2312 and later and Windows 11 with any version of App Volumes. [AVA-24417]

  Typically in App Volumes configurations with a Writable Volume, if redirection is not already configured by DEM (Dynamic Environment Manager) or GPO (Group Policy Objects), App Volumes automatically redirects the OS search index from a folder on the system volume (C:\ProgramData\Microsoft\Search\Data) to a folder on the Writable Volume (C:\SnapVolumesTemp\writable\persistent\Search\Data).

• “new Microsoft Teams” which is installed in the base image, launched, and updated successfully by the user with a UIA+profile Writable Volume at the first login fails to launch at the second login onwards with the same UIA + Profile writable. This failure occurs because unexpected registry entries are captured in the Writable Volume. [AVA-24024]

  Workaround: Customize the base image by adding the following exclusions in custom\snapvol.cfg:

  exclude_registry=\REGISTRY\MACHINE\Software\Classes\PackagedCom

  exclude_registry=\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\ms-teams.exe

  exclude_registry=\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\ms-teamsupdate.exe

  When the user having the same Writable Volume logs into the agent computer which has the updated based image, new MS Teams launches successfully.

• Running the change logon command on an RDS host does not work when application packages or Writable Volumes are attached to the RDS host. Status of the RDS host machine is not updated in the Omnissa Horizon console. [AVA-23264]

  Workaround: Add the following in the custom snapvol.cfg file:

  exclude_registry_value_path=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\WinStationsDisabled.

• An advertised shortcut launches the MSI installer when the shortcut is clicked. App Volumes agent does not allow the MSI installer to run when a corresponding application package having such an advertised shortcut is virtualized.

  The following error message is displayed:

  This action is not allowed for application . [AVA-21004]

  Workaround: When packaging the application, delete the advertised shortcut from the Start menu, and recreate another shortcut for the application’s executable.

• 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-20343]

• 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. [AVA-20264]

• Applications cannot write large string values (several hundred thousand characters) to the registry. [3034063]

• 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. [2791414]

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

• 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. [2624048]

  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.

• 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. [2845852]

  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")

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

  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

With Horizon Client for Android, users can connect to and use remote desktops and published applications using an Android phone or tablet. Horizon Client for Android also supports Samsung Dex and Zebra devices.

IMPORTANT NOTICE: Changes to Support Lifecycle Dates

Effective with Horizon Client version 2606, the End of Availability (EOA), End of General Support (EOGS), and End of Technical Guidance (EOTG) milestones for this client changed from the previous policy to the policy shown below.

Note: The support policy for versions before 2606 remains unchanged.

Milestone Previous Policy Policy from 2606 Onwards EOA / EOGS GA + 36 months GA + 18 months EOTG EOGS + 12 months EOGS + 12 months (unchanged)

What’s New

Horizon Client for Android 2606 is released along with Horizon 8 2606.

• Blast Networking - Open SSL 3.5 Upgrade

Horizon components have been updated to use OpenSSL 3.5, replacing the previous OpenSSL 3.0.x libraries which are approaching end of life. This includes the Blast Secure Gateway (BSG) for both Connection Server and Unified Access Gateway (UAG).

Before You Begin

• Horizon Client for Android is supported with the following deployment types:
  • Horizon 8 version 2006 and later
  • Horizon Cloud in Microsoft Azure
  • Horizon Cloud Service - next-gen
• Horizon Client for Android requires the Android 14, 15, or 16 operating systems.
• When you install Horizon Client for Android, you are prompted to let the app read phone status and identity. This prompt relates to the RSA soft-token integration feature. The prompt is requesting permission to read the state of the phone. This permission does not allow the app to make a phone call or send a message. You can safely grant this permission.
• Install and upgrade Horizon Client for Android just as you do any other Android app. For example, you can get the latest version of the app from Google Play or the Amazon Appstore for Android. For a link to the Horizon Client app in one of these stores, go to the Horizon Client Downloads page.

Resolved Issues

There are no resolved issues in this release.

Known Issues

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

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

• Android Dex multi-monitor mode does not work

  Applications are unable to display windows on both the Device screen and the Dex screen at the same time. This occurs on all Android 14 phones with the latest updates.

  Workaround: None.

• User input displays on suggestion bar of keyboard when using Horizon Screen Keyboard to enter letters or numbers in the password input box of the Windows Lock screen.

  Workaround: There are two ways to address this issue.

  • Disable Predictive Text on mobile device settings, or
  • Switch to Direct Touch mode and enable Windows Native Touch Gestures in Client Settings. Wait for the Windows keyboard to automatically pop up and then use the Windows keyboard for password input.

• When the Samsung DeX “New” view mode is selected, the Android taskbar will only display the Horizon client main window.

  When this problem occurs no remote session window displays on the taskbar. Any minimized session windows cannot be restored and are therefore inaccessible.

  Workaround: None.

• On certain Android devices, when you use the client drive redirection feature to copy, rename, or create files on a redirected external SD card, you receive the error “You need permission to perform this action.”

  This problem occurs if the Android device prevents third-party apps from getting automatic permission to put files on an external SD card.

  Workaround: None.

• If you use a NAT64 network that is shared from a macOS 10.14 or later system, internet access is not available on an Android device and Horizon Client for Android cannot connect to a server.

  Workaround: Use an earlier macOS version to share the NAT64 network, for example, use macOS version 10.11.6.

• When you connect to a remote desktop with the High Quality Mode option enabled, if you change the resolution from the Auto-fit resolution option to another resolution in the Horizon Client settings, and then change the resolution back to the Auto-fit resolution option, Horizon Client uses the wrong resolution.

  Workaround: Log off and reconnect to the remote desktop.

• When you use the Horizon Blast display protocol to connect to a remote desktop or published application with a non-English input method, you might not be able to enter certain symbols.

  Workaround: Use the local input buffer, or connect to the remote desktop or published application with the PCoIP display protocol.

• On some Android devices, certain keys introduce white spaces when you connect to a remote desktop and input text with Horizon Client.

  Workaround: Turn off predictive text for the keyboard in the Android Settings app.

• The Unity Touch sidebar cannot show changes in the All Programs menu for new software that you install during that same session.

  Workaround: To see items for new software that you recently installed, disconnect from the desktop and then connect again.

• Because an Android device does not have a persistent ID, the device’s MAC address is used to generate an ID for the license. If a device’s MAC address cannot be detected, its SIM is used instead. If neither the MAC address nor SIM can be detected, a random ID is generated for the device. In certain circumstances, this process can result in multiple licenses being issued to the same device.

  Workaround: An administrator can remove the inactive licenses.

Documentation

Horizon Client for Android documentation is in the Omnissa Product Documentation portal.

Localized Content for Omnissa Docs

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

Support Contact Information

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

For information on filing a support request in Customer Connect and via Cloud Services Portal, see KB 6000005.

Original source

Horizon 8 2606 | 24 AUG 2026

Server Build: 8.19.0-32260804026 Agent Build: 8.19.0-32216675775

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

Important Notes

• The Horizon 2606 Agent is supported with both the 2603 ESB Server and the 2606 Server versions. See Compatibility Matrix for Various Versions of Horizon 8 Components for more details.
• For customers running Horizon 8 2512 with Nutanix automated pools or farms: A pairing mechanism change in 2603 requires that Connection Servers and Agents must both be updated to 2603 or later for ongoing provisioning operations to work. To prepare your environment for limited backward compatibility, see KB article 6001315. Does not apply if you have already upgraded to 2512.1 or later.
• Horizon 8 is not supported with vSphere 6.5 or vSphere 6.7, which are both past the end of General Support. Horizon 8 Instant Clones are incompatible with these vSphere versions, and you must upgrade to vSphere 7.0 or later before upgrading to Horizon 8 to use Instant Clones.

What’s New

Horizon Connection Server

• The Connection Server installer now automatically stops and disables Active Directory Web Services (ADWS) during installation, reducing the default security exposure surface. ADWS is not required for normal Connection Server operation and can be enabled when temporarily needed through the Horizon Advisor AD LDS Operations menu.
• This release introduces next preferred site logic in Cloud Pod Architecture (CPA). Administrators can define an explicit preferred site order so that when an initial site reaches capacity, sessions are routed to the next configured site rather than falling back randomly.
• The new AD LDS migration script allows customers with large CPA deployments to move from the legacy AD LDS partition to the new Horizon partition over extended migration period. It supports staged migration, so independent pods can be migrated in separate maintenance windows while CPA remains functional. Administrators can add or remove local pools from global entitlements, create or delete global entitlements, and perform site operations during migration, reducing risk and downtime for large, multi-pod deployments. This script is now delivered as part of Horizon Advisor and is no longer available as a standalone script.
• PSG (PCoIP Secure Gateway) is now selectable as an optional component during the Horizon Connection Server installation.
• Administrators can now upgrade, modify, repair, or reinstall Horizon Agent on a Nutanix Golden Image without needing to change its Windows hostname (computer name). Existing registration is preserved, pool operations are unaffected, and installer workflows have been optimized to avoid unnecessary re-registration and pairing actions.
• Microsoft introduced Microsoft Entra Hybrid Join using Microsoft Entra Kerberos that significantly improves sync wait time for Entra ID Hybrid Managed mode. For details, see Support for Microsoft Entra (Azure Active Directory).
• Horizon Agent Auto-Upgrade (AAU) now supports Nutanix AHV environments. Administrators can extend automated agent lifecycle management to Nutanix AHV-hosted desktop pools in addition to existing vSphere support.
• New password requirements have been introduced for Connection Server LCM API installations and upgrades, varying depending on the installation type and hosting method.
• True SSO unlock now supports any third-party SAML Identity Provider, in addition to Workspace ONE Access. The Identity Provider must support SP-initiated SSO using the HTTP POST binding for AuthnRequests.
• Administrators can now create App Volumes published apps on demand using manual RDSH Farms in addition to the existing support for Instant Clone automated RDSH Farms.
• Horizon 8 now calculates Concurrent Connection User (CCU) license consumption using the same logic as Horizon Cloud, giving administrators and license teams accurate, consistent usage counts across both platforms. A new REST API also lets the UI and Edge Gateway retrieve historical peak and daily CCU data, reducing reliance on manual or unreliable tracking and giving license teams data for compliance and capacity planning.
• Horizon components have been updated to use OpenSSL 3.5, replacing the previous OpenSSL 3.0.x libraries which are approaching end of life. This includes the Blast Secure Gateway (BSG) for both Connection Server and Unified Access Gateway (UAG).

Horizon Console

• Administrators can now monitor Unified Access Gateway (UAG) health and utilization at the pod level directly from the Horizon Console, displaying real-time availability status, service health, error details, and certificate expiration status for each UAG appliance.
• A new Isolated App Launch setting is available for published applications. When enabled, each application launch starts in a new, independent RDSH session rather than reusing an existing session.
• JWT authenticator configuration has been relocated to Global Settings > Authenticators in the Horizon Console, providing a single location for managing all authentication methods.
• Administrators can now apply an Allowed User Access Location to multiple desktop pools or application pools in a single action from the Horizon Console.
• Horizon Console UI behavior: Rows Per Page preferences are automatically saved in the Horizon Console.
• Certificate management for SAML certificates is now available within the Horizon Console, enabling administrators to view, update, and manage SAML certificate lifecycles without leaving the console.
• Horizon Console tables, including session grids, now support a “Select All Pages” option, restoring the ability to select rows across all pages of a multi-page table rather than only the currently visible page. This allows bulk actions, such as sending messages to all sessions, to operate on the full result set instead of requiring page-by-page selection.

Horizon Agent for Linux

• Horizon now supports application-based URL redirection for the Linux Agent, enabling URLs clicked in applications such as Slack and email clients to redirect to the Horizon Client on Mac, Linux, and Windows.
• Horizon Agent for Linux 2606 adds support for ECDSA certificate types for the agent TLS endpoint. Both RSA (default) and ECDSA key types are now supported via installer flags.
• Horizon Agent for Linux 2606 upgrades the bundled OpenSSL libraries from the 3.0.x series to the latest available 3.5.x release to support continued compliance with cryptographic library requirements.
• Administrators can now configure the sample rate used for redirected (virtual) microphone audio on Horizon Agent for Linux VDI desktops.
• FIPS 140-3 mode is now supported on RHEL 9.x (9.6 and later).
• This release adds support for Debian 13.4, RHEL 9.8, and Rocky Linux 9.8, and drops support for Debian 13.3. Wayland support for RHEL 10.0 on Horizon 8 on vSphere is added as Beta, For more details, please check beta.omnissa.com.

Horizon Agent for Windows

• The “Instant Clone Agent” feature in the “Horizon Agent for Windows” installer has been renamed to “Provisioning and Customization Agent” to reflect that this feature is required for provisioning other types of pools and farms besides vSphere. Existing deployments are not affected by this change.
• Horizon Agent for Windows 2606 upgrades the bundled OpenSSL libraries from the 3.0.x series to the latest available 3.5.x release to support continued compliance with cryptographic library requirements.

Horizon Agent for Mac - LIMITED AVAILABILITY

• Horizon Agent for macOS enters Limited Availability (LA) for production environments in 2606. Administrators can install the macOS Agent on physical macOS devices and enroll them with Workspace ONE UEM to centrally manage required macOS privacy permissions, including Screen Recording and Accessibility, through MDM policies. This eliminates the need for end users to manually approve permission prompts during Horizon login or remote session workflows.

Horizon 8 on Amazon WorkSpaces Core

• Improved WorkSpaces quota validation: Before creating or editing a pool, the system verifies that the requested number of WorkSpaces fits within the AWS regional quota based on current usage. If the quota or current usage cannot be retrieved because of a transient AWS API issue, the validation allows the operation to proceed, improving pool creation reliability while preserving AWS-side quota enforcement.
• Horizon 8 on Amazon WorkSpaces Core now supports encrypting the WorkSpaces instance within the automated pools workflow. Administrators can chose either the AWS managed KMS key or a Customer managed KMS key. When choosing to encrypt a WorkSpace instance, both root and user volumes will be encrypted. Doing so ensures that the data stored at rest, disk I/O to the volume, and snapshots created from the volumes are all encrypted. Encrypted WorkSpaces instances take longer to provision than unencrypted instances. For more information see Encrypted WorkSpaces in WorkSpaces Personal - Amazon WorkSpaces.
• Administrators can now perform pool bundle maintenance operations directly from the Horizon console, improving operational efficiency and reducing reliance on external workflows. Pool maintenance scheduling enables updates to the bundle or image associated with a pool, with changes in Horizon automatically synchronized to AWS. For non-persistent pools, refresh operations now offer flexibility to either force user logoff or wait for users to log off naturally. Additionally, the pool machines tab has been enhanced to display WorkSpace ID, Bundle ID, and Image ID, providing clear visibility into current configuration and maintenance status.

Nutanix

• Improved provisioning retry and recovery logic for Nutanix virtual machines that experience customization failures.

Remote Desktop Features

• Cache Size Enforcement for Linux Client Redirection Features: Added support for cache size limits for Browser Content Redirection (BCR) and HTML5 Multimedia Redirection (HTML5MMR) on Linux clients. Administrators can configure maximum cache sizes to prevent excessive disk usage from client-side browser processes.
• Blast protocol now supports ECDSA Certificates.
• Storage Drive Redirection (SDR) has been removed from the Horizon Agent installer and is no longer available in Horizon Client. To share local drives and folders with remote desktops and published applications, use Global Sharing (Client Drive Redirection) instead.

Windows OS Optimization Tool for Omnissa Horizon

• New Security tab options: Turn Off Device Encryption and Disable BitLocker
  • Turn Off Device Encryption decrypts all the encrypted volumes on the VM. The tool waits for the decryption to completed before moving on to the next step. The decryption may take some time to complete depending on the size of the volume.
  • Disable BitLocker prevents Windows from automatically enabling device encryption on the image.
• The Windows OS Optimization Tool has been enhanced for the golden image creation workflow, streamlining the end-to-end preparation process.
• OSOT SCCM integration now supports VMware Tools management within SCCM task sequences. Administrators can include VMware Tools installation and configuration steps in SCCM-based golden image creation workflows.

Resolved Issues

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

• AST-14744: Remote Assistant Support broken due to Microsoft patch update
• HZN-10304: VLAN subnets from multi-cluster virtual switches were not displayed in the network selection UI (Nutanix pool management).
• HZN-10301: REST API intermittently returned “This application is currently not available” when connecting to a published application.
• HZN-10257: The inventory page loaded slowly in large-scale deployments.
• HZN-9969: Expanding a pool with an NVIDIA vGPU could fail with the error “Host or cluster does not support the same GRID vGPU type as the template or snapshot.”
• HZN-9966: The Connection Server favicon request returned a 502 error after a replica server restart.
• HZN-9950: In the Instant Clone pool Schedule Push Image flow, the Push to Specific Machines grid displayed all data on a single page and did not honor pagination.
• HZN-9909: The REST API Push Image endpoint for Instant Clone pools was missing MAINTENANCE_ADMIN validation.
• HZN-9771: Moving between pages cleared the selected items in Users and Groups for a Global Entitlement.
• HZN-9764: Smart Card authentication with a custom altSecId mapping failed to pass userNameHint to the AD lookup.
• HZN-9705: Users could not access VDI via Workspace ONE Access after upgrading the Horizon environment.
• HZN-9525: After a silent install, first logon to Horizon Console with an administrator account from a child domain could cause errors under Settings.
• HZN-9471: Editing pools could fail with the error “Host or cluster with requested id was not found.”
• HZN-9467: Authentication to Linux desktops failed after upgrading Horizon.
• HZN-9392: A Connection Server upgrade could fail with an “Allow_ntlmfallback cannot be null” error.
• HZN-9277: Unable to edit pools or provision VMs on pools after upgrading.
• HZN-9179: Desktop pool provisioning failed with an LDAP runtime error (Nutanix).
• HZN-9158: Desktop pool creation issue with Horizon Connection Server on Ubuntu (duplicate of another tracked issue).
• HZN-9149: Universal Broker JWT-based authentication broke when upgrading Connection Server from 2506 to 2603 (duplicate of another tracked issue).
• HZN-9139: Horizon did not connect reliably to Nutanix.
• HZN-9133: Adding virtual machines to a Full Clone pool failed with the error “delete_or_refresh_machine_after_logoff can be set to REFRESH only for instant clone desktop pools.”
• HZN-9124: Creating a new RDS Host could fail with “A desktop pool or farm named [name] already exists” even when no such pool or farm existed.
• HZN-9061: Unable to access the second page of the Applications inventory in Horizon Console after upgrade.
• HZN-9036: The GET external/v1/ad-users-or-groups API did not return correct data depending on how pages were requested.
• HZN-9004: Instant Clone Push Image Applies to Only a Few VMs While Remaining VMs Retain Old Image
• HZN-8915: Connection Server did not properly handle Nutanix machine cache updates when the PendingOperation owner changed to another Connection Server.
• HZN-8893: Creating a new Linux OS desktop pool did not display the Customization Specification option (duplicate of another tracked issue).
• HZN-8883: The InternalVMSweeper job running concurrently on multiple nodes could cause provisioning failures (NGVC).
• HZN-8871: Machine status in the Summary tab was inaccurate for Capacity Provider-based VMs (Nutanix).
• HZN-8793: Horizon memory data was missing from the Pool view.
• HZN-8790: Authentication to Linux desktops failed after upgrading Horizon.
• HZN-8785: Constant async commit events were written to the error.log-.old file on the Connection Server.
• HZN-8772: The Connection Server Admin UI became unavailable.
• HZN-8749: The domain changed unexpectedly when editing a pool.
• HZN-8747: Log collection using Horizon Console failed with an internal server error.
• HZN-8686: Log collection using Horizon Console failed with an internal server error.
• HZN-8432: After disconnecting from a Horizon desktop session, a new desktop was assigned on reconnection instead of the original one.
• HZN-8336: Unable to view domain accounts under Horizon Console > Domains; displayed “An internal server error occurred.”
• HZN-8253: Removed unnecessary fetching of counts from the historical table, improving performance.
• HZN-988: ADMIN_LIMIT_EXCEEDED error occurs when more than 1273 global entitlements gets local resource assignments in one pod

Known Issues

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

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

Horizon Connection Server

• HZN-8048: After restarting a Connection Server, the error “Cannot look up datacenter from Virtual Center.” is displayed in the Horizon Console.
  Workaround: See KB article 6001328.
• HZN-7443: If a VM is stuck in Customization state, delete the VM from Horizon Admin Console or Horizon REST API. Horizon will then recreate the VM.
• When there are more than ten global dedicated entitlements available to a user, the machine host name will sometimes not be visible in global entitlements if the “Show assigned host name” option is enabled.
• Scheduling an upgrade for an RDS host may complete successfully, but the upgrade itself can fail when the scheduled time is reached.
  Workaround: See KB article 6000992.
• If Horizon Events Database is hosted by an instance of Microsoft SQL Server (any version), do not disable TLS 1.2. This connection cannot be made over TLS 1.3.
• HZN-2542: When changing the browser locale and refreshing the Horizon Console UI, error alerts fail to display for the newly selected language.
  Workaround: Log in to Horizon Console in a new browser tab.
• HZN-19589: CPA join fails for a pod if the “Default First Site” is removed from the federation/pod it joins.
  Workaround: Perform the join after setting pae-LDAPSchemaVersion to a lower value than the current one under CN=common,OU=Global,OU=Properties,DC=vdiglobal,DC=horizon,DC=internal.
• HZEC-2336: View API consumers like the MP4H Adapter invoke MachineDetailsView. This API fails intermittently with user data not found error.
  Workaround: None
• HZEC-2873: Number of issues reported for ESXi Hosts in the dashboard summary may not match with number of issues reported in the dedicated ESXi Host issues section in the dashboard. If NVIDIA vGPU support detects a mismatch with the supported vGPUs for the given host, the issue count should be incremented but the count may not display in the UI.
  Workaround: View the warnings in Dashboard > System Health > View > vSphere > ESX Hosts.

Horizon Agent for Windows

• HZN-8997: The Admin UI displays an incorrect GOS type for the Agent VM following the upgrade from Windows 10 to Windows 11.
  Workaround: Remove the machine from the Admin UI (under Registered Machines > Others), then reinstall the unmanaged agent. After completing these steps, the Admin UI correctly displays the operating system as Windows 11.
• When a QoS policy is configured on the Horizon Agent, the Bypass Blast Service TCP proxy feature is disabled.
  Workaround: None.

Horizon Agent for Linux

This section describes issues that might occur with Horizon Agent for Linux or when you configure a Linux desktop.

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

Horizon Client

This section describes problems that end users might encounter when using Horizon Client or Horizon Web Client to connect to remote desktops and applications. For problems that occur only in a specific Horizon Client platform, see the Horizon Client release notes in the Omnissa Product Documentation portal.

• VCART-9656: When you connect to a Linux desktop, some keyboard inputs do not work. For example, if you are using a non-English IME on both the client device and the remote desktop, some non-English keys are not displayed correctly.
  Workaround: None.
• VCART-9655: When you use the Ambir Image Scan Pro 490i to perform a scan on a remote desktop or application, the dialog box always displays “Scanning…” and does not complete.
  Workaround: Perform a scan on the client. The client scan calibrates the scanner. After the calibrate operation is finished, save the calibration file and deploy it in ProgramData\AmbirTechnology\ImageScanPro490i.
• VCART-4245: HDR support for full screen mode is limited to a scenario where the selected monitor is the primary monitor.
  Workaround: None.

Windows OS Optimization Tool

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

APIs

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

Nutanix

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

Horizon Advisor

• HZM-10760: Server requirement checks in remote mode: When prechecks are run remotely against a target server, the Static IP, OS Edition, OS Version, and Installed Features results reflect the machine running Horizon Advisor rather than the target server.
  Workaround: Run the precheck locally on the target server to get accurate results for these four checks.

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 VMware 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 VMware Solution, see KB 88202.
For a list of Horizon 8 features supported on Alibaba Cloud VMware Service (ACVS), see KB 92140.

Before You Begin

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

Upgrade

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

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

Compatibility Notes

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

Use of Open Source

Horizon 8 uses several open-source software packages. For more information about what packages are used in this release, see Open source notices.

• Horizon Connection Server 2606 is built on the Apache Tomcat implementation of Jakarta EE, version 10.1.57 and on the BellSoft Liberica distribution of OpenJDK, version 21.0.11.0.1 (CPU).
• Horizon Agent for Linux 2606 and Horizon Agent for Windows 2606 use the BellSoft Liberica distribution of OpenJDK, 21.0.11.0.1 (CPU).

Documentation

Horizon 8 documentation is in the Omnissa Product Documentation portal.

Localized Content for Omnissa Docs

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

Support Contact Information

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

For information on filing a support request in Customer Connect and via Cloud Services Portal, see KB 6000005.

Original source

Unified Access Gateway appliances provide users with secure remote access to virtual desktops, internal sites, applications, and file repositories. To learn more, see Unified Access Gateway Documentation.

Omnissa Unified Access Gateway Release Notes provide information about the new features and enhancements in each release. This page contains a summary of the new capabilities, issues resolved, and known issues that are reported in each version.

What’s New

Unified Access Gateway 2606 provides the following new features and enhancements:

General

• AlmaLinux 9.6 Operating System upgrade

The Unified Access Gateway appliance operating system has been upgraded from AlmaLinux 9.2 to AlmaLinux 9.6. The upgrade maintains full deployment compatibility across all supported hypervisors and preserves existing system hardening, authentication, password management, FIPS enablement, and STIG compliance behavior.

• Enhancement to log rotation and disk space management

Improved log management mechanisms to monitor disk utilization and trigger early log rotation, helping prevent storage from filling up in large-device environments.

• Logging and troubleshooting improvements

• Updates to OS package versions and Java component versions

Horizon

• Update SSL Server certificate and key without service restart

Unified Access Gateway now supports TLS certificate replacement without interrupting existing user sessions. Existing sessions remain connected while new sessions use the updated certificate. If a network interruption occurs after renewal, an automatic reconnect can fail because Horizon Client still expects the previous certificate. The Horizon Client user can reconnect by selecting the entitlement again. See TLS/SSL Certificates.

• Native QCOW2 image for KVM-based hypervisors

Unified Access Gateway is now available as a native QCOW2 image, eliminating the need for manual image conversion when deploying to KVM-based hypervisors. Nutanix AHV is qualified and supported in this release.

Starting with UAG 2606, Nutanix AHV deployments use the QCOW2 image. Nutanix is no longer listed on the vSphere/AWS/Google Cloud OVA - existing AHV customers should switch to the QCOW2 artifact at their next deployment or upgrade. See PowerShell deployment to Nutanix AHV.

• Support for ECC TLS certificates and ECDSA Cipher Suites

Elliptic Curve Cryptography (ECC) TLS certificates together with ECDSA cipher suites are now supported, in addition to the existing RSA-based certificates.

• Support for multiple signing certificates in IdP metadata

When an external identity provider IdP metadata that includes more than one signing certificate is uploaded, all of them are now considered for SAML authentication during Admin UI login.

• Dedicated SAML signing certificate configuration

Added support for configuring a dedicated signing certificate for SAML authentication with an external identity provider (IdP). Using the TLS certificate for SAML signing remains supported when a dedicated certificate is not configured.

Content Gateway

In this release, we have made a few updates containing overall security and stability with no new features.

Before You Begin

• Install and Upgrade

To download the Unified Access Gateway, see the Product Download page.

• Security Scan

Because of the OS update, special instructions are required to get accurate scan results of the operating system used by the Unified Access Gateway appliance. For more information, see Security scanning of Linux on Unified Access Gateway (UAG) version 2412 and beyond (6000738).

Resolved Issues

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

• PPAT-22168: Stop sending Tunnel-related logs to stdout and stderr in UAG.
• PPAT-21439: Improved DTR validation workflow where a non-matching protocol specifier (such as UDP:*) stopped evaluation of the other domains in the same DTR rank.
• AST-25524: Error "UAG settings imported partially due to one or more errors observed while trying to persist settings" is displayed when exporting a JSON configuration from UAG admin console and importing the same file back without any modifications.
• UAG-13396: Stack trace disclosure from an API, under certain conditions.
• UAG-13133: If certain configurations are updated in rapid succession, the health status might show an incorrect state.

Known Issues

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

• PPAT-21429: Syslog over TCP fails when sent directly from Tunnel service.

Workaround:

1. On Workspace ONE UEM console, go to Tunnel configuration and select the Syslog Hostname as localhost.
2. On UAG Admin console, go to Advanced Settings > Syslog server settings and select the Protocol as TCP.

Documentation

Documentation for Unified Access Gateway is located at Omnissa Product Documentation.

Support Contact Information

To receive support, access Customer Connect.
For information about filing a Support Request in Customer Connect and using Cloud Services Portal, see the Knowledge Base (KB) article 6000005.

Localization

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

Original source

With Horizon® Client™ for Windows 2606, you can access remote desktops and published applications from your Windows computer with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).

IMPORTANT NOTICE: Changes to Support Lifecycle Dates

Effective with Horizon Client version 2606, the End of Availability (EOA), End of General Support (EOGS), and End of Technical Guidance (EOTG) milestones for this client changed from the previous policy to the policy shown below.

Note: The support policy for versions before 2606 remains unchanged.

Milestone Previous Policy Policy from 2606 Onwards EOA / EOGS GA + 36 months GA + 18 months EOTG EOGS + 12 months EOGS + 12 months (unchanged)

What’s New

• True SSO unlock now supports any third-party SAML Identity Provider, in addition to Workspace ONE Access. The Identity Provider must support SP-initiated SSO using the HTTP POST binding for AuthnRequests.
• Horizon components have been updated to use OpenSSL 3.5, replacing the previous OpenSSL 3.0.x libraries which are approaching end of life. This includes the Blast Secure Gateway (BSG) for both Connection Server and Unified Access Gateway (UAG).

Before You Begin

• For the Windows operating systems that this release of Horizon Client for Windows supports, see the Horizon Client for Windows Guide.
• Horizon Client for Windows is supported with the latest maintenance release of the following deployment types:
  • Omnissa Horizon 8 version 2006 and later
  • Omnissa Horizon Cloud Service - Next-Gen
  • Horizon Cloud in Microsoft Azure
• To use Horizon Client in FIPS mode, you must use Connection Server version 2309 or later; if using Unified Access Gateway, you must also use Unified Access Gateway 2309 or later. For more information, see Omnissa Knowledge Base (KB) article 95144.
• To install Horizon Client for Windows, download the installer from the Horizon Clients download page.
• For installation instructions, see the Horizon Client for Windows Guide.
• For information about the features that are supported in nested mode, see Omnissa Knowledge Base article 80509, “Horizon Guidelines for Nested Mode.”

Resolved Issues

The following issues are resolved in this release.

There are no resolved issues in this release.

Known Issues

• Jumplist, URI, and Shortcuts may not work for Horizon Client Next.

Workaround: Rename horizon-client-next to horizon-client. You can also rename the existing horizon-client binary to any name of your choice to avoid conflicts.

Documentation

Horizon Client for Windows documentation is in the Omnissa Product Documentation.

Localized Content for Omnissa Docs

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

Support Contact Information

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

For information on filing a support request in Customer Connect and via Cloud Services Portal, see Omnissa Knowledge Base article 6000005.

Original source

This page contains release-related information for Horizon Client for Linux 2606, which enables users to connect to and use remote desktops and published applications using a Linux device.

This page is revised periodically as needed with information about the release. Check back regularly for additions and updates to these release notes.

What’s New

Horizon Client for Linux 2606 is released in conjunction with Horizon 8 2606.

• Improved VAAPI Video Decoding Performance

  Video decoding performance on Linux clients using Intel and AMD GPUs has been improved with performance gains of up to 2x.

• FIDO2/U2F Hardware Security Key Authentication using USB Redirection

  Horizon Client for Linux now supports FIDO2 and U2F hardware security key authentication within Linux VDI sessions via USB redirection, enabling seamless web authentication without the manual configuration steps previously required.

• Linux Horizon Clients Gain FIDO2/WebAuthn Redirection Support for UWP Apps

  Horizon Client for Linux now supports FIDO2 (WebAuthn) redirection for UWP applications running inside the remote session. This enhancement brings the Linux Client to feature parity with the Horizon Windows Client, enabling end-user authentication scenarios such as signing into the new Outlook for Windows (UWP) and Microsoft Teams through secure and seamless FIDO2 device usage directly inside the virtual desktop.

• Blast Networking - Open SSL 3.5 Upgrade

  Horizon components have been updated to use OpenSSL 3.5, replacing the previous OpenSSL 3.0.x libraries which are approaching end of life. This includes the Blast Secure Gateway (BSG) for both Connection Server and Unified Access Gateway (UAG).

• Cache Size Enforcement for Linux Client Redirection Features: Added support for cache size limits for Browser Content Redirection (BCR) and HTML5 Multimedia Redirection (HTML5MMR) on Linux clients. Administrators can configure maximum cache sizes to prevent excessive disk usage from client-side browser processes.

• Horizon Client for Linux 2606 supports multiple audio output devices for Multimedia Redirection (MMR) over Blast. Users can now route audio from redirected media to a non-default audio output device, enabling more flexible audio configuration in VDI sessions accessed through linux client.

Resolved Issues

This release includes fixes for the following:

There are no resolved issues in this release.

Known Issues

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

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

Browser Redirection

• When using Browser Redirection from a remote desktop, drop-down menus on web pages may fail to expand.

  Workaround: None

• Right-click context menus in Chrome or Edge render incorrectly when BCR is enabled on Linux clients

  When using Horizon Client on Linux endpoints (Ubuntu or RHEL), right-click context menus inside Chrome or Edge within a Horizon VDI session may not display correctly when Browser Content Redirection (BCR) is enabled.

  Workaround: None

Display

• On some HP thin clients that have the HP ThinPro 5.2.0 (T6X52011) operating system, Horizon Client for Linux might display a black screen or crash when user is playing some video on a remote desktop and pressing the fast-rewind button on Windows Media Player.

  Workaround: Upgrade the OS to HP ThinPro 6.1.0 (T7X61007) or the latest version.

• The Horizon Client for Linux authentication domain list, desktop/application protocol list, and display list appear black on some Linux operating systems.

  Because Horizon Client for Linux uses the Linux operating system’s GNOME theme, these lists appear black, making them difficult to read.

  Workaround: Change the GNOME theme used by the Linux operating system. For example, on an Ubuntu system, install gnome-tweak-tool if it is not yet installed, run gnome-tweak-tool, and change the GTK+ theme from Ambiance to Radiance.

• When client users connect to a published application using a multiple-monitor configuration, they may encounter unexpected behavior in the display if they disconnect or reconnect monitors in their configuration.

  Workaround: Disconnect from the published application and reconnect again.

• Horizon Client does not support the Dark Appearance setting in Linux distributions.

  Workaround: None

• Power-save settings fail to take effect with mouse focus in desktop window.

  If the user’s mouse pointer is positioned in a remote desktop window, power-save and screen-saver settings fail to take effect on the client system when the configured timeout is reached.

  Workaround: Move the focus away from the desktop window by positioning the mouse pointer outside the desktop window.

HTML5 Multimedia Redirection (HTML5 MMR)

• When you open a local URL in Microsoft Edge on the remote desktop, multimedia content is not redirected to the client system as expected.

  By default, HTML5 MMR in an Edge browser only works for content situated on a non-local URL. To redirect content from a local URL, you must configure a certain setting for Microsoft Edge.

  Workaround: On the remote desktop, open a Command Prompt window and run the following command:

  CheckNetIsolation LoopbackExempt -a -n=Microsoft.MicrosoftEdge_8wekyb3d8bbwe
  

• HTML5 MMR and Browser Redirection do not work on Ubuntu 24.04 clients.

  In Ubuntu 24.04, the setting for restricting unprivileged user namespaces is activated by default. Due to a known Chromium limitation, this setting interferes with the operations of Electron, which is required by the HTML5 MMR and Browser Redirection features.

  Workaround: Run the command to deactivate the setting for restricting unprivileged user namespaces:

  sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
  

  Also, include this command in .bashrc or a similar startup file, to ensure the setting remains deactivated when the client system reboots.

Keyboard and Mouse

• Mouse does not work inside the Horizon Blast session when the keyboard layout is switched to Secondary Keyboard Layout

  Workaround: Manually add the following configuration option in the /etc/omnissa/config file:

  RemoteDisplay.allowVMPointerEvent2 = FALSE
  

• Keyboard and mouse do not work when connecting to a remote application from a Raspberry Pi running ThinLinX or Stratodesk.

  There is a system conflict when using H.264 decoding with ThinLinX or Stratodesk Raspberry Pi for remote application sessions.

  Workaround: Turn off H.264 decoding in the Horizon Blast settings.

• Windows shortcuts don’t work with seamless window applications.

  If there are identical shortcuts with differing functions on the client Linux operating system and a remote Windows operating system, the shortcut for the Windows operating system will not work when a seamless window application is active. Only the shortcut for the Linux operating system takes effect. For example, by default, pressing Alt opens a Search dialog window on an Ubuntu operating system and it shows the application’s menu on a Windows operating system. When a seamless window application is active, pressing Alt displays the Ubuntu operating system’s Search menu, but does not show the application’s menu.

  Workaround: Change the shortcut in the host Linux operating system or in the remote Windows operating system so that the shortcuts in the two operating systems do not conflict.

Multimedia Redirection (MMR)

• Videos do not play smoothly in remote desktops and sound disappears when MMR is enabled and the network delay is more than 75 ms.

  Workaround: Disable MMR when the network delay is more than 75 ms.

Printing

• If multiple Horizon clients connect to the same published desktop or published application simultaneously and map to a location-based printer with the same name, the printer appears in the first client session, but not in later client sessions.

  Workaround: For the client sessions in which the printer does not appear, perform a manual refresh. For a remote desktop, press F5 or refresh the Devices and Printers window. For a remote application, close and reopen the application print dialog box. The location-based printer appears in the printer list.

Real-Time Audio-Video (RTAV)

• When a Raspberry Pi 4 client user tries to play RTAV video at custom high resolutions (such as 1280 x 800) not supported by the connected USB webcam, the video fails to display in the remote desktop.

  Workaround: Use a standard resolution that is supported by the connected USB webcam.

• When a Raspberry Pi 4 client user plays RTAV video at high resolution, the frame rate (FPS) of the video is low due to the limited CPU and memory of the client device.

  Workaround: None

Remote Sessions

• H.264 does not work for some versions of Stratodesk NoTouch.

  The H.264 video codec does not work on client systems running some versions of the Stratodesk NoTouch operating system. By default, some Stratodesk releases use KMS for the graphics mode, instead of FKMS.

  Workaround: Configure the system to use FKMS. Go to Configuration > Services > Raspberry Pi and set Graphics Mode to Fkms. Reboot the system to save your changes.

• FIDO2 limitation on Raspberry Pi with Stratodesk NoTouch.

  FIDO2 authentication does not work when using H.264 codec in full-screen mode on a RaspBerry Pi running Stratodesk NoTouch.

  Workaround: Exit full-screen mode to use FIDO2 authentication.

• System Tray redirection functionality is not supported.

  System Tray redirection functionality is not supported, so you cannot exit a remote application session using the system tray.

  Workaround: Use the remote application’s UI to end the application session. For example, to exit a Skype session, select the Settings icon and then select File > Exit.

• You cannot start an application from the Application Launcher because the launcher is unsupported.

  Workaround: Start the remote application via the Linux client’s UI.

• System hangs may occur when using remote applications from a client system running Stratodesk.

  Workaround: Reduce the GPU memory to 128 MB. For example, in Stratodesk running on a Raspberry Pi, go to Configuration > Services > Raspberry Pi and change GPU memory (MB) to 128.

Miscellaneous

• .Net-based smart card authentication does not support TLS 1.3.

  Workaround: None.

• Issues when client system runs pcsc-lite version 1.5.

  Smart card removal policy may not work, logging off, shutting down or resetting a Windows remote desktop may result in a black screen, or the Horizon Client menu may become blank for about 10 seconds when a user has smart card sessions to multiple desktops and the user disconnects from one desktop.

  Workaround: Upgrade to pcsc-lite 1.7.4 or later.

• When a remote desktop is reconnected, Powermic Speechmic does not work with DMO 2022.2.

  When a remote desktop is reconnected after being disconnected, Powermic device does not work with dictation on DMO 2022.2. This happens when using a USB split and RTAV solution.

  Workaround: Use DMO 2021.4 instead.

• If you use a PulseAudio sound system, you might hear static when setting the volume using guest system volume slider.

  Workaround: Use the Linux client system’s volume slider or use ALSA audio by adding

  sound.backendType = alsa
  

  to either the ~/.omnissa/config or the /etc/omnissa/config configuration file.

• Horizon Client crashes upon connecting to a remote desktop.

  This known issue occurs under the following conditions:

  • Horizon Client is running on an Ubuntu 20.04 system with Intel Ice Lake or later hardware, and
  • Session protocol is Horizon Blast with HEVC 4:4:4 encoding

  The Intel media driver that ships by default with Ubuntu 20.04 contains a bug that causes Horizon Client to crash. Later versions of the driver contain a fix for this bug.

  Workaround: Update the Intel media driver by installing the latest version of

  intel-media-va-driver-non-free
  

Before You Begin

Note: The supported systems listed below and in the Horizon Client for Linux Guide pertain to the Horizon Client for Linux that Omnissa makes available. In addition, several Omnissa partners offer thin and zero client devices for Horizon deployments. The features that are available for each thin or zero client device, and the operating systems supported, are determined by the vendor and model, and the configuration that an enterprise chooses to use. For information about the vendors and models for these client devices, see the Omnissa Compatibility Guides.

• Horizon Client for Linux has been tested and is supported on the following 64-bit operating systems if you use the installer provided by Omnissa:
  • Debian 12.11, 13.0
  • Ubuntu x64 22.04.5, 2404.5
  • Red Hat Enterprise Linux (RHEL) 8.10, 9.6, 10
• Horizon Client for Linux is supported on Raspberry Pi 4 Model B devices running Stratodesk NoTouch Operating System, with some limitations. The supported Horizon Client features include Omnissa Horizon Blast Extreme, Integrated Printing, USB redirection, Real-Time Audio-Video (RTAV), and H.264 decoding (for one monitor at resolution equal to or lower than 1920 x 1080).
• Horizon Client for Linux is supported with the latest maintenance release of the following deployment types:
  • Omnissa Horizon 8 version 2006 and later
  • Omnissa Horizon Cloud Service - Next-Gen
  • Horizon Cloud in Microsoft Azure
• To install Horizon Client for Linux, download the installer from the Horizon Clients download page.
• Horizon Client for Linux does not ship with the GTK+ library, but it does use the library installed on the host system. Make sure your system is up to date with a version of the library that includes fixes for publicly reported security vulnerabilities. A list of the publicly reported security vulnerabilities, and the versions affected, for GTK+ can be found at https://www.cvedetails.com/vulnerability-list/vendor_id-666/GTK.html.
• For information about the features that are supported in nested mode, see Omnissa Knowledge Base (KB) article 67248, “Horizon Guidelines for Nested Mode.”

For more system requirements and detailed installation instructions, see Horizon Client for Linux Guide.

Information for Distribution Partners

The following deployment instructions and information about library dependencies are provided for Omnissa distribution partners. These instructions describe how to deploy Horizon Client for Linux and individual Horizon Client components using tar.gz packages.

For instructions on how to install Horizon Client for Linux using the .deb or .rpm installer file, see Installing Horizon Client for Linux.

Deployment Instructions

1. Download the Omnissa-Horizon-Client-Linux-YYMM-x.x.x-yyyyyyyy.tar.gz file from the Horizon Client downloads site and extract the contents of the downloaded tar.gz package to your system, where YYMM is the marketing version number, x.x.x is the internal version number, and yyyyyyyy is the build number.

2. Navigate to the folder for your CPU instruction set architecture. You will find additional tar.gz packages for individual Horizon Client components. For example, in the x64 folder you will find the following tar.gz packages for Horizon Client.

   Omnissa-Horizon-Client-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
   Omnissa-Horizon-PCoIP-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
   Omnissa-Horizon-serialportClient-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
   Omnissa-Horizon-USB-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
   Omnissa-Horizon-scannerClient-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
   Omnissa-Horizon-integratedPrinting-YYMM-x.x.x.yyyyyyyy.x64.tar.gz
   Omnissa-Horizon-html5mmr-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
   Omnissa-Horizon-fileAssociation-YYMM-x.x.x-yyyyyyyy.x64.tar.gz

Use the following deployment instructions for each of the tar.gz packages.

Horizon Client for Linux

The Omnissa-Horizon-Client-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz package contains the Horizon Client binaries. Use the following instructions as a guide for configuring the Horizon Client binary files.

The Omnissa-Horizon-PCoIP-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz package contains the mandatory binaries used by both display protocols, PCoIP and Horizon Blast. Use the following instructions as a guide for configuring the Horizon Client display protocol files.

1. Extract the Omnissa-Horizon-Client-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz package.
2. Navigate to the extracted folder, Omnissa-Horizon-Client-YYMM-x.x.x-yyyyyyyy.ARCH. Move the contents of the usr folder to the /usr folder. Depending on your particular Linux environment, you can choose to use a folder different from /usr.
3. Extract the contents of the Omnissa-Horizon-PCoIP-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz package.
4. Navigate to the extracted folder, Omnissa-Horizon-PCoIP-YYMM-x.x.x-yyyyyyyy.ARCH, and copy the contents of the usr folder to the /usr folder. Depending on your particular Linux environment, you can choose to use a folder different from /usr.

Note: To keep the attributes intact, use the -a option of the cp command when copying the files from lib folder.

USB Redirection

The Omnissa-Horizon-USB-YYMM-xxx-yyyy.ARCH.tar.gz package contains the binaries used by the USB Redirection feature.

1. Extract the contents of the Omnissa-Horizon-USB-YYMM-xxx-yyyy.ARCH.tar.gz package.

2. Navigate to where the package was extracted and copy the extracted folders to the recommended system folders.

   • Copy the contents of the usr folder to the /usr folder.

   • Copy the contents of the etc folder to the /etc folder.

   • Create symbolic links for horizon-USBArbitrator using the following command:

     sudo ln -s /usr/lib/omnissa/horizon/usb/horizon-USBArbitrator /usr/bin/horizon-USBArbitrator
     

3. Configure the USB Redirection feature, using the following example for an Ubuntu system as a guide.

Ubuntu example for USB Redirection

1. Set up USB arbitrator daemon in the system’s auto-startup script using one of the following methods, where # refers to 2, 3, 4, or 5, depending on your system’s run level.

   • Create symbolic links using the following command:

     sudo ln -s /etc/init.d/horizon-USBArbitrator /etc/rc#.d/S50horizon-USBArbitrator
     

   • Add /etc/init.d/horizon-USBArbitrator start in your system’s /etc/rc.local file. Make sure /etc/rc.local has the executable permission.

2. Automatically stop the USB arbitrator daemon before a system reboot or halt using the following command, where # refers to 0 or 6, depending on your system’s run level.

   sudo ln -s /etc/init.d/horizon-USBArbitrator /etc/rc#.d/K08horizon-USBArbitrator
   

3. Manually start, stop, or restart the USB arbitrator daemon when necessary using the following command:

   sudo /etc/init.d/horizon-USBArbitrator [start|stop|restart]
   

Serial Port Redirection

To install the Serial Port Redirection feature, see the README file included in the Omnissa-Horizon-serialportClient-YYMM-x.x.x.yyyyyyyy.ARCH.tar.gz file, which is available with the Omnissa-Horizon-Client-Linux-YYMM-x.x.x-yyyyyyyy.tar.gz file that you downloaded earlier from the Horizon Client downloads site.

Scanner Redirection

To install the Scanner Redirection feature, see the README file included in the Omnissa-Horizon-scannerClient-x.x.x.yyyyyyyy.ARCH.tar.gz file, which is available with the Omnissa-Horizon-Client-Linux-YYMM-x.x.x-yyyyyyyy.tar.gz file that you downloaded earlier from the Horizon Client downloads site.

Integrated Printing

To install the Integrated Printing feature, see the README file included in the Omnissa-Horizon-integratedPrinting-x.x.x.yyyyyyyy.ARCH.tar.gz file, which is available for download from the product downloads site.

HTML5 Multimedia Redirection

To install the HTML5 Multimedia Redirection feature, see the README file included in the Omnissa-Horizon-html5mmr-x.x.x-yyyyyyyy.ARCH.tar.gz file, which is available for download from the product downloads site.

File Type Association

To install the File Type Association feature, see the README file included in the Omnissa-Horizon-fileAssociation-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz file, which is available with the Omnissa-Horizon-Client-Linux-YYMM-x.x.x-yyyyyyyy.tar.gz file that you downloaded earlier from the product downloads site.

Building Dependencies

The following libraries are required for building and running Horizon Client for Linux.

• gcc 6.4 or later

The following environment variables are required for building Horizon Client for Linux with the Seamless Window feature.

• export VIEW_LIBCRTBORA=1

After you install the Horizon Client components, locate the /bin directory in the Horizon Client package that you extracted earlier. From that bin directory, run the horizon-client-lib-san script, which checks the build dependencies.

Microsoft Teams Optimization and HID Features

To configure the Teams Optimization and HID-compliant features on a thin client, perform the following steps using an administrator account.

1. On the thin client, modify the /etc/hosts file by adding the following entry:

   127.0.0.1 view-localhost
   

2. Set the correct access mode on libwebrtc_sharedlib.so as follows:

   chmod +755 /usr/lib/omnissa/horizon/vdpService/webrtcRedir/libwebrtc_sharedlib.so
   

3. To configure the HID-compliant features, create a file named horizon_hid.rules and add the following entries to it:

   SUBSYSTEM=="usb", MODE="0666"
   KERNEL=="hidraw*", MODE="0666"
   

4. Copy the horizon_hid.rules file to /etc/udev/rules.d.

5. Reload the udev rules as follows:

   sudo udevadm control --reload-rules && sudo udevadm trigger
   

Documentation

Horizon Client for Linux documentation is in the Omnissa Information Hub.

Localized Content for Omnissa Docs

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

Note: To have the client user interface use Simplified Chinese characters, set the client system to use the zh_CN locale. If you set the client system to use the zh_SG locale, the user interface is displayed in English characters.

Support Contact Information

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

For information on filing a support request in Customer Connect and via Cloud Services Portal, see Omnissa Knowledge Base article 6000005.

Original source

Check for additions and updates to these release notes.

With Horizon® Client™ for Mac, you can access remote desktops and published applications from your Mac with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).

IMPORTANT NOTICE: Changes to Support Lifecycle Dates

Effective with Horizon Client version 2606, the End of Availability (EOA), End of General Support (EOGS), and End of Technical Guidance (EOTG) milestones for this client changed from the previous policy to the policy shown below.

Note: The support policy for versions before 2606 remains unchanged.

Milestone Previous Policy Policy from 2606 Onwards EOA / EOGS GA + 36 months GA + 18 months EOTG EOGS + 12 months EOGS + 12 months (unchanged)

What’s New

• Horizon Client for Mac 2606 is released in conjunction with Horizon 8 2606.
• Multi-instance SAML connectivity: Users can connect to multiple Horizon production environments across three or more regions simultaneously using SAML authentication.
• Multi-pod simultaneous sessions: Users can now connect to and maintain simultaneous sessions with desktops across multiple Horizon 8 pods, when using URI-based launch workflows, enabling concurrent access to VMs in different pods.
• Horizon Client for Mac now supports the Microsoft Teams shared surface feature in the MKS rendering layer. This update enables overlay rendering for Teams video call experiences—including meeting reactions, spotlighting, and collaborative annotations—during remote desktop sessions accessed through the Mac client.
• Mac Horizon Clients Gain FIDO2/WebAuthn Redirection Support for UWP Apps

The Horizon Client for Mac now supports FIDO2 (WebAuthn) redirection for UWP applications running inside the remote session. This enhancement brings the Mac Client to feature parity with the Horizon Windows Client, enabling end-user authentication scenarios such as signing into the new Outlook for Windows (UWP) and Microsoft Teams through secure and seamless FIDO2 device usage directly inside the virtual desktop.

• Blast Networking - Open SSL 3.5 Upgrade

Horizon components have been updated to use OpenSSL 3.5, replacing the previous OpenSSL 3.0.x libraries which are approaching end of life. This includes the Blast Secure Gateway (BSG) for both Connection Server and Unified Access Gateway (UAG).

Before You Begin

• Horizon Client for Mac requires a macOS Sonoma (14.x), macOS Sequoia (15.x), or macOS Tahoe (26.x) operating system running on a 64-bit Intel-based Mac or ARM-based Mac.
• Horizon Client for Mac 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
• To install Horizon Client for Mac, download the disk image file from Omnissa Customer Connect. For system requirements and installation instructions, see the Horizon Client for Mac Guide.
• Beginning with Horizon Client for Mac 2006, Virtual Printing (also known as ThinPrint) is not supported. Use Horizon Integrated Printing instead.

Limitations

This release may not work with existing Nuance and Imprivata integrations.

Resolved Issues

• AST-11503: Users unable to launch Horizon VDIs after upgrading Horizon client to version 2512
• AST-15953: URL redirection issue with published app that launches Epic EMR

Known Issues

Displays and Keyboards

• Teams Optimization

  When using the Omnissa Horizon Client for macOS with an R0 Teams account, the Notepad application flickers continuously after being shared in a Microsoft Teams meeting. The entire shared application viewport flickers throughout the session. This issue occurs only when Teams Optimization is active.

  Workaround: None.

• Flickering Headers for MSTeams

  Under MS Teams optimization, the sharing of browser applications like Chrome or Edge from an RDSH/VDI environment can lead to header flickering. This is a visual disruption that is also visible to Mac clients.

  Workaround: None.

• Desktop stops responding when you connect to a remote desktop with the Blast display protocol

  When you connect to a remote desktop with the Horizon Blast display protocol from a Mac client system that has an NVIDIA GeForce GT 755M graphics card, the desktop stops responding.

  Workaround: None. This is a third-party issue.

• Auto-fit does not work for the remote desktop if you change the display to full resolution.

  If you launch a remote desktop with the PCoIP display protocol in full-screen or window mode on an iMac with a Retina or monitor that supports a 5K display, and the screen size is more than 4K (4096 x 2160), auto-fit does not work for the remote desktop if you change the display to full resolution.

  Workaround: None. This problem is caused by a PCoIP limitation.

• Remote desktop does not start if you start a remote desktop with the Horizon Blast display protocol in full-screen or window mode

  If you start a remote desktop with the Horizon Blast display protocol in full-screen or window mode on an iMac that has a Retina display or a monitor that supports a 5K display with Full Resolution mode, and then disconnect and reconnect with the PCoIP display protocol, the connection fails and the remote desktop does not start.

  Workaround: This problem is caused by a PCoIP limitation. Change to Normal mode and use the PCoIP or Horizon Blast display protocol.

Smart Card Authentication

• Some .net smart cards fail to authenticate to Connection Server over a TLS 1.3 connection

  Some .net smart cards do not support the RSA-X-509 mechanism, which is required by TLS 1.3. To determine if your smart card supports RSA-X-509, run the command pkcs11-tools --module xxx -M.

  Workaround: Use TLS 1.2 to connect to the Connection Server.

• TokenD support for physical smart cards does not work

  TokenD support for physical smart cards does not work well with macOS Catalina 10.15.4 and later.

  Workaround: Use CTK instead, or modify the following option to enable TokenD support:

  #sudo defaults write /Library/Preferences/com.apple.security.smartcard Legacy -bool true
  

• Client might not verify smart card’s PIN during server authentication when the smart card PIN is cached

  With the IDPrime .Net card, when the SafeNet Authentication Client middleware is installed, you can view or change the smart card’s cache type. If the cache type for the IDPrime .Net card is “Normal Cache,” the client might not verify the smart card’s PIN during server authentication when the smart card PIN is cached.

  Workaround: Change the Cache Type to “Always Prompt” for the IDPrime .Net card. This setting enables the client to verify the smart card’s PIN each time the user connects to the server.

• Horizon Client might stop responding when you connect to a server that has a valid root-signed certificate

  If you set the Horizon Client security preference (Horizon Client > Preferences > Security) to Do not verify server identity certificates and connect to a server that has a valid root-signed certificate, Horizon Client might stop responding.

  Workaround: Unplug the smart card reader and then plug it back in.

• Smart card authentication issues

  On macOS 10.15 or later, if you are using a TokenD driver, the Keychain Access app does not refresh when you unplug and re-plug in a smart card/smart card reader, and the Mac client cannot obtain the update status for the smart card. Because of this issue, the following problems might occur in Horizon Client on macOS 10.15 or later:

  • Smart card authentication does not work after you unplug and re-plug in a smart card/smart card reader.
  • Smart card redirection might not work after you unplug and re-plug in a smart card/smart card reader several times.
  • The Disconnect user sessions on smart card removal option in Horizon Console does not work.
  • The smart card removal policy on the agent machine might not work.

  Workaround: Switch to the CryptoTokenKit driver on macOS 10.15 or later. If you want to continue using the TokenD driver, for the smart card authentication issue, quit both Keychain Access and the Horizon Client app, relaunch Horizon Client, and perform smart card authentication again, making sure that Keychain Access is not launched. For the smart card redirection issue, reboot the Mac client machine, launch Horizon Client, and perform smart card authentication again, making sure that Keychain Access isn’t launched. There is no workaround for the smart card removal policy issue with a TokenD driver.

Touch Bar

• Focus for the front window is lost when switching between published applications that are hosted on Windows Server 2016

  You might lose focus for the front window when you use the Touch Bar to switch between published applications that are hosted on Windows Server 2016. This problem can also occur when you press Command+~, or click the dock icon, to switch windows. This problem typically only occurs after switching windows several times.

  Workaround: Use the mouse to click the window and regain focus.

USB Redirection

• System Extension Blocked error

  When you start the USB service on a macOS 10.15 or later system, the System Extension Blocked dialog box appears.

  Workaround: Click OK in the System Extension Block dialog box, navigate to System Preferences > Security & Privacy, and allow the extension to load.

• Connecting password-protected storage devices might not work correctly

  If you use the PCoIP display protocol, connecting some password-protected storage devices (such as IronKey USB flash drives) might not work correctly. For example, after you redirect the device to the remote desktop, the password prompt does not appear. The remote desktop shows that a new drive was added and so displays a new drive letter but no corresponding label to identify the device.

  Workaround: Configure Horizon Client to automatically connect the device when you insert it. From the Horizon Client menu bar, select Desktop > USB > Autoconnect USB Devices on Insert.

• Files that you copy or move to the drive do not appear on the drive when using the USB redirection feature

  If you use the USB redirection feature to connect a Transcend USB 3.0 external hard drive to a remote desktop from your Mac client system, files that you copy or move to the drive do not appear on the drive after you disconnect the drive from the remote desktop.

  Workaround: Redirect the external hard drive to the remote desktop again. The files appear on the drive.

• Agent unreachable error

  When you connect to a Windows remote desktop, start USB services, redirect a USB storage device to the remote desktop, disconnect from the remote desktop, and then try to reconnect to the remote desktop, either USB services are not available in the remote desktop or you cannot reconnect to the remote desktop. In Horizon Console, the state of the machine is Agent unreachable.

  Workaround: If you are an end user, restart Horizon Client and try again. If you are a Horizon administrator, restart Horizon Agent in the machine.

• Desktop connection is sometimes disconnected when the USB “Automatically connect at startup” setting is enabled

  After you connect to a remote desktop with the USB Automatically connect at startup setting enabled, the desktop connection is sometimes disconnected.

  Workaround: None.

Miscellaneous

• .NET-based smart card authentication does not support on TLS 1.3.

  Workaround: Use TLS 1.2 for .NET cards.

• Launching applications from a second CPA disconnects the existing session

  If you first connect to a pod in a Cloud Pod Architecture (CPA1) and launch an application, you can open multiple applications within CPA1. If you then launch an application from a different pod (CPA2), a new session is created for CPA2. When you attempt to open an additional application from CPA2, the existing CPA2 session is disconnected.

  Workaround: None.

• Scanner property ‘Black and White’ Option is blocked on Mac OS version 13.5.2 with Horizon Scanner Redirection

  Workaround: Use a Mac OS version other than version 13.5.2. See KB 95187.

• Moom user interface does not work

  The Moom user interface does not work for UWP published applications.

  Workaround: None.

• Cannot start a Omnissa App Volumes application

  You cannot start a Omnissa App Volumes application from the Dock on the client system.

  Workaround: Start the application from Horizon Client, or use a shortcut.

• Horizon Client for Mac stops responding

  Horizon Client for Mac stops responding if you unplug an external graphics processing unit (GPU).

  Workaround: None.

• Moom UI does not appear when you hover your mouse over the Maximize icon

  With Moom 3.2.12 (3240), the Moom UI appears when you hover your mouse over the Close icon, not the maximize icon, in Office 2016 and 2019 apps.

  Workaround: None.

• Response time of Windows Server 2016 hosted remote applications is slow

  On late 2016 MacBook Pro client systems, the response time of Windows Server 2016 hosted remote applications is slow in the first few seconds after you launch a Windows Server 2016 application or switch the top window between Horizon Client and the Windows Server 2016 application window.

  Workaround: None. This is a third-party issue.

• Cannot log in to the same server as a different user when “Remember this password” is selected

  If you select the Remember this password check box when you log in to a server, you cannot log in to the same server as a different user if the credential caching timeout period (clientCredentialCacheTimeout) on the server has not yet expired. Horizon Client will automatically use the saved credentials to log you in to the server.

  Workaround: Remove the server from the Selector window (right-click the server icon and select the Delete menu item), click the Add Server button to add the server again, and then log in to the server as the different user.

• Unexpected results can occur if you edit an application pool in Horizon Console and change the path to point to a different application

  If an administrator edits an application pool in Horizon Console and changes the path to point to a different application that already has an application pool associated with it, unexpected results can occur. For example, the original application might be launched from the Mac Dock instead of the new application.

  Workaround: Make sure that each application in a farm is associated with only one application pool.

• Changes to webcam and audio devices are not detected

  Changes to webcam and audio devices that are connected to, or disconnected from, the Mac client system during a remote desktop session are not detected by the Real-Time Audio-Video feature.

  Workaround: Disconnect and reconnect to your remote desktop session to detect webcam and audio device changes. For example, if you connect a USB headset to the Mac client system during a remote desktop session and you want to use that headset on the remote desktop, you must disconnect and reconnect to the remote desktop session to make the headset available.

• Screen-share of Microsoft Teams as RDSH application shows desktop wallpaper only

  When you screen-share an RDSH application session of Microsoft Teams, only the desktop wallpaper appears in the screen-share preview and the recipient’s screen-share. The application window and desktop icons are not displayed. This issue occurs when Horizon Client is not enabled to record screen contents.

  Workaround: Go to the macOS system settings. Under Screen & System Audio Recording, enable Horizon Client to record the content of your screen and audio.

Documentation

Horizon Client for Mac documentation is in the Omnissa Information Hub.

Localized Content for Omnissa Docs

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

Support Contact Information

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

For information on filing a support request in Customer Connect and via Cloud Services Portal, see the Omnissa knowledge base article at https://kb.omnissa.com/s/article/2006985.

Original source

This page contains release-related information for Horizon Client for Chrome 2606, which enables users to connect to and use remote desktops and published applications using a Chromebook, a Chromebox, or a device running ChromeOS Flex.

This page is revised periodically as needed with information about the release. Check back regularly for additions and updates to these release notes.

IMPORTANT NOTICE: Changes to Support Lifecycle Dates

Effective with Horizon Client version 2606, the End of Availability (EOA), End of General Support (EOGS), and End of Technical Guidance (EOTG) milestones for this client changed from the previous policy to the policy shown below.

Note: The support policy for versions before 2606 remains unchanged.

Milestone Previous Policy Policy from 2606 Onwards EOA / EOGS GA + 36 months GA + 18 months EOTG EOGS + 12 months EOGS + 12 months (unchanged)

What’s New

Horizon Client for Chrome 2606 is released in conjunction with Horizon 8 2606.

• Enhanced WebRTC media redirection: Video background blur and image replacement features use the MediaPipe Selfie Segmentation model to segment the video background.
• Blast Networking - Open SSL 3.5 Upgrade
  Horizon components have been updated to use OpenSSL 3.5, replacing the previous OpenSSL 3.0.x libraries which are approaching end of life. This includes the Blast Secure Gateway (BSG) for both Connection Server and Unified Access Gateway (UAG).

Before You Begin

• Horizon Client for Chrome requires ChromeOS 75 or later.
• Horizon Client for Chrome 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
• Install and upgrade Horizon Client for Chrome just as you do any other Chrome app. You can get the latest version of the app from the Chrome Web Store.
• For system requirements and installation instructions, see the Horizon Client for Chrome Guide.

Limitations

This release may not work with existing Zoom, Cisco, Nuance, and Imprivata integrations.

The following features are not supported when you use this release of Horizon Client for Chrome with a Horizon Cloud Service - next-gen deployment:

• Workspace ONE integration
• Windows 365 and reverse connect transport
• Unified Access Gateway failover
• Resumption of remote applications
• Kiosk mode for the client

Resolved Issues

There are no resolved issues in this release.

Known Issues

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

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

• Unexpected Page Displayed in Chrome Client When Accessing UAG with Third-Party SAML IDP

  When using the Chrome Client to access the UAG with a third-party SAML IDP, users may encounter an unexpected page displaying a Client Selection prompt for Chrome Native Client, ARC ++ Client, or HTML Access.

  Workaround:

  • Click "Launch Native Client". Do not select "Check here to skip this screen and always use Native client.”
  • Use HTML Access.

• Printer property ‘Un-Collated’ is not taking effect in Win11 VDI and RDSH 2019/2022 under Printer Redirection.

  Workaround: None.

• Chrome Client fails to add default XPS printer driver in a Windows 11 virtual desktop

  After you install a Windows 11 agent and start the desktop on a Chrome client, no client printers are added when you check the printer list.

  Workaround: In Programs and Features ->Turn Windows features on or off, select Microsoft XPS Document Writer to turn on. Make sure two drivers are available:
  Printer Microsoft XPS Document Writer and the driver is Microsoft XPS Document Writer v4 Printer Microsoft Print to PDF and the driver is Microsoft Print to PDF

Display and Multimedia

• For a specific type of Chromebook, Acer ARM Chromebook Spin 513, when the Chrome Client enables RTAV H.264 codec, the VDI camera video stream is fuzzy.

• The Media Optimization for Microsoft Teams feature becomes unavailable after a network interruption occurs on the Horizon Client session.

  Workaround: For details, see KB article 85761.

• After dragging certain apps to a small monitor, the app might have a strange boundary on Horizon Client for Chrome.

  This issue only appears when Chromebook has a very high DPI or an extended monitor has a small resolution. An example condition would be Chromebook with 4K (3840) screen in 213% DPI scale + small extended monitor (1920) in 100%. An example app could be a calculator that is not resizable.

  Workaround:

  You can make the following changes:

  • Enable High Resolution.
  • Change to a larger extended monitor. A 2560 screen will resolve the issue in most of cases.
  • For Chromebook, set the display scale to lower DPI (smaller font and icon).

• H.264 decoding does not work in this release.

  The setting to enable H.264 decoding has been removed from the Horizon Client user interface.

  Workaround: None.

• During a Teams audio call with the Media Optimization for Microsoft Teams feature enabled, no alert message appears when the user speaks with the microphone muted.

  Workaround: None.

• When sharing the screen during a Teams video call with the Media Optimization for Microsoft Teams feature enabled, if the client user locks and then unlocks the Chrome OS, the screen share and outgoing video stop working.

  Workaround: None.

• When the client user minimizes the remote desktop window during a Teams screen-sharing session with the Media Optimization for Microsoft Teams feature enabled, the screen-share contents turn black.

  Workaround: None.

Smart Card Authentication

• You may see the following problems after authenticating with a smart card:

  • If you enter an incorrect PIN, log off from the server, and then immediately log in to the server again, you are prompted for Active Directory authentication.
  • If you log off from a session and then log in to the server again, the server fails to authenticate with smart card authentication.
  • If your published application session is idle and times out, and you unplug and then reinsert your smart card reader, you are not prompted for your PIN when you try to connect to a published application.

  Workaround: Log off or restart the Chromebook and log in with the smart card again.

• If you enter an incorrect PIN during smart card authentication, Charismathics does not present any direct feedback in the dialog box.

  Workaround: This problem is a third-party issue. For more information, go to https://support.google.com/chrome/a/answer/7014689.

Documentation

Horizon Client for Chrome documentation is in the Omnissa Information Hub.

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 and learn about support policies, see Omnissa Customer Connect.

For information on filing a support request in Customer Connect and via Cloud Services Portal, see the Omnissa knowledge base article at https://kb.omnissa.com/s/article/2006985.

Original source

Horizon Web Client 2606 | 24 AUG 2026

This page is revised periodically as needed with information about the Horizon Web Client 2606, 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 Client for Web Client 2606 is released in conjunction with Horizon 8 2606.
• The maximum clipboard size for clipboard redirection in Horizon Web Client has been increased from 1 MB to 64 MB, enabling larger copy and paste operations between the client system and remote desktops or published applications.
• New set of codecs have been introduced in the Horizon Web Client, along with a new client setting for selecting preferred codecs. For Horizon 8, the new codecs are enabled by default with BlastCodec preferred, while for Horizon Cloud Service (HCS), end users must enable the codecs themselves. Together with BlastCodec, the new codecs deliver improved graphics performance and efficiency for browser-based desktop sessions. Note that the new codecs are incompatible with the on-ramp feature. If your users need to use the on-ramp feature, administrators should set enableBlastCodec=false in the properties file when installing the 2606 environment.
• Tenant administrators can now disable Horizon Web Client access for specific tenants from the administrator console. This new capability provides greater control over end-user access methods in multi-tenant Horizon deployments, enabling organizations to restrict browser-based client access where policy requires it.
• Blast Networking - Open SSL 3.5 Upgrade
  Horizon components have been updated to use OpenSSL 3.5, replacing the previous OpenSSL 3.0.x libraries which are approaching end of life. This includes the Blast Secure Gateway (BSG) for both Connection Server and Unified Access Gateway (UAG).

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 2606 supports Horizon Agent 2606.
• 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 2606 and Horizon 8 version 2606, 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 issues 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:
  1. Use mmc to import the CA-signed certificate into the Windows certificate store.
  2. 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.
  3. 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.
  1. Choose Apple menu > System Preferences.
  2. Click General.
  3. 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 via Cloud Services Portal, see the Omnissa knowledge base article at https://kb.omnissa.com/s/article/2006985.

Original source

Horizon Cloud | 14 August 2026

Horizon Agents Installer (HAI) version 26.1.0-31670512777 | 14 AUG 2026

Horizon Edge Gateway version 2603.2.0 | 01 JUL 2026

Check periodically for additions and updates to these release notes.

Horizon Cloud is a multi-cloud Desktop as a Service deployment with thin edge infrastructure. The service provides you with a global view of your desktops and applications spanning on-premises and cloud environments. Regardless of the location of your desktop and application deployments, Horizon Cloud enables you to consistently manage and monitor them.

These Horizon Cloud release notes detail the new features and enhancements in each release. The release notes also provide other information about Horizon Cloud such as limitations, known issues, and support contact information.

Support for new features depends on your specific infrastructure and capacity providers.

August 14, 2026 - HAI Update

A new build of the Horizon Agents Installer (HAI) version 26.1.0-31670512777 is now available. This HAI version addresses a deadlock in Horizon Windows agent that prevents end users from connecting to their virtual desktop. The following agent versions are included in the Horizon Agents Installer:

• Horizon Agent: 8.18.0-31663763437
• Dynamic Environment Manager Agent: 10.19.0.2389
• App Volumes Agent: 4.21.0.5081

Original source

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

Omnissa Workspace ONE Content Gateway Container 2606 | 11 AUG 2026

What’s New

• Ability to upload trust certificate from dux to connect to external systems. For more information, see Adding CA Certficate Files.
• Security improvements and vulnerability fixes.

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.

Resolved Issues

We are always working to improve Content Gateway Container with every release. There are no major bug fixes to report.

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 2606 | July 31 | Build 4.22.0.161

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.

What’s New - 2606

Custom Package Lifecycle Stages

Provides the ability to define, build, and reorder stages for aligning lifecycle management processes. For example, Approved could be added after Tested, and before Published.

App Volumes Agent On-Demand Download Progress for Local Copy Mode

Introduces a download progress dialog for packages delivered in local copy mode, giving end users real-time visibility into application delivery.
With prior releases, users had no visibility to download status. The new Windows-native dialog lets users pause, resume, or cancel a package download in progress, reducing confusion and help-desk tickets during app delivery.

User Sentiment for Local Copy Mode

Brings sentiment feedback to local copy mode, matching the capability already available for virtual delivery. After using an application, end users can submit a thumbs up or down along with optional comments.
Admins and application owners can then view sentiments by package and application, giving teams a direct feedback channel.

Smart Card Login for App Volumes Manager

Adds smart card authentication support for App Volumes Manager. This capability helps organizations authenticate users with physical identity assurance media.
It removes the extra step of requesting time-bound temporary passwords for administrators who authenticate without Active Directory credentials.

CVE Reporting for Applications and Packages (Technical Preview)

Maps application packages and versions to publicly known vulnerabilities, surfacing severity and CVSS scores from sources including NVD, CISA, and OSV.
App owners can view and prioritize which applications need attention first and factor vulnerability risk into staging and delivery decisions.
For more information about this feature, see Omnissa Beta Program.

App Volumes and Workspace ONE Intelligence with Experience Management (Coming Soon)

Sends App Volumes health, performance, and operational data to Workspace ONE Intelligence with Experience Management, delivering centralized visibility into application delivery and platform health.
Administrators can proactively identify issues, monitor service reliability, and accelerate troubleshooting with insights into package activity, attachment performance, failures, and overall environment health.
Support for the upcoming Experience Management dashboard will be available soon.

Resolved Issues

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

• [AVM-47039] A failed SyncIntegrationsJob can block subsequent synchronization requests initiated from an App Voumes integration (in the App Volumes Admin UI, Infrastructure → Integrations), thus preventing new integration synchronization jobs from getting scheduled and running successfully.
• [AVM-46951] App Volumes Manager is unavailable after a failed Rails console session when the Windows Integrated Authentication for SQL Server is the database connection method chosen during App Volumes Manager installation.
• [AVM-46820] A database migration failure might occur when upgrading to App Volumes 2512 and the following error is logged at C:\Program Files (x86)\CloudVolumes\Manager\log\svmanager_setup.log : CREATE UNIQUE INDEX terminated because a duplicate key was found…. This issue causes the upgrade to fail.
• [AVM-46677] App Volumes Manager reports the following database error Volume access mode is not included in the list, in the System Messages tab within the App Volumes Manager admin UI, when a new computer record is created during App Volumes agent startup.
  This error occurs because App Volumes Manager is unable to detect in which package access mode (shared storage or local copy) the App Volumes agent is installed on the computer. As a result, computer-based application assignments are not attached to the computer.
• [AVM-46349] Certificate validation fails after SSL certificate regeneration on the target App Volumes Manager instance. This issue occurs because the source instance retains the previously accepted certificate. This mismatch causes certificate validation to fail, resulting in communication failure between the source and target instances.
  Note: Clicking the Certificate button on the source instance does not retrieve the newly generated certificate — it continues to display the outdated certificate.
• [AVA-28474] The PowerShell Cmdlet fails to launch an App Volumes MSIX package application, when using a Launch ID with the Run-AppVolumesApp command.
• [AVA-28332] App Volumes Application Capture Command-Line Program (appappcapture.exe) fails when using the appcapture.exe convert command to convert an App-V application package to an App Volumes VHD or VMDK application package.
• [AVA-28262] When capturing an application in the MSI format using the App Volumes Application Capture Command-Line Program (appcapture.exe), the MSI file does not get created whereas the VHD and JSON files are created successfully. This issue occurs because an invalid product version is generated for the application.
• [AVA-28258] An Invalid License Key warning dialog is seen, when any App Volumes agent version currently installed in Standalone mode, without an App Essentials license key, is upgraded to App Volumes agent 2603.1 using the App Essentials license key. Regardless of this warning dialog, the upgrade is successful and the App Essentials license key is also successfully updated.
• [AVA-28172] When a Windows endpoint installed with App Volumes Agent in local copy mode synchronizes with App Volumes Manager for the first time, applications get downloaded to the endpoint only after a reboot.
• [AVA-28046] App Volumes Direct installation fails when using the App Essentials license for install and the following error occurs: The License Key entered is invalid. Verify the format and ensure it matches the provided License Key. License Keys are 35 characters long and formatted as XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX.
• [AVA-28036] Some issues occur when using App Volumes-packaged MSIX applications due to a race condition between App Volumes and an OS operation. The issues are as follows:
  • In a Horizon RDSH session, the MSIX applications might fail to launch with the following error: Windows cannot access the specified device, path, or file.
  • In a Dependency or Install Order Application Relationships scenario, if an MSIX application is the base or the first application, then as per the expected behavior, the MSIX application must virtualize first followed by the dependent or the second application respectively. Instead, the dependent or the second application might get virtualized even before the MSIX application. Neither relationship type is honored.
    Note: For Dependency, the expected behavior is when the base application fails to virtualize, then virtualization of the dependent application also fails.
• [AVA-27990] Unexpected folders such as Omnissa and VMware Tools might appear in the same location as the captured package.
  Note: You can ignore these folders as they do not affect the captured package.
• [AVA-27476] Applications such as Google Chrome Portable (installed per user) display a blank window or an “Aw, Snap!” error at first launch when using a UIA+profile Writable Volume.
• [AVA-21872] When a Windows endpoint installed with App Volumes Agent in local copy mode synchronizes with App Volumes Manager for the first time, applications get downloaded to the endpoint only after a reboot.

Known Issues

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

• [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-28409] An application configured for delayed download gets automatically downloaded when this application is in a Dependency or Install Order relationship with other applications, which are configured for automatic download.
  For more information about delayed download, see the Assign an App Volumes Application to an Entity section in the App Volumes Administration Guide at Omnissa Product Documentation.
• [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 Dynamic Environment Manager offers personalization and dynamic policy configuration across any virtual, physical, and cloud-based environment. Dynamic Environment Manager can simplify end-user profile management with a single and scalable solution. IT can simply map infrastructure (including networks and printer mappings) and dynamically set policies for end-users. You can experience quick, personalized, and consistent access to your Windows workspace and applications. Dynamic Environment Manager provides a secured by default approach by logging the users out in case the Flex config files path is not available at logon.

Omnissa Dynamic Environment Manager Release Notes provide information about the new features and enhancements in each release. This page contains a summary of the new capabilities, issues resolved, and known issues that are reported in each version.

What’s New

• Condition – AD Username. Introducing a User Name condition for targeting policy assignments to specific Active Directory users. See Managing Conditions.
• Entitlement-Based Filtering in DEM Self-Support Tool. The Self-Support Tool now supports condition-based filtering for auto-start shortcuts. See Configuring Dynamic Environment Manager Self-Support to Allow Managing Auto-Start Shortcuts.
• Support Bulk Delete for Personalization Configuration Files. The Multi-select Delete capability in the Management Console now also applies to personalization configuration files. When Multi-select Delete is enabled, you can configure a Delete Limit to set the maximum number of files that can be deleted in a single operation. This limit applies across all configuration file types. See Managing DEM Management Console.
• Updated Components. This release updates the main product components. Application Profiler, Helpdesk Support Tool, and SyncTool are not updated.

Resolved Issues

Note

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

• DEM-902: “Run once” does not work for user environment settings in silo-based non-DirectFlex config files

  If the Run once option is selected for a user environment setting configured in a non-DirectFlex configuration file in a silo, Error determining whether DEM setting should be applied - DEM path '\domain\share\silos...' does not start with Flex config files path '\domain\share\general' is logged at run-time. Because the run-once status of the setting cannot be determined, it is applied every time.

  This issue is resolved in this release.

• DEM-1175: “Run once” does not work for user environment settings in non-DirectFlex config files when SyncTool is used

  If SyncTool is used and the Run once option is selected for a user environment setting configured in a non-DirectFlex configuration file, Error determining whether DEM setting should be applied - DEM path 'C:\Users...\AppData\Local...\FlexSync...' does not start with Flex config files path '\domain\share\general' is logged at run-time. Because the run-once status of the setting cannot be determined, it is applied every time.

  This issue is resolved in this release.

Known Issues

Note

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

• DEM-188: New Microsoft Teams does not trigger DirectFlex processing

  Launches of the new Microsoft Teams are performed by the AppInfo service. In older versions of Dynamic Environment Manager, AppInfo starting a DirectFlex-enabled executable triggered DirectFlex processing. With the default DEM configuration, this behavior does not exist.

  Workaround: To enable the old behavior, set REG_DWORD value DirectFlex to 2 in the HKLM\SOFTWARE\Immidio\Flex Profiles key (for Group Policy-based setups), or in the HKLM\SOFTWARE\Omnissa\DEM\Agent\Configuration key (for NoAD).

• DEM-724: COM servers do not trigger DirectFlex processing

  In older versions of Dynamic Environment Manager, instantiating an out-of-process COM object hosted by a DirectFlex-enabled executable triggered DirectFlex processing. With the default DEM configuration, this behavior does not exist.

  Workaround: To enable the old behavior, set REG_DWORD value DirectFlex to 1 in the HKLM\SOFTWARE\Immidio\Flex Profiles key (for Group Policy-based setups), or in the HKLM\SOFTWARE\Omnissa\DEM\Agent\Configuration key (for NoAD).

Note

To enable the workarounds of DEM-188 and DEM-724 at the same time, DirectFlex must be set to 3.

• DEM-725:

  • Cannot display button text on some Asian versions of Windows operating systems

    On some Asian versions of Windows operating systems, the button text in the Management Console, the Application Profiler, and the Helpdesk Support Tool might be missing.

    Workaround: Specify the /NoScale command-line argument when you start the Management Console, Application Profiler, and the Helpdesk Support Tool.

  • Button text truncated on some Asian versions of Windows operating systems

    On some Asian versions of Windows operating systems, the button text in the Self-Support Tool is truncated if a German Multilingual User Interface is used.

    Workaround: No workaround exists for this issue.

Documentation

Documentation for Omnissa Dynamic Environment Manager is located at Omnissa Product Documentation.

Internationalization

Dynamic Environment Manager content is available in English, Simplified Chinese, and Japanese. For details on Omnissa’s localization strategy, see the knowledge base article Announcing Omnissa Localization Support.

Support Contact Information

To receive support, access Customer Connect. For information about filing a Support Request in Customer Connect and using Cloud Services Portal, see the Knowledge Base (KB) article 6000005.

Original source

Omnissa ThinApp accelerates application deployment and simplifies application migration by isolating applications from their underlying operating systems to eliminate application conflict and streamline delivery and management.

ThinApp 2412 Release Notes lists New features, Resolved Issues, and Known Issues for this release.

What’s New

Branding Update: New Logo and Splash Screens

Omnissa ThinApp has a new logo and updated splash screens as part of our transition to Omnissa.

Licensing

With the 2412 release, Omnissa ThinApp is implementing a new license key format. Customers can download the new license key from the license portal.

Resolved Issues

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

• When using Windows Update KB5025221 and later, some of the ThinApped virtualized applications fail due to an access violation exception. A new parameter is introduced to fix this issue. For more information, see the Omnissa ThinApp Package.ini Parameters Reference Guide. [TAPP-28]
• When using Windows Update KB5025221 and later, some ThinApped virtualized applications fail due to the change in the Windows CopyFile API behavior. [TAPP-30]

Known Issues

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

• Unable to install ThinApp 2412 on Windows 7 due to license key validation failure. [TAPP-146]

• ThinApp 64-bit packages fail to run on Windows 11 24H2 machines. [TAPP-141]

• A COMDLG32.dll error appears when applications are run from a network share.
  Workaround: Add ProcessExternalNameBehavior=Original and SetVirtualModuleFileNameInPeb=1 to the General Parameters section of the Package.ini and rebuild the package.

• When 64-bit version of Microsoft PowerPoint 2010 or Microsoft Word 2010 on Windows 10 is started, a “Fatal Application Exit” error occurs.
  Workaround: Add the ChildProcessEnvironmentException=msiexec.exe in Package.ini and build the project.

• When a website is marked as favorite in Internet Explorer, the website is not seen immediately in the Favorites Bar.
  Workaround: Create ##Attributes.ini file in the %Common Favorites% folder with the following content and rebuild the package:

  [Isolation] DirectoryIsolationMode=WriteCopy
  

• Visual Studio 2010 displays the following error message:
  Invalid license data. Reinstall is required on launch.
  Workaround: None

• When you start AutoCAD on 64-bit versions of Windows 7, the following error message is displayed:
  PresentationFontCache.exe - Application Error
  Workaround: None

• If you replace the Outdir parameter in Package.ini with any of the following language characters: Simplified Chinese, Traditional Chinese, Japanese, and Korean, ThinApp fails to build packages on the 32-bit versions of Windows 7.
  Workaround: None

• If you attempt to start two instances of Microsoft Word 2013 or Microsoft Power Point 2013, these applications become unresponsive.
  Workaround: None

• Microsoft Visio 2010 fails to start when deployed to Windows 10 1803.
  Workaround: None

• Microsoft Visio 2010 help files are not displayed on 64-bit versions of Windows.
  Workaround: None

• Microsoft Office 2010 and Microsoft Office 2013 fail to start when deployed to a system with Microsoft Office natively installed.

• If Protected View is enabled in Microsoft Excel 2013, Excel fails to open files from a network share.
  Workaround: Disable protected view from File > Options > Trust Center > Trust Center Settings > Protected View > Enable Protected View for files located in potentially unsafe locations.

• Internet Explorer 6.0 does not open some specific URLs.
  Workaround: Add the following parameters to Package.ini and rebuild the package:

  [BuildOptions] NotificationDLLs=T2embed.dll
  

• Unable to insert Office objects in certain Microsoft Office applications such as Excel charts in Excel, Word document in Word, PowerPoint, and so on.
  Workaround: None

• LibreOffice does not shut down correctly on the 64-bit version of Windows 8.1
  Workaround: Add the following parameter in the General Purpose Parameters section in the Package.ini file and rebuild the package:

  [BuildOptions] ReleaseShutdownLocksEarly=1
  

• Virtual Internet Explorer 11 fails during shutdown after Internet Explorer 11 security patch KB 4056568 has been applied.
  Workaround: Add the following parameter in the General Purpose Parameters section in the Package.ini file and rebuild the package:

  [BuildOptions] ForceTerminateThread=1
  

• Not able to start Google Chrome from a network share.
  Workaround: Add SetVirtualModuleFileNameInPeb=1 to Package.ini and rebuild the package.

• ThinApp cannot change registry key names on 32-bit versions of Windows.
  Workaround: None

Documentation

• For more information about Omnissa ThinApp, see the Omnissa ThinApp User’s Guide.
• For more information about how to configure and customize the ThinApp Package.ini parameters, see the Omnissa ThinApp Package.ini Parameters Reference Guide.

Omnissa ThinApp Documentation is available at Omnissa Product Documentation.

Internationalization

ThinApp content is available in Japanese.

To switch to a different language, click the language icon and select your preferred language.

Support Contact Information

To receive support, access Customer Connect.

Alternately, to file a Support Request in Customer Connect and via Cloud Services Portal, you can use the information presented in this KB article.

Original source

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

Omnissa App Volumes 2212.7 includes bug fixes.

What’s New

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

Resolved Issues

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

• If it is not possible to determine the Active Directory site from an IP address or subnet, a default Active Directory site is not set. This might result in App Volumes Manager contacting Domain Controllers out of its (App Volumes Manager’s) Active Directory site. [AVM-28680]
• Application packages and Writable Volumes cannot be attached to instant-clone desktop pools which have the Add vTPM Device to VMs option selected in the Horizon Console. [AVM-31057]

For more information about the Add vTPM Device to VMs option, see the Windows Desktops and Applications in Horizon 8 documentation.

For more information about the Virtual Trusted Platform Module (vTPM), see the vSphere Virtual Machine Administration documentation.

• After enabling the Mount ESXi option in the Machine Managers page and when saving this setting, the following error is visible in the App Volumes Manager admin UI: Failed to connect n of n hosts host1.com host2.com hostn.com [AVM-31066]
• After moving to another datastore, a Writable Volume loses delete protection. As a result, the Writable Volume might get accidentally deleted from the datastore. [AVM-31094]
• Refresh Volume background job fails and the following error is seen in the App Volumes admin UI System Messages tab: Refresh Volume #<Thread:ID_number run> Validation failed: Snapvol has already been taken. This error occurs when the Refresh Volume job tries to create the capture OS (packaging machine) record for a package whereas the OS record is already present in the App Volumes Manager database but is not marked as a capture OS. [AVM-31233]
• When SSL verification for an App Volumes target instance happens through a cacert.pem file present in the config directory where App Volumes Manager is installed, the following error is displayed: Error while retrieving the certificate. Unable to find the certificate for the target manager instance. After a while, the error is not visible. [AVM-31353]

NOTE: This is a UI display issue and causes no functional impact.

• Published applications on demand are not delivered at application launch when a user is assigned both on demand and classic delivery mode applications when logged into an RDSH server. [AVA-21686]
• Google Chrome icon is not visible until after the application is virtualized when the application package is delivered as on-demand [AVA-21543]
• When a handle is created or opened before virtualization started in an agent computer which has a Profile-only Writable Volume and application packages as attachments, memory leak and increased handle count is observed. This issue of memory leak and increase in handle count can impact the performance of the Profile-only Writable Volume. [AVA-21549]
• Simulated shortcuts of on-demand packages cannot be stored and reused. These shortcuts are deleted after package attachment and before virtualization. As a result, when end users launch the stored, simulated shortcut after a package is attached to the agent computer, the following message is displayed App delivery failed. Unable to deliver the application at this time. Please try again later. [AVA-21555]
• Software Protection service fails to work when FSLogix 2.9.8440.42104 is installed on an agent computer running App Volumes 2212 and later and affects some of the attached application packages. As a result, these applications do not work correctly. [AVA-21594]

Known Issues

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

• After upgrading from App Volumes 2203.2, cached static files prevent the loading of UI elements within App Volumes Manager admin UI. [AVM-30954]

Workaround: Clear the cache of your browser and load balancer.

• Applications packaged on Windows 11 are shown as packaged with Windows 10 and applications packaged on Windows server 2019 and Windows server 2022 are shown as packaged with Windows server 2016 in App Volumes Manager admin UI. [AVM-29123]
• App Volumes Manager installation fails with the following error: Unable to install App Volumes Manager with region language (Control Panel setting) except English when the language setting on the virtual machine is Arabic. [2884143]

Workaround: Change the language to English and then install App Volumes Manager.

• “new Microsoft Teams” which is installed in the base image, launched, and updated successfully by the user with a UIA+profile Writable Volume at the first login fails to launch at the second login onwards with the same UIA + Profile writable. This failure occurs because unexpected registry entries are captured in the Writable Volume. [AVA-24024]

Workaround: Customize the base image by adding the following exclusions in custom\snapvol.cfg:

exclude_registry=\REGISTRY\MACHINE\Software\Classes\PackagedCom
exclude_registry=\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\ms-teams.exe
exclude_registry=\REGISTRY\MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\ms-teamsupdate.exe

When the user having the same Writable Volume logs into the agent computer which has the updated based image, new MS Teams launches successfully.

• “new Microsoft Teams” application fails to launch when Profile-only or UIA+profile Writable Volume is attached to the agent computer.

Note: When this issue occurs, no error message is displayed by the application. [AVA-23756]

• Running the change logon command on an RDS host does not work when application packages or Writable Volumes are attached to the RDS host. Status of the RDS host machine is not updated in the Omnissa Horizon console. [AVA-23264]

Workaround: Add the following in the custom snapvol.cfg file:

exclude_registry_value_path=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\WinStationsDisabled.

• End users with a Writable Volume experience an increase in the login time if there is a difference in the registered MOF (Managed Object Format) entries between the base virtual machine and the Writable Volume. [AVA-23247]
• When an App Volumes application package or Writable Volume includes a printer specification and the memory integrity feature is enabled, Windows crashes at startup. [AVA-23138]

Memory integrity is a virtualization-based security (VBS) feature. This feature is sometimes referred to as hypervisor-protected code integrity (HVCI). For more information about this feature, see the relevant Microsoft documentation.

• After the Windows update of “September 12, 2023—KB5030219 (OS Build 22621.2283)” on a VM with either an application package or Writable Volume attached, Windows start menu and search do not respond. [AVA-23022]

Workaround: Create the file “%SVAgent%\Config\Custom\Snapvol.cfg” on the base image with the following content:

exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\PolicyManager\default

• An application assigned to an RDS server using App Volumes Manager is not listed in the Horizon Console. As a result, a Horizon administrator is unable to create an application pool with the application assigned to the RDS server. [AVA-20887]

Workaround:

1. On the RDS server where agent is installed, locate the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\svdriver\Parameters, create a REG_DWORD value OverrideSkipHzWsnmAppScanCalls, and set the value to 1.
2. Restart the RDS server.

• If a VMDK of an application package contains a square bracket, ‘[‘, the package does not get imported to App Volumes. As a result, the package is not listed in the Inventory tab of the App Volumes Manager admin UI. [3034059]

Workaround: Rename the VMDK and import the package again.

• 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 not 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. [3006443]
• 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. [3072078]
• Applications cannot write large string values (several hundred thousand characters) to the registry. [3034063]
• 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. [2791414]

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

• 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. [2624048]

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.

• 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. [2845852]

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")

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

Workaround: Retry the move or copy operation.

Omnissa 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.

Alternately, 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