Horizon Client for Linux 4.1 | 16 June 2016
Last Updated: 19 July 2016
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 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 VMware Blast and PCoIP display protocols 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.
- Support for Windows Media MMR
- H.264 support for Intel-based Linux devices
- GUI for USB redirection
- Clipboard size is configurable up to a maximum of 16 MB
- OpenSSL 1.0.2h support
- Support for 64-bit RHEL 6.7
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.2h. For your convenience, the Horizon Client installer provided on the VMware Downloads site downloads and installs the library.
- Horizon Client for Linux 4.1 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.1 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) 6.7, 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.x.
- 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.1 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.
- On some thin clients, when a user is connected to a remote desktop, selecting the record function in an audio application on the desktop causes the session to be disconnected.
When the environment variable http_proxy or https_proxy is set, the NO_PROXY environment variable does not work.
Note: You can set no_proxy or NO_PROXY, but not both. The variable name is case-sensitive.
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.7, 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 display, 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.
- On Ubuntu 12.04 and 14.04, if you press the Windows key in a View desktop, the Windows key press is also captured by the client operating system.
On Ubuntu 12.04, 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.
On RHEL 7.2 64-bit using AMD open source drivers, with H.264 enabled and the VMware Blast protocol, users might not be able to connect to a remote desktop.
Workaround: Add vmgl.GL_ARB_transform_feedback2 = FALSE to /etc/vmware/config.
- On RHEL 6.7, with two monitors at the maximum resolution of 2560 x 1600, if you change the order of the monitors (the main monitor becomes the secondary and the secondary becomes the main), and then run Horizon Client and connect to a desktop using PCoIP and setting Full Screen - All Monitors, after the remote desktop is displayed, the menu options File > Disconnect from Server and File > Return to Desktop and Application List do not work.
Some video files might not play properly on a remote desktop when MMR is enabled.
Solution: Make sure that the video format is supported and the proper decoder plug-in for the video is installed on the client.
On a Windows 7 remote desktop, playing video on Internet Explorer and then opening a new tab causes the video to appear in the new tab.
Workaround: Do not open a new tab or switch to a different tab while video is playing.