Horizon Client for Linux 4.0.1 | 31 March 2016
Last Updated: 31 March 2016
These release notes cover the following topics:
VMware Horizon Client for Linux makes it easy to access your Windows virtual desktop from a supported Linux system with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).
- Support for Ubuntu, Red Hat Enterprise Linux (RHEL), SUSE Linux Enterprise Desktop (SLED), and CentOS - The Horizon Client installer available from the VMware Downloads site provides support for these operating systems.
- Unmatched performance - The adaptive capabilities of the PCoIP display protocol are optimized to deliver the best user experience, even over low-bandwidth and high-latency connections. Your desktop is fast and responsive regardless of where you are.
- Simple connectivity - Horizon Client for Linux is tightly integrated with VMware Horizon for simple setup and connectivity.
- Secure from any location - At your desk or away from the office, your data is delivered securely to you wherever you are. Enhanced certificate checking is performed on the client. Horizon Client for Linux also supports optional RADIUS and RSA SecurID authentication.
New Features in Horizon Client 4.0.1
- TLSv1.0 is enabled by default
Enabling TLSv1.0 ensures that by default Horizon Client can connect to VMware Horizon Air servers. You do not need to upgrade to Horizon Client 4.0.1 unless you use Horizon Client to connect to Horizon Air cloud-hosted desktops and applications.
Note: Configuration file property (view.sslProtocolString) and command-line option (--sslProtocolString) settings can override the default setting. For more information, see Using VMware Horizon Client for Linux.
New Features in Horizon Client 4.0
- VMware Blast Extreme
End users can select the VMware Blast display protocol when they connect to a remote desktop or application in Horizon Client, and they can configure decoding and network protocol options for VMware Blast sessions. Administrators can create vmware-view URIs to launch a remote desktop or application with the VMware Blast display protocol. This feature requires Horizon Agent 7.0.
- Client drive redirection feature enhancements
You can now share USB storage devices with remote desktops and applications.
- Multiple monitors in different modes
If you use more than 2 monitors, the monitors are no longer required to have the same resolution and mode (portrait or landscape).
- TLSv1.0 disabled by default TLSv1.0 is disabled by default for communications between Horizon Client and View Connection Server and View Agent or Horizon Agent. SSLv3 is removed.
- OpenSSL 1.0.2f support
The OpenSSL library is updated to version openssl-1.0.2f.
- Additional 64-bit Linux support
Ubuntu 14.04 64-bit and Red Hat Enterprise Linux (RHEL) 7.2 are now supported.
New Features in Horizon Client 3.5
- Support for 64-bit Linux
You can install Horizon Client on Ubuntu 12.04 64-bit.
- Client drive redirection (Tech Preview)
Users can now share folders and drives on their Linux client systems with remote desktops and applications. This feature is called client drive redirection. Requires View Agent 6.1.1 or later.
- Windows 10 remote desktop support
You can use Horizon Client to connect to Windows 10 remote desktops.
- Smart card reauthentication after idle session
If you use a smart card to authenticate, you can now use your smart card to reauthenticate if your remote session becomes idle.
- TLSv1.2 enabled by default
TLSv1.2 is enabled by default for communication between Horizon Client and View Connection Server and View Agent. In addition, the default cipher control string is changed to "!aNULL:kECDH+AES:ECDH+AES:RSA+AES:@STRENGTH".
- 4K display support
You can use a 4K display when accessing a remote desktop or application with the PCoIP display protocol. This feature also requires Horizon 6 version 6.2.
- Access Point integration
Horizon Client can use the new Access Point appliance instead of a security server to connect to a View Connection Server instance.
New Features in Horizon Client 3.4
- Improved user experience when installing Horizon Client
The Horizon Client installer now automatically downloads and installs the required version of the OpenSSL library. The installer can also register and start services associated with the USB redirection feature and the virtual printing feature.
Previously, users had to perform post-installation configuration tasks to enable these features. These improvements are available with both the graphical UI installation wizard and the command-line installation program.
- Smart cards for logging in to RDS desktops and hosted applications
Users can now authenticate to RDS-based desktops and RDS-based applications using smart cards. Requires View Agent 6.1 or later.
- Linux remote desktops
Administrators can set up a Linux virtual machine as a remote desktop. End users can log in to a Linux remote desktop from Horizon Client for Linux. Requires View Agent 6.1.1 or later and Horizon Client for Linux 3.4. Not all features are supported in this release. For more information, see Setting Up Horizon 6 for Linux Desktops.
- Temporary removal of FIPS mode support
For security reasons, this release does not support FIPS (Federal Information Processing Standard) mode. If your company requires that clients be FIPS-enabled, do not upgrade to Horizon Client 3.4. Wait for a future release.
New Features in Horizon Client 3.3: There was no 3.3 release of this client.
New Features in Horizon Client 3.2
- Support for additional operating systems with the client installer -- The new client installer provides both a graphical UI and a command-line UI for silent installations on the supported operating systems. See Before You Begin.
- New UI for selecting which monitors to use for Horizon Client - If you specify that you want to use all monitors, and if you are using the PCoIP display protocol, you can specify a subset of adjacent monitors to use.
- Persistent settings in location-based printing -- Printer settings for location-based printers are retained after a user logs out or disconnects from the desktop. After the user logs in to the desktop again, the location-based printer continues to use the previously configured settings. The remote desktop must have View Agent 6.0.2 installed.
New Features in Horizon Client 3.1
- Support for hosted applications -- With this release of Horizon Client for Linux, you can securely access remote Windows-based applications and remote desktops running in a VMware Horizon 6.0 or 6.0.1 environment. After launching Horizon Client and logging in to a Horizon 6.0 or later View server, you see all the remote applications that you are entitled to use, in addition to remote desktops. Selecting an application opens a window for that application on your local Linux system. A remote application looks and behaves as if it were locally installed.
- Favorite remote desktops and applications - You can select remote desktops and applications as favorites in Horizon Client. Favorites are identified by a star. The star helps you quickly find your favorite desktops and applications. Your favorite selections are saved, even after you log off from the View server.
- Expanded virtual printing and location-based printing support -- The virtual printing and location-based printing features are now supported for single-session Windows Server 2008 R2 desktops, RDS desktops (that are hosted on virtual machine RDS hosts), and remote applications. You can also print from nested, or session-in-session remote applications. These are remote applications you might access from a thin-client version of Horizon Client. You must be connected to an Horizon 6.0.1 with View server to use these features.
- USB 3.0 support -- Horizon Client 3.1, together with Horizon 6.0.1 with View, supports USB 3.0 devices plugged into USB 3.0 ports. USB 3.0 devices are supported only with a single stream. Because multiple stream support is not implemented in this release, USB device performance is not enhanced.
Note: On the Linux client system, i386 processors are supported, whereas armel and armhf architectures are not. The Linux kernel version must be 2.6.35 or later
- USB channel encryption configuration -- You can now use the advanced SSL options that you use to encrypt communications between Horizon Client and the View server and View Agent to select security protocols and specify a cipher control string for the USB channel.
- Application name changed -- The name of the Horizon Client application for Linux has changed from VMware Horizon View Client to VMware Horizon Client.
- FreeRDP support was upgraded from FreeRDP 1.0.1 to FreeRDP 1.1 -- With this upgrade, the syntax for command-line usage has changed. For more information, see Using VMware Horizon Client for Linux.
- Support for Ubuntu 14.04 clients
New Features in Horizon Client 3.0: There was no 3.0 release of this client.
The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, and Korean.
Note: To have the client user interface use Simplified Chinese characters, set the client system to use the zh_CN locale. If you set the client system to use the zh_SG locale, the user interface is displayed in English characters.
- The OpenSSL library is updated to version openssl-1.0.2f. For your convenience, the Horizon Client installer provided on the VMware Downloads site downloads and installs the library.
- Horizon Client for Linux 4.0 is supported on the following 32-bit operating systems if you use the installer provided by VMware:
- Ubuntu 12.04, 14.04
- Red Hat Enterprise Linux (RHEL) 6.7
- SUSE Linux Enterprise Desktop (SLED) 11 SP4
- CentOS 6.7
- Horizon Client for Linux 4.0 is supported on the following 64-bit operating systems if you use the installer provided by VMware:
- Ubuntu x64 12.04, 14.04
- Red Hat Enterprise Linux (RHEL) 7.2
- VMware Horizon Client for Linux is supported with the latest maintenance release of Horizon View 5.3.x, VMware Horizon 6.0.x, VMware Horizon 6 version 6.1.x, VMware Horizon 6 version 6.2.x, and Horizon 7 version 7.0
- To install, download the installer from the VMware Horizon Client download page.
- Ubuntu users can also download and install Horizon Client 3.5 and earlier versions from the Ubuntu Software Center. You must enable Canonical Partners and use Synaptic Package Manager to search for and configure installation of the vmware-view-client package. Note that there might be a delay between the time when Horizon Client is first released by VMware and its availability on the Ubuntu Software Center. Also note that the latest version of the client that supports Ubuntu 10.04 is Horizon View Client 1.7.
- Horizon Client for Linux 4.0 does not ship with the GTK+ library, but it does use the library installed on the host system. Make sure your system is up to date with a version of the library that includes fixes for publicly reported security vulnerabilities. A list of the publicly reported security vulnerabilities, and the versions affected, for GTK+ can be found at https://www.cvedetails.com/vulnerability-list/vendor_id-666/GTK.html.
For more system requirements and detailed installation instructions, see Using VMware Horizon Client for Linux.
Resolved in Horizon Client 3.5
When you run the Horizon Client installer, the scan check will always return success for the client compatibility component. To get an accurate compatibility check, you must manually run the following command:
This command will tell you if all required libraries are found in your client system. The scan results for the other components, including PCoIP, USB, RTAV, smart card, and virtual printing, are not affected by this issue. The scan check for these components returns accurate results.
Resolved in Horizon Client 3.4
Previously, several issues were encountered when using Japanese-language keyboards.
Workaround for previous releases: In order to use the hiragana/katakana/muhenkan/henkan key from a Japanese USB keyboard, enable 106/109 key keyboard support on the View desktop. For instructions, see the Microsoft KB at http://support.microsoft.com/kb/822190. If using this KB does not solve the problem, see http://support.microsoft.com/kb/927824/en-us.
Horizon Client for Linux 3.2 required openssl 1.0.1i instead of 0.9.8, but SUSE Linux Enterprise Desktop (SLED) 11 did not support native openssl-1.0.1i. Because the hash links for the trusted CA certificates under /etc/ssl/cert were different from 0.9.8 and 1.0.1, verification of the server certificate failed.
Workaround for previous releases: After compiling and installing openssl 1.0.1i on SLED 11, rebuild the hash link with c_rehash of openssl-1.0.1i as follows:
The c_rehash file is located under the bin folder of compiled openssl.
Resolved in Horizon Client 3.2
Previously, after a session timeout, the desktop could become unresponsive and after about 45 seconds, you were returned to the desktop selector screen.
This issue has been resolved.
Resolved in Horizon Client 3.1
- Previously, if you enabled the group policy setting called "Disable sending CAD when users press Ctrl+Alt+Del" in the remote desktop, then on the Linux client, selecting "Send Ctrl+Alt+Delete" from the menu bar had no effect and using the Ctrl+Alt+Insert key combination had no effect. This issue has been resolved.
- Previously, on Ubuntu 12.04 systems, in the Login dialog box for Horizon Client, if you clicked About VMware Horizon Client, you would not be able to close the About box until you first closed the Login box. This issue has been resolved.
- Previously, after you installed Horizon Client, you could not change the language used by the operating system on the client machine. The Language Support app in system settings would not start. This issue has been resolved.
Previously, if you used Horizon Client with a Ubuntu 12.04 operating system, the menu bar would not appear on the desktop selector screen if you launched the client with the
--fullscreen parameter. This issue has been resolved.
- Previously, the copy and paste feature did not work on Linux systems with ARM processors. This issue has been resolved.
A known security issue can affect Horizon Clients. The issue involves a privilege escalation leveraging glibc. This issue was devised by the Project Zero team as described in CVE-2014-5119. To mitigate this issue, partners and customers are advised to update the Linux operating system as follows:
- For Ubuntu refer to http://www.ubuntu.com/usn/usn-2328-1/.
- For RHEL refer to https://access.redhat.com/security/cve/CVE-2014-5119.
- For SLES refer to http://support.novell.com/security/cve/CVE-2014-5119.html.
- For CentOS refer to http://lists.centos.org/pipermail/centos-announce/2014-August/020518.html.
- If you use Horizon Client to connect to a remote desktop that has client drive redirection disabled, such as through a group policy setting, or if you connect to a remote desktop that has View Agent 6.1.0 or an earlier version installed, no message is displayed to explain why the client drive redirection feature is not working.
- In some versions of Linux, including CentOS 6.5 and 6.6, the Numlock LED does not work while in a View desktop.
If multiple Horizon clients connect to the same RDS desktop or remote application simultaneously and map to a location-based printer with the same name, the printer appears in the first client session, but not in later client sessions.
Workaround: For the client sessions in which the printer does not appear, perform a manual refresh. For a remote desktop, press F5 or refresh the Devices and Printers window. For a remote application, close and reopen the application print dialog box. The location-based printer appears in the printer list.
Virtual printing might not work if you connect to a remote desktop using RDP, open Horizon Client on the remote desktop, launch a nested application session, and then log off and log back in to the desktop. When you try to print from the nested application, the expected printer list might not appear. This issue only occurs after you log back in to the desktop.
Workaround: Reset the application on the remote desktop. To avoid having to set applications, use PCoIP for both ends of the session-in-session connection. That is, use PCoIP to connect to the remote desktop and use PCoIP to connect from within the desktop to the nested application. If you are using location-based printing, you can resolve this issue by closing and reopening the application's print dialog box.
If you use a FreeRDP connection and specify a monitor configuration that conflicts with the configuration the end user chooses, Horizon Client performance becomes poor and the client might stop responding altogether. For example, the following command for launching Horizon Client would cause problems if the user selected "Full Screen - This Monitor":
vmware-view --enableNla --rdpclient=xfreerdp --xfreerdpOptions="/sec:nla /cert-ignore /p:password /u:crt\administrator /multimon"
As a best practice, avoid specifying FreeRDP options for the disply, such as /multimon or /workarea. Instead, let Horizon Client control the topology.
- If you use FreeRDP to connect to a Windows XP or Vista remote desktop, and the client system uses multiple monitors with a combined screen resolution that is larger than the maximum resolution set for the remote desktop, you will not be able to see the Start menu or taskbar in the remote desktop. For example, if the client system uses two monitors with a screen resolution of 2560x1600 each, this issue occurs.
If your client system is running pcsc-lite version 1.5, smart card removal policy may not work, logging off, shutting down or resetting a Windows remote desktop may result in a black screen, or the Horizon Client menu may become blank for about 10 seconds when a user has smart card sessions to multiple desktops and the user disconnects from one desktop.
Workaround: Upgrade to pcsc-lite 1.7.4 or later.
If you use a PulseAudio sound system, you might hear static when setting the volume using guest system volume slider.
Workaround: Use the Linux client system's volume slider or use ALSA audio.
If you connect to a View desktop with FreeRDP and configure the desktop to connect to a separate disk, if the disk name includes non-ASCII characters, the disk name cannot be displayed correctly in the View desktop. For example, if you use non-ASCII characters in the disk name and then launch Horizon Client with command line option
'--rdpclient=xfreerdp' and '--xfreerdpOptions="/drive:
the disk name does not appear correctly in the View desktop.
- If you use Horizon Client with a Ubuntu 12.04 operating system, if you press the Windows key in a View desktop, the Windows key press is also captured by the client operating system.
If you use Horizon Client with a Ubuntu 12.04 operating system, occasionally you might see an issue when launching a View desktop in full screen mode.
Workarounds: Update to the latest patch release of Ubuntu 12.04, or switch to the client operating system by pressing Alt+Tab, and then switch back to the View desktop session.
When you select the VMware Blast display protocol to connect to a remote desktop and the UDP network protocol is used, your session might be disconnected.
Workaround: Disable UDP networking for VMware Blast sessions. See "Configure VMware Blast Options" in Using Horizon Client for Linux.
Users cannot use rdesktop 1.8.x to connect to Horizon 7 Windows desktops. This is because Horizon 7 does not support TLSv1.0 by default and rdesktop 1.8.x supports only TLSv1.0.
Workaround: Enable TLSv1.0 on the desktop by setting the following registry key:.
Be aware that TLSv1.0 is considered insufficiently secure. For Windows 7 desktops, Microsoft KB https://support.microsoft.com/en-us/kb/3080079 must also be installed.