Omnissa Release Notes

Horizon Client for Chrome 2603 | 14 APR 2026

This page contains release-related information for Horizon Client for Chrome 2603, 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.

What’s New

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

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 Report a problem

Horizon Client for iOS 2603 | 14 APR 2026

The Horizon Client for iOS allows you to connect to and use remote desktops and published applications from an iOS-based device such as an iPhone or iPad.

What’s New

• Access to cloud-based entitlements in Omnissa Workspace ONE mode

This release supports access to Omnissa Horizon Cloud Service - next-gen desktops and applications in Workspace ONE mode, which an administrator can enable in Horizon Universal Console. In this mode, users must use Workspace ONE Intelligent Hub to connect to the Horizon Cloud Service - next-gen portal and open desktop and application sessions. Users cannot open desktops and applications directly from Horizon Client, ensuring that conditional access policies in Omnissa Access are enforced.

This feature is only available when both Horizon Client for iOS and Horizon Web Client are updated to version 2603.

Before You Begin

Horizon Client for iOS is supported with the following deployment types:
Enhanced external keyboard features require Connection Server and Horizon Agent version 2111 (8.4.0) or later.

• Horizon 8 2006 and later
• Horizon Cloud in Microsoft Azure
• Horizon Cloud Service - next-gen
• Horizon Client for iOS requires iOS 18.x, iPadOS 18.x, iOS 26.x, and iPadOS 26.x
• Install and upgrade Horizon Client for iOS just as you do any other iOS app, by going to the Apple Store. For a link to the Horizon Client app in the Apple Store, go to the Omnissa Customer Connect page.
• For system requirements and installation instructions, see the Horizon Client for iOS Guide.

Resolved Issues

• AST-11503: Users unable to launch Horizon VDIs after upgrading Horizon client to version 2512

Known Issues

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

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.

Navigation

• Remote application icon does not appear in the Unity Touch sidebar

  When High Resolution Mode is enabled and you run certain remote applications (such as Notepad), the icon of the remote application does not appear in the Unity Touch sidebar and a default image appears instead. This problem occurs only with Horizon Agent 7.1 and earlier.

  Workaround: None.

Input Methods

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

• Unity Touch sidebar cannot show changes in the All Programs menu

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

  Workaround: In order to see items for new software that you just installed, disconnect from the desktop and then connect again.

• Shift key in the top row of the onscreen keyboard

  The Shift key in the top row of the onscreen keyboard or in the navigation keys is for entering key combinations, such as Ctrl+Shift. If you need to capitalize a letter or type an exclamation point (!) or question mark (?) or another symbol that you create by using the Shift key, use the up arrow as you would in the standard onscreen keyboard.

  Workaround: None.

• Onscreen keyboard input does not immediately switch between native iOS apps and Horizon Client in Split View mode

  Onscreen keyboard input does not immediately switch between native iOS apps and Horizon Client in Split View mode. For example, if an iOS native app is on the right side of Split View mode and a Horizon Client remote application is on the left side of Split View mode and you input data in the iOS native app, when you click in the remote application, your input goes to the iOS native app instead of to the remote application.

  Workaround: Click another point to change the cursor position. The onscreen keyboard input is switched correctly.

• Keyboard input does not work

  When you connect to a Linux desktop, some keyboard input does 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: Set the English IME on the client device and set the non-English IME on the remote desktop.

• Keyboard shortcut bar appears at the bottom of the screen

  When you connect to a remote desktop from an iPad, the keyboard shortcut bar appears at the bottom of your screen.

  Workaround: To dismiss the shortcut bar, open the iPad Settings app, tap General, tap Keyboard, and toggle off the Shortcuts option.

Connectivity

• iPhone, iPad, and Android clients consume one per device license each for PCoIP and MS RDP instead of one for both

  When you connect to an RDS (Remote Desktop Session) desktop with the PCoIP display protocol, a license is issued to your iOS device. If you later connect to the same RDS desktop with a third-party app that uses RDP (such as Microsoft Remote Desktop), a second license is issued to your iOS device. This problem occurs because PCoIP and RDP record different names for your device on the license server. For example, if your iPhone is named Jane’s iPhone, PCoIP records the name as JANES-IPHONE and RDP records the name as Jane-s-iPhone.

  Workaround: None.

Display and Multimedia

• Incompatibility with Picture-in-Picture

  Horizon Client for iOS does not work with the iOS Picture-in-Picture feature.

  Workaround: None

