|
Horizon Client for Chrome 2203 | 05 APR 2022 |
Check for additions and updates to these release notes.
What's New
Horizon Client for Chrome 2203 includes the following new features.
- Support for URL Content Redirection
With the URL Content Redirection feature, URL content can be redirected from the client machine to a remote desktop or published application (client-to-agent redirection), or from a remote desktop or published application to the client machine (agent-to-client redirection).
- Support for Browser Redirection
With Browser Redirection, when an end user opens a website in a Chrome or Microsoft Edge (Chromium) browser in a remote desktop, the web page is rendered on the client system instead of the agent system, and it is displayed as an overlay on the remote browser's window.
- Restart and Reset Capabilities from Desktop Selector Screen
Users can restart and reset remote desktops directly from the desktop selector screen.
- Disable USB Redirection for Specific Devices
You can now filter USB redirection by release number in addition to vendor and product IDs.
- Configure File Association for Enrolled Chromebooks
The File Association feature is enabled by default. Using the Google Admin console with the enableFileAssociation JSON configuration option, you can deactivate File Association for enrolled Chromebook devices.
- Mouse Forward and Back Buttons
You can use the forward and back buttons on an external mouse to navigate the user interface in a remote desktop.
- Support for Numeric Keypads
You can use an external numeric keypad to enter input in a remote desktop.
For information about new remote desktop features, see the Omnissa Horizon 8 2203 Release Notes.
Internationalization
The user interface and documentation for Horizon Client for Chrome are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.
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 2203 and Horizon 7 version 7.5 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
- "Set Time Zone Automatically" setting fails to take effect.
The time zone of a remote desktop or application fails to synchronize with the time zone of the local cient system, even with the "Set Time Zone Automatically" option enabled in the Settings window of Horizon Client.
- Horizon Client gets stuck during authentication to the default Connection Server.
Horizon Client for Chrome cannot complete authentication to establish a connection with the default Connection Server instance. In the JSON configuration file for the Horizon Client app, under the server-list section, the default property cannot be set to "true".
Known Issues
- Display and Multimedia
- Smart Card Authentication
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 KB 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:
1. Enable High Resolution.
2. Change to a larger extended monitor. A 2560 screen will resolve the issue in most of cases.
3. 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 might encounter 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 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.
Was this page helpful?