| VMware Horizon Client for Chrome 2212 | 12 JAN 2023 Check for additions and updates to these release notes. |
This page contains release-related information for Horizon Client for Chrome 2212, which enables users to connect to and use remote desktops and published applications using a Chromebook 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.
Horizon Client for Chrome 2212 includes the following new features.
Server icons for primary host names only
By default, Horizon Client displays a server icon for the primary host only and hides the display of icons for any secondary host. Administrators can change this default behavior using a new Google Admin property, hideSecondaryServer.
Automatic USB redirection
New auto-connect settings allow users to configure automatic redirection behavior for client USB devices. With two new Google Admin settings, autoForwardUSBPolicy and enableAutoForwardUSB, administrators can configure global policies that define the default automatic redirection behavior for all users.
File upload and download policies
With two new Google Admin settings, allowFileUpload and allowFileDownload, administrators can configure whether users are allowed to upload or download files between a remote desktop and client device using the file transfer feature.
For information about new remote desktop features, see the VMware Horizon 8 2212 Release Notes.
Horizon Client for Chrome requires Chrome OS 75 or later.
Horizon Client for Chrome is supported with the latest maintenance release of the following deployment types:
VMware Horizon 8 version 2006 and later
VMware Horizon 7 version 7.13 and later
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.
The following issues have been resolved in this release.
Duplicate server icons were generated for primary and secondary host names.
When performing a URL launch through the Avi load balancer where there was a primary load balancer host name and a secondary Unified Access Gateway (UAG) host name, Horizon Client for Chrome displayed a server icon for each host name. This resulted in two icons for the same server.
This issue has been resolved in this release. Horizon Client for Chrome now displays a server icon only for primary host names.
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.
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.
Horizon Client for Chrome documentation is in the VMware Horizon Documentation Center.
The user interface and documentation for Horizon Client for Chrome are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.
To receive support, access VMware Customer Connect. To learn more about the support policies, see Support Policies.
For information on filing a support request in Customer Connect and via Cloud Services Portal, see the VMware knowledge base article at https://kb.vmware.com/s/article/2006985.