• External monitor mirrors the entire screen instead of showing only the remote desktop or application

  If you launch Horizon Client on the right side of Split View mode, connect to a remote desktop or application, and then enter presentation mode, the external monitor mirrors the entire screen (touchpad and desktop or application) instead of showing only the remote desktop or application. This is a third-party issue.

  Workaround: Move Horizon Client to the left side of Split View mode.

Audio and Video

• Displayed frame is mirrored in left-right direction in some apps

  When a camera on the client device is redirected with the Real-Time Audio-Video (RTAV) feature, the preview is mirrored in the left-right direction in some apps.

  Workaround: None.

• Horizon Client exits unexpectedly

  Occasionally, Horizon Client exits unexpectedly during a long video meeting.

  Workaround: None.

Documentation

Horizon Client for iOS 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 Report a problem

Horizon Web Client 2603 | 14 APR 2026

This page is revised periodically as needed with information about the Horizon Web Client 2603, 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 2603 is released in conjunction with Horizon 8 2603.

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 2603 supports Horizon Agent 2603.
• 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 2603 and Horizon 8 version 2603, 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 Report a problem

Horizon Client for Mac 2603 | 14 APR 2026

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

What’s New

Horizon Client for Mac 2603 is released in conjunction with Horizon 8 2603.

• MID Parameter in F5 Webtop URI

Added support for the MID parameter in F5 Webtop URI launches to the Horizon Client for Mac, matching Horizon Client for Windows behavior.

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 Report a problem

Horizon Client for Android 2603 | 14 APR 2026

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.

What’s New

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

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

AST-11503: Users unable to launch Horizon VDIs after upgrading Horizon client to version 2512

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 Report a problem

Horizon Client for Windows 2603 | 14 APR 2026

With Horizon® Client™ for Windows 2603, 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).

What’s New

Horizon® Client™ for Windows 2603 is released in conjunction with Horizon 8 2603.

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.

• AST-7637: Client is slow during Microsoft Teams screen sharing
• AST-9024: URL redirection not working in client 2503 and later
• AST-11503: Users unable to launch Horizon VDIs after upgrading Horizon client to version 2512
• AST-14437: URL redirection issue after upgrade to Horizon Client 2506.2
• VCART-7979: SDR Redirection Fails with ‘Unsupported in this session’ Error in one of the clients on RDSH
• VCART-10202: Client crashes during video conference with high number of participants
• VCART-10316: Client crashes when using multiple RDSH apps and/or overlays
• VCART-11024: Blast connection fails when RSA-PSS is configured on client

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 Report a problem

Horizon Client for Linux 2603 | 14 APR 2026

This page contains release-related information for Horizon Client for Linux 2603, 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 2603 is released in conjunction with Horizon 8 2603.

MID Parameter in F5 Webtop URI

Added support for the MID parameter in F5 Webtop URI launches to the Horizon Client for Linux, matching Horizon Client for Windows behavior.

Resolved Issues

This release includes fixes for the following:

• AST-15953: URL redirection issue with published app that launches Epic EMR
• AST-11503: Users unable to launch Horizon VDIs after upgrading Horizon client to version 2512
• AST-6880: Client is slow on connect when using DP to HDMI adapters

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, 24.04.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

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.

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

Extract the Omnissa-Horizon-Client-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz package.

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.

Extract the contents of the Omnissa-Horizon-PCoIP-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz package.

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.

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

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

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

Ubuntu example for USB Redirection

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.

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

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.

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

127.0.0.1 view-localhost

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

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

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"

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

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 Report a problem

Horizon 8 2603 | 14 APR 2026

Build: 8.18.0-24169897839

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

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

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.

Important lifecycle milestones:

Horizon 2512 is the last release that supports vSphere 7.x.

Horizon 2603 ESB will not support vSphere 7.x.

Action Required: You must upgrade to vSphere 8.x or 9.x by 2603 ESB to remain fully supported.

What’s New

Horizon Connection Server

This release introduces next preferred site logic in CPA to improve routing when a site is full. Instead of random fallback, admins can now define a preferred site order. CPA will follow this order to select the next available site, providing more predictable routing, better performance, and improved load balancing.

Administrators can create published applications delivered by unmanaged manual pools.

Horizon now gathers entitlements across pods that are not federated. This gives users a single view of desktops and applications from both on-premises and hosted environments through the Horizon Client.

