Horizon Client for Chrome 4.10 | 13 December 2018
These release notes cover the following topics:
- Key Features
- What's New in This Release
- Before You Begin
- Resolved Issues
- Known Issues
VMware Horizon Client for Chrome makes it easy to access your remote desktops and published applications from your Chromebook with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).
- Work the way you want to - Use your Chromebook to work on your remote desktops and published applications from any location. Support for the VMware Blast display protocol from VMware means your remote desktop or published application is fast and responsive, regardless of where you are.
- Simple connectivity - Horizon Client for Chrome is tightly integrated with VMware Horizon 7 for simple setup and connectivity. Open Chrome, enter a server URL, and log in to see a list of available remote desktops and published applications.
- Secure from any location - At your desk or away from the office, your data is always secure. Enhanced certificate checking is performed on the client. Horizon Client for Chrome also supports optional RADIUS and RSA SecurID authentication.
- Display remote desktops and published applications in full-screen mode
You can display a remote desktop or published application in full-screen mode.
- Use published applications in multi-session mode
When multi-session mode is enabled for a published application, you can use multiple sessions of the published application when you log on to the server from different client devices. For example, if you open a published application in multi-session mode on client A, and then open the same published application on client B, the published application remains open on client A and a new session of the published application opens on client B.
For Horizon Client for Chrome, the user interface is available only in English. The documentation is available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.
- Horizon Client for Chrome requires Chrome OS 44 or later.
- Horizon Client for Chrome is supported with the latest maintenance release of Horizon 6 version 6.2.6 or Horizon 7 version 7.4 and later releases. To connect to a Horizon 7 version 7.4 server, you must register the Horizon Client for Chrome extension on the server. This change is not required for Horizon 6 version 6.2.6 or Horizon 7 version 7.5 and later servers.
- 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 VMware Horizon Client for Chrome Installation and Setup Guide document.
You cannot edit the server name, or add and edit a server description, when you start Horizon Client for Chrome.
The maximize, minimize, and close buttons appear in the client window in kiosk mode. These features are disabled in kiosk mode, so the buttons should not be shown.
The multi-monitor feature does not work in kiosk mode.
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.
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.
When H.264 decoding is enabled, if you use the sidebar to switch between remote desktops, or between remote desktops and published applications, the remote sessions become unresponsive. The remote sessions are still connected, but mouse clicks and other actions do not work.
Workaround: Close and reconnect to the remote desktop or published application sessions.
Virtual desktop performance is slow when H.264 decoding is enabled for VMware Blast connections.
Workaround: Disable H.264 decoding before connecting to a virtual desktop with the VMware Blast display protocol.