|
Horizon Client for Chrome 2506 | 31 JUL 2025 |
This page contains release-related information for Horizon Client for Chrome 2506, 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 2506 is released along with the Horizon 8 2506 release.
For information about new remote desktop features, see the Horizon 8 2506 Release Notes.
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 major issue resolutions to report 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 launch 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.
Was this page helpful?