The SAML Metadata feature enables administrators to configure Security Assertion Markup Language (SAML) authentication settings at the Cloud Pod Architecture (CPA) level. This functionality provides centralized control over SAML metadata distribution, certificate management, and entity identification across multiple pod deployments within your Omnissa environment.

Connection Server now supports uploading elliptic curve (EC) certificates for the “vdm” certificate when compatible cipher suites are configured.

Horizon Console

Added support for Windows Integrated Authentication (IWA) for MS SQL Event Databases in Horizon 8, removing the need to store or rotate DB credentials. Admins can choose SQL Authentication or IWA directly in the Horizon console. Username/password fields are hidden when IWA is selected. PostgreSQL 17 for Event DB is also supported in this release.

This release adds a new interface in the Horizon Console for managing Global SAML Authenticators. This allows administrators to view, create, change, and manage authenticators and their connected Connection Servers from one place.

An option to Copy from Golden Image for network selection during Nutanix pool and farm workflows is now available.

Post-synchronization and power-off scripts can be specified during Nutanix pool and farm workflows.

This release improves accessibility across the Horizon Console with enhanced keyboard navigation, screen reader support, focus handling, contrast, and form labeling to better align with WCAG 2.2 AA guidelines.

The Horizon Console now displays basic health information for UAGs registered with the Connection Server, including service status and gateway certificate health, providing essential infrastructure visibility.

Enhanced security by preventing exposure of database passwords in the Recording Server UI and API responses. Added masked display and improved password handling across configuration workflows.

Added the ability to search unassigned VMs and support custom filters in the Advanced Filter modal.

Administrators can now enable Workspace ONE UEM management directly from the Horizon Console when creating non-persistent desktop pools, as support for persistent desktop pools is already available. This enhancement extends Workspace ONE UEM across physical devices, mobile endpoints, and Horizon VDI, delivering a unified Day-2 management experience through a single console. The integration ensures consistent policy application from day one, simplifies operations, enhances compliance and security, and reduces total cost of ownership.

Horizon Agent for Linux

Horizon now supports VM names longer than 15 characters for Linux VDI desktop pools, removing previous naming‑pattern limits. Windows VDI continues to support a maximum of 15 characters.

Added support for the MATE desktop environment on Red Hat Enterprise Linux (RHEL) 8.x and 9.x for Horizon Linux virtual desktops.

The Horizon Linux Agent now uses an isolated, agent‑specific smart card service (pcscd-horizon) instead of overwriting the system /usr/sbin/pcscd, ensuring safe coexistence with the OS smart card service and improving system stability.

Added support for Debian 12.13, Debian 13.3, and Rocky 9.7.

Updated NVIDIA vGPU Support: Horizon Agent 2603 adds support for NVIDIA vGPU versions 16.13, 18.6, 19.4, and 20.0.

Horizon Agent for Windows

The Horizon Windows Agent now includes a Blast system tray icon for desktop sessions. This icon provides at-a-glance visibility into the session experience, including network connection quality, and serves as a convenient entry point for Blast-related session information. An administrative policy (Blast System Tray) is available to disable the icon if needed.

Added support for end users to immediately disconnect from a remote desktop or application session by pressing the Ctrl+Alt+F12 keyboard shortcut. This feature is disabled by default. Administrators can enable it through the viewClient.enableSessionDisconnectHotKey setting.

Improved IP address selection logic in the Horizon Windows Agent to prioritize routable IPv4/IPv6 pairs for Blast connections, eliminating failures caused by non-routable interfaces (example, Internal Hyper-V NICs) without requiring additional configuration.

Updated NVIDIA vGPU Support: Horizon Agent 2603 adds support for NVIDIA vGPU versions 16.13, 18.6, 19.4, and 20.0.

Remote Desktop Features

Horizon now introduces Enforced Identity Consistency, a security enhancement that ensures only the entitled user who launches a desktop or published application can log in to that session even when Single Sign-On (SSO) is unavailable. For details on how to configure it, See GPO “Restrict Logon To Entitled Horizon Users Only” under Agent Configuration Policy Settings.

Some performance enhancements from previous releases are now extended to support BSG.

This release improves Universal Broker by allowing you to create Pool Groups that contain Horizon 8 RDSH farm desktops directly from the Horizon Cloud Universal Console. By synchronizing RDSH farms and enhancing integration with the Control Plane, you can more seamlessly incorporate multi-session resources, optimize resource utilization, and manage hybrid environments from a central location.

Added support for URL Content Redirection in Workspace ONE mode.

