VMware Horizon Client for Chrome 2206 Release Notes

VMware Horizon Client for Chrome 2206 | 19 JUL 2022

Check for additions and updates to these release notes.

What's New

Horizon Client for Chrome 2206 includes the following new features.

Enhanced support for touch gestures
This release includes the following enhancements:
- Touch gestures are supported in multiple-monitor mode.
- Users can scroll in a remote session using one or two fingers. Scrolled content moves in the same direction as the user's fingers.
Improved support for Google Admin policies
When users start Horizon Client for Chrome from the VMware Workspace ONE catalog using a URI, the client honors the configurations defined by Google Admin policies.
ActivClient support
This release supports the use of smart cards that rely on ActivClient middleware for authentication.
User authentication in managed-app mode
Horizon Client for Chrome supports user authentication when running as a managed app, such as an app managed by Unified Access Gateway and VMware Workspace ONE. Administrators can use the new Google Admin policy setting ws1WebviewMode to configure these authentication options.

For information about new remote desktop features, see the VMware Horizon 8 2206 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 VMware Horizon 2206 and Horizon 7 version 7.13 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 number provided before each resolved issue refers to the VMware internal issues tracking system.

2969481: Ctrl+Alt+Delete failed to unlock screen

In earlier releases, pressing Ctrl+Alt+Delete on the keyboard did not work to unlock the screen of a remote session. This issue has been resolved.

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