|
Horizon Client for Chrome 2209.1 | 6 December 2022 |
What's New
Horizon Client for Chrome 2209.1 fixes an issue with self-signed certificates that interfered with direct connections to remote desktops.
Before You Begin
-
Horizon Client for Chrome requires Chrome OS 75 or later.
-
- Horizon Client for Chrome is supported with the latest maintenance release of Horizon 8 version 2006 and later.
-
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.
Resolved Issues
The following issues have been resolved in this release.
- A problem with the self-signed certificate prevented users from connecting directly to a remote desktop.
Users could not connect to a remote desktop directly from Horizon Client for Chrome and were required to use Unified Access Gateway as a workaround.
This issue has been fixed in this release, and users can now connect to a remote desktop directly.
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
- Display and Multimedia
- Smart Card Authentication
- Security
Display and Multimedia
- The Media Optimization for Microsoft Teams feature becomes unavailable after a network interruption occurs on the Horizon Client session.
Workaround : For details, see Omnissa Knowledge Base (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.
Security
- ChromeOS crashes when user dismisses certificate warning for remote desktop connections.
When a user attempts to connect directly to a desktop and selects Back to safety in the certificate warning that pops up, the client ChromeOS crashes.
Workaround: None
Documentation
Horizon Client for Chrome documentation is in the Omnissa Information Hub.
Localized Content for Omnissa Docs
The transition from Broadcom to Omnissa is in progress. As part of that transition, we are reviewing our localization strategy for how best to serve the needs of our customers and partners. We will be providing localized version of Omnissa Docs content again soon. Thank you for your patience.
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?