Windows OS Optimization Tool for Omnissa Horizon

Added support for using the OSOT SCCM plugin to streamline integration with SCCM and simplify task sequence creation and deployment workflows. The plugin is supported on Windows 11 24H2 and Windows 11 25H2.

Added support for using a custom unattend.xml during sysprep in SCCM task sequences, allowing configuration of language, locale, time zone, user accounts, and other Windows setup parameters. This replaces the default Apply Windows Settings step.

Added support for using a task sequence import script to streamline OSOT deployment and automate task sequence configuration.

Resolved Issues

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

AST-6712: Horizon attempts to reconnect user with session “already used”

AST-7962: Blast crashes and prevents user from reconnecting to their session

AST-11503: Users unable to launch Horizon VDIs after upgrading Horizon client to version 2512

HZN-4903: Admin user is unable to login to admin console after stale entries remain for local custom role in global database

HZN-6021: User lookup and Machines Tab Takes Extremely Long Time or Time-Out

HZN-6250: Users unable to connect to Application pool associated with App Volumes application when no local AVM assignment is present for user

HZN-6785: Events are not displayed correctly in Horizon Admin console

HZN-6912: Pool Power policy of power off after logoff is not working due to COLLISON

HZN-6964: Registered machines can be deleted when pools exist.

HZN-7229: TrueSSO login is being triggered even though the Password cache option is enabled on WS1 and TrueSSO mode is disabled on WS1

HZN-7357: Horizon console only lists 100 home site user assignments, whereas the report pulled shows 151 user assignments

HZN-7386: Custom icon associated with Published application gets removed if the application is edited

HZN-7416: Horizon recorded assignment to dedicated systems changed from readable username to GUID

HZN-7492: Connection Server returns false Horizon Client compatibility Error due to improper supportedFeatures validation

HZN-7591: NVIDIA machines not added to a vCenter-managed, manual desktop pool

HZN-7599: Idle timeout is sending a logoff before sending a stopAWS API call

HZN-7633: Section under “System Health” in one of the horizon pods says “ESX Hosts”. However, when attempting to expand this, there is no information, and an error message about “Internal server error” pops up

HZN-7833: After upgrading Horizon 2406 -> Omnissa Horizon 2512, internal Connection Servers no longer display any AD/domain accounts in the Admin Console when domains are excluded from Connection Server

HZN-7991: The Horizon weekly backup schedule is set to perform backups at midnight on Sunday instead of midnight on Saturday

HZN-7995: Intermittently observing error “An internal server error occurred” while assigning a manual desktop to a user

HZN-8041: In Horizon Admin Console Remote Access page will not load for over 30 minutes

HZN-8088: The Activate > Term/Perpetual button opens the license entry modal without switching the system’s license mode from SUBSCRIPTION to PERPETUAL_ONLY. As a result, term license activation fails

HZN-8091: Unable to add new application from the existing farms. When adding application, the drop-down list shows no RDS hosts with an error “Internal Error Occurred“

HZN-8132: If a user is not entitled to the pool but assigned to a dedicated VDI, there is a pop-up box mentioning the user is not entitled to the pool and an error message

HZN-8134: Refresh fails after a user logs off. According to the logs from both CSs, commitRequests sometimes conflict, resulting in a VoteAbort for both

HZN-8178: Adding vms with L2 gpu profile “VM is on a host that doesn’t support NVIDIA GRID vGPUs or the vGPU type”

HZN-8179: Users added from secondary domain are not listing under Desktop Pool > Policy Override tab is stuck on a spinning wheel

HZN-8196: Outfit variable font used in Horizon admin console is displayed incorrectly in Firefox running on Windows 2019 and Windows Server 2016

HZN-8275: Ad user or groups get by ids api required for assign users flow for machines

HZN-8283: Installer fails when attempting to upgrade from 2506 -> 2512.1

HZN-8361: Creation of an instant clone desktop pool is failing

HZN-8382: Admin UI fails to load after upgrading Horizon Connection Server from 2506 to 2512.1

VCART-7428: Scheduling an upgrade for an RDS host may complete successfully, but the upgrade itself can fail when the scheduled time is reached.

Known Issues

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

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

Horizon Connection Server

HZN-5160: Sorting and filtering capabilities have been removed for specific columns in administrative grids. This results in a loss of functionality compared to previous releases and may impact administrative workflows.

Workaround: None

HZN-7443: If a VM is stuck in Customization state, delete the VM from Horizon Admin Console or Horizon REST API. Horizon will then recreate the VM.

When there are more than ten global dedicated entitlements available to a user, the machine host name will sometimes not be visible in global entitlements if the “Show assigned host name” option is enabled.

Scheduling an upgrade for an RDS host may complete successfully, but the upgrade itself can fail when the scheduled time is reached.

Workaround: See KB article 6000992.

If Horizon Events Database is hosted by an instance of Microsoft SQL Server (any version), do not disable TLS 1.2. This connection cannot be made over TLS 1.3.

HZN-2542: When changing the browser locale and refreshing the Horizon Console UI, error alerts fail to display for the newly selected language.

Workaround: Log in to Horizon Console in a new browser tab.

HZEC-2336: View API consumers like the MP4H Adapter invoke MachineDetailsView. This API fails intermittently with user data not found error.

Workaround: None

HZEC-2873: Number of issues reported for ESXi Hosts in the dashboard summary may not match with number of issues reported in the dedicated ESXi Host issues section in the dashboard.

If NVIDIA vGPU support detects a mismatch with the supported vGPUs for the given host, the issue count should be incremented but the count may not display in the UI.

Workaround: View the warnings in Dashboard > System Health > View > vSphere > ESX Hosts.

Horizon Agent for Windows

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.

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.

VCART-9642: Linux published applications do not support the jump list feature on Windows client systems.

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.

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.

VCART-9646: Published applications do not support the Move and Size context commands for the taskbar on Windows client systems.

VCART-9647: Published applications do not support the Size command from the application window’s context menu.

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.

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.

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.

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.

VCART-9656: When you connect to a Linux desktop, some keyboard inputs do not work.

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.

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 8 API

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

Horizon Edge and Horizon Cloud Connector

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

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

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

Horizon 8 Deployed on Public Cloud SDDCs

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

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

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

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

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

Before You Begin

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

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

To use View Storage Accelerator in a vSphere environment, a desktop virtual machine must be 512GB or smaller. View Storage Accelerator is disabled on virtual machines that are larger than 512GB. Virtual machine size is defined by the total VMDK capacity.

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

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

Compatibility Notes

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

Use of Open Source

As part of the installation process, an open_source_licenses.txt file is written to the file system. Key open-source components included in this release are:

Horizon Connection Server 2603 is built on the Apache Tomcat implementation of Jakarta EE, version 10.1.49.

Horizon Agent for Linux 2603, Horizon Agent for Windows 2603, and Horizon Connection Server 2603 all utilize the BellSoft Liberica distribution of OpenJDK, version 17.0.16.0.1 (CPU).

Documentation

Horizon 8 documentation is in the Omnissa Product Documentation portal.

Localized Content for Omnissa Docs

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

Support Contact Information

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

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

Original source Report a problem

Omnissa dux 2.2 | 12 NOV 2024 | Build 2.2.0.247

We are excited to share the new release of Omnissa dux version 2.2! Read on to learn about the new features and improvements in this release.

New Features

Download location changed

The download location for dux has changed. Navigate to the README file for more information.

• For AMD64/Intel: https://packages.omnissa.com/ws1-tunnel/dux/2.2.0.247/dux-2.2.0.247-1.x86_64.rpm
• For ARM64/Apple Silicon: https://packages.omnissa.com/ws1-tunnel/dux/2.2.0.247/dux-2.2.0.247-1.aarch64.rpm

Support localhost deployment without using SSH

For organizations that do not want to leave SSH enabled for remote administration, you can choose to leverage a hypervisor’s virtual console to do administration. In most instances, it is recommended to leave ssh enabled so dux can administer multiple hosts from a single location.

To use dux locally from the same host, specify the host information as “localhost,” the hostname, or the IP address under the “Tunnel Server Host(s) Information” section of the manifest.

Added exec-shell command to SSH directly into a container

To run Vpnreport, it may be required to directly interact with a Tunnel container. A few other improvements have been added:

• Support for defining a custom SSH port in the manifest.
• Dry run command now checks if the Tunnel container image is available at the right location.
• Fallback to interactive prompt for credentials on SSH authentication failure.

Minimum Requirements

Workspace ONE UEM Console 2410 or later

Download Instructions

Linux and Windows: dux 2.2.0.247

macOS: Use package manager brew

For new install:

brew tap wsonetunnel/tunnel
brew install dux

To update the dux version to 3.0

brew update
brew upgrade dux

Resolved Issues

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

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.

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 Report a problem

Urgent Notification regarding legacy Domain End of Service

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

Omnissa Workspace ONE Web for Android Release Notes detail the new features and enhancements in each release. This page contains a summary of the new capabilities, issues that have been resolved, and known issues that have been reported in each version.

Workspace ONE Web 26.03 - April 2026

New Features

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

Note

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

Minimum Requirements

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

Resolved Issues

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

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.

Workspace ONE Web 26.02 - March 2026

New Features

• Custom settings to suppress alerts from websites that contain untrusted resources. See Suppress alert from websites containing untrusted resource.
• Custom settings to control QR Code in Single tab mode. See Scan URL QR Codes in Kiosk Mode.
• Support for External Keyboard shortcuts. See Supported External Keyboard Shortcuts.

Note

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

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-177231: Unable to open downloaded PDF file from WS1 Web using Content app. The system unexpectedly prompts for a password.

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.

Workspace ONE Web 25.11.1 - December 2025

New Features

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

Note

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

Minimum Requirements

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

Resolved Issues

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

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.

Workspace ONE Web 25.11 - December 2025

New Features

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

Note

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

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-177045: Focus on the input element lost during page load for onLoad() JavaScript function.

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.

Workspace ONE Web 25.08 - September 2025

New Features

• Simplified navigation that makes finding key features faster and intuitive.
• Improved security and support for secure systems.

Note

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

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-176762: Automatic selection of Search/Input text field when prompted on a new page does not work.

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.

Workspace ONE Web 25.06 - July 2025

New Features

• Enhancements to UI for a modern and intuitive user experience, with a refreshed URL address bar and bottom navigation options.
• Support the “Find in Page” feature, allowing users to search for specific text within PDF documents.
• Ability to Show Notification only once. See Show Notification Prompt Once.
• Ability to disable the “Introducing Widgets” pop-up. See Allow Widgets Popup.

Minimum Requirements

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

Resolved Issues

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

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.

Workspace ONE Web 25.02.1 - June 2025

New Features

• Updated web domain to align with Omnissa branding.

Minimum Requirements

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

Resolved Issues

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

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.

Workspace ONE Web 25.02 - February 2025

New Features

• Scan QR Code in Single Tab Kiosk mode.
• Support for Password Protected PDF.

Minimum Requirements

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

Resolved Issues

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

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.

Workspace ONE Web 24.11.1 - December 2024

New Features

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

Minimum Requirements

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

Resolved Issues

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

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.

Workspace ONE Web 24.11 - December 2024

New Features

• Branding Update: App now features a new logo and splash screens as part of our transition to Omnissa.
• Ability to collecting mobile analytics data from devices via Workspace ONE Web.

Mobile Analytics is part of our Digital Employee Experience solution set. Omnissa Intelligence receives the data from UEM with additional device and application data that allows comprehensive view of device performance and the experience it delivers to end users.

• Learn how to enable collection
• Understand the device-wide data we can collect

Note

End of Support Life for Omnissa Tunnel Proxy. See the Knowledge Base article 87345.

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-176309: Scroll up action on webpage triggers Pull to refresh action on webpage.
• ABRW-176328: Cannot move within Maps, instead the Pull to refresh action is being triggered.

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.

Workspace ONE Web 24.10 - November 2024

New Features

• Allow sync by pull to refresh in Normal and Multi Tab Kiosk mode.

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-176135: Missing video recording option from App Chooser tray on Web.

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.

Workspace ONE Web 24.08.1 - September 2024

New Features

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

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-176173: SharePoint site failing to load via Web app on Android.

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.

Workspace ONE Web 24.08 - August 2024

New Features

• Allow users to clear history based on a specific time range.
• Enable WebRTC by default.

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-176035: Auto deletion of downloaded files for Web in Kiosk modes on relaunch.

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.

Workspace ONE Web 24.06 - June 2024

New Features

• Enhancements in Multi Tab Kiosk mode.
• Support for Proxy Authentication.

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-175907: Web fails to retain IA Auth credentials after kill-relaunch for the first time.

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.

Workspace ONE Web 24.02.2 - May 2024

New Features

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

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-175800: OutOfMemoryError while loading large websites in Workspace ONE Web.

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.

Workspace ONE Web 24.02.1 - April 2024

New Features

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

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-175939: Clear Cookies On Exit setting is not working on Workspace ONE Web.

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.

Workspace ONE Web 24.02 - February 2024

New Features

• Improvements to the Managed bookmark icon.

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-175750: Remove background-running instance of Workspace ONE Web after Android Mobile SSO auth.

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.

Workspace ONE Web 23.12.1 - January 2024

New Features

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

Minimum Requirements

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

Resolved Issues

Note

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

• ASDK-174983: Black screen while opening Web app on Android 13 and 14 devices.

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.

Workspace ONE Web 23.12 - December 2023

New Features

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

Minimum Requirements

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

Resolved Issues

Note

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

• ABRW-175689: Android Web app does not show actual favicon for specific Web pages on Bookmarks screen.

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.

Workspace ONE Web 23.11 - November 2023

New Features

• Custom icon for Bookmarks Ability to customize bookmark icon on device.

Minimum Requirements

• Android 9+
• Workspace ONE UEM 2203+

Resolved Issues

Note

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

• ABRW-175648: JavaScript window.close() not being called because of blocked screen.

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.

Workspace ONE Web 23.09 - September 2023

New Features

• WebRTC in Custom tabs
  Users can launch the Custom tab using their native app and take advantage of the WebRTC features like taking picture using camera, taking videos, and mic access.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM 2203+

Resolved Issues

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

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.

Workspace ONE Web 23.08 – August 2023

New Features

• App Experience - Configuration for page text zoom percentage.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM 2203+

Resolved Issues

Note

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

• ABRW-175419: App ignores web links when user relaunches the app after leaving the device idle for few hours.
• ABRW-175424: KVP to disable Rage Shake not functioning on fresh install/configuration.

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.

Workspace ONE Web 23.06 – June 2023

New Features

• Configuration for page text zoom percentage
  New Custom Setting has been introduced to set zoom percentage of text on webpage in range of 50% & 200%. Default text zoom percentage remains at 100%.
• Standardize support options across iOS and Android platforms
  Removed inconsistency for few Support screen options between iOS & Android Workspace ONE Web for Rage Shake.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM 2109+

Resolved Issues

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

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.

Workspace ONE Web 23.05 – May 2023

New Features

• User Agent modification for Web
  This implements a new user agent string for WS1 Web without any reference to Android System Webview and thus extends support to CWS integration.
• Improved Favicon fetch request to avoid failing on custom servers
  Improvised the icon fetching mechanism from custom servers.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM 2111+

Resolved Issues

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

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.

Workspace ONE Web 23.04 – April 2023

New Features

• Admin configuration to add a new Search Engine in Workspace ONE Web
  This enables the Web admins to configure additional search engines (internal or external) in the Web. The configured search engines become available to the end users in the existing list of search engines, and they can choose to use them as needed.
• Device widget for Workspace ONE Web Bookmarks
  Now users can add device widget that can list the bookmarks configured in Workspace ONE Web. This allows users to launch the Web app faster in WS1 Web directly from device’s home screen hence providing quicker to access bookmarks.
• Support for dark mode on Workspace ONE Web Android
  Workspace ONE Web now supports dark mode on Android devices.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM 2111+

Resolved Issues

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

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.

Workspace ONE Web 23.02 – February 2023

New Features

• Support Enable shift-based access control.
  This feature enables the admins to put shift based access on Web which restricts the end users to access Web application on their mobile devices if they are not in their shift hours.
• Ability to open and view PDF files in Kiosk mode.
  This feature allows user to open and view PDF files within Workspace ONE Web in Kiosk mode.
• Modify Web user-agent to work with CWS.
  This feature allows the Web admin to use a new modified user agent for Workspace ONE Web which enables the Cloud Web Security policies and restrictions to work within Web.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM 2109+

Resolved Issues

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

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.

Workspace ONE Web 22.12 – December 2022

New Features

• Support Custom tab protocol in Web
  This enables another mobile app to open Web custom tab without having to launch the complete Web app for use-cases like authentication and integrated browsing.
• Certificate selector for IA/CA into MS applications using MS Authenticator
  This enables the users to select a certificate installed by MS authenticator on the device trust store to perform integrated authentication and conditional access into the Microsoft web applications. ****

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM 2105+

Resolved Issues

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

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.

Workspace ONE Web 22.11 – November 2022

New Features

• Support Web for Samsung DEX devices
  Support for Samsung DEX devices in both mobile and desktop modes.
• Ability to add website shortcut on device home screen
  This will enable the Web end user to add shortcut for a web application/URL on the device home screen.
• Watermark support for Print option in Web
  Web can be configured to show Watermark as a DLP capability on the websites browsed so that confidential data or information exposed through Websites can be protected. With this enhancement, the watermark is retained on the page even if the user tries to print it through Web.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM Console version 2105+

Resolved Issues

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

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.

Workspace ONE Web 22.10 – October 2022

New Features

• PDF Viewing capability in Web Android for non-Kiosk mode
  Users will now be able to open and view PDF files within the Workspace ONE Web browser application without requiring a separate PDF viewer app to be installed on the device. This capability is not yet available for Kiosk mode.
• Restrict upload & download based on file type
  This will enable the admins to control upload or download actions in Workspace ONE Web based on the file type being uploaded or downloaded.
• Watermark support in DLP settings for WS1 Web
  This will enable the admins to configure showing watermark as a data loss prevention (DLP) capability on the websites opened through Workspace ONE Web to protect the confidential data or information exposed through these websites. Watermark support is not yet available when user tries to print a webpage, so print needs to be disabled to achieve complete DLP protection through watermarking.
• Bug fixes and stability improvements.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM 2105+

Resolved Issues

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

Known Issues

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

Workspace ONE Web 22.08 – August 2022

New Features

• Support user defined order for Web bookmarks
  User will now be able to reorder bookmarks as per their preference and save the order for faster access to their frequently used or favorite bookmarks
• Use first letter of bookmark title for bookmark abbreviation when there is no icon
  Web now shows first letter of the name/title of bookmark instead of the first letter of the URL, if corresponding page doesn’t have any icon associated with it
• Support for Android 13
  All the capabilities of Workspace ONE Web application are now supported on Android 13.

Minimum Requirements

• Android 13+
• Workspace ONE UEM Console version 2102+

Resolved Issues

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

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.

Workspace ONE Web 22.07 – July 2022

New Features

• Support Web standalone secure browsing with CWS
  This will enable the admins to extend the security capabilities of Workspace ONE Web application running in standalone mode by applying the web security policies configured through Cloud Web Security service.
• Enable in-app Play Store rating prompt
  This will enable the end users to rate Workspace ONE Web experience from within the application through the in-app Play Store rating prompt.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM Console 2010+

Resolved Issues

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

Known Issues

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

Workspace ONE Web 22.05 – May 2022

New Features

• Allow upload of files from Workspace ONE Content repositories
  Users will now be able to upload files/documents present in Workspace ONE Content repositories or local storage to web applications opened in the Workspace ONE Web browser.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM Console 2010+

Resolved Issues

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

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.

Workspace ONE Web 22.04 – April 2022

New Features

• Enhancements to IA certificate renewal option IA
  More intuitive messages for IA certificate renewal.
• Integrating In-App update SDK feature in Workspace ONE Web
  This feature will allow a way for the admins to configure in-app update prompt for the users who have not upgraded the Web app to the latest Play Store version on their devices.
• Option to renew IA certificate in Single app Kiosk Mode
  End user will now have an option to view and renew certificates in Kiosk mode as well.
• Support to pull Web application logs from UEM console
  This new capability allows the UEM administrator to pull the Web application logs from a device through the UEM console without involving the end user using the device.
• Support to send Web app logs to UEM
  End user will now get an option to send the Web application logs to UEM console through the new option ‘Send logs to administrator’ on the support page. This is particularly helpful in extracting logs from Web for diagnostic purposes when the Web is used in the single app mode.
• Enhanced organization and discovery of bookmarks in Web
  The search in bookmarks now work across the title and URL. And the bookmarks are now sorted by default in alphabetical manner on both the bookmark launcher home page and the bookmarks page. This will now enable users to discover the bookmarks more easily.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM Console 2010+

Resolved Issues

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

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.

Workspace ONE Web 22.02 – February 2022

New Features

• Single tab Kiosk mode configuration to hide URL bar and/or navigation controls
  This will provide admin configurations to hide URL address bar and/or bottom bar (navigation controls and home button) from Web browser in single tab Kiosk mode. This will enable the customers to provide locked down full screen experience in Kiosk mode to the frontline workers to keep them focused on the workflow or task that they are supposed to work on through the configured web applications in Kiosk mode and minimize distractions.

Minimum Requirements

• Android 8.0+
• Workspace ONE UEM Console 2010+

Resolved Issues

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

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.

Download Instructions

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

Support Contact Information

To receive support, either submit a ticket through the Customer Connect portal or call your local support line.

Original source Report a problem