VMware

VMware Horizon Client for Windows Release Notes

Horizon Client for Windows 3.3 | 12 March 2015

Last Updated: 12 March 2015

These release notes cover the following topics:

Key Features

VMware Horizon Client for Windows makes it easy to access your Windows virtual desktop with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).

  • Support for Windows 8 and 8.1 (with Updates) and Windows 7 systems - With Horizon Client 3.3, support for Windows XP and Windows Vista has been discontinued. See What's New.
  • 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 Windows is tightly integrated with VMware Horizon 6 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. SSL/TLS encryption is always used to protect user credentials, and enhanced certificate checking is performed on the client. Horizon Client for Windows also supports optional RADIUS and RSA SecurID authentication.

Top of Page

What's New in This Release

The 3.3 release of Horizon Client for Windows includes the following new features:

  • Support for x86-based tablets such as Windows Surface Pro
    You can now install Horizon Client for Windows on x86-based tablets, providing features that are not available with Horizon Client for Windows Store, including USB redirection, Windows Media MMR, virtual printing, Real-Time Audio-Video, and smart cards. You can configure Horizon Client so that onscreen keyboard, mouse, and handwriting pad events are sent to the remote desktop or remote application, even if the mouse or onscreen keyboard is outside of the Horizon Client window.
  • 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.
  • Support for IPv6 networks
    Horizon Client 3.3 supports IPv6 networks in addition to IPv4 networks. The Horizon 6 version 6.1 environment must be operated in either an IPv6 or an IPv4 configuration; a mixed mode of operation is not supported. Not all Horizon 6 features that are supported in an IPv4 environment are supported in an IPv6 environment. Requires VMware Horizon 6 version 6.1 servers and desktops.
  • USB redirection of mass storage devices on RDS desktops and hosted applications
    Users can plug their USB flash drives and hard disks into their client systems and have these devices redirected to RDS-hosted desktops and applications. USB redirection of other types of USB devices, and other types of USB storage devices such as security storage drives and USB CD-ROM, is not supported. This feature is supported on Windows clients and Windows Server 2012 RDS hosts. Requires View Agent 6.1.
  • Support discontinued for Windows XP and Windows Vista as client operating systems
    Horizon Client for Windows 3.3 must be installed on a Windows 7 or Windows 8.x client system. Horizon Client will work with Windows XP and Windows Vista remote desktops if you continue to use View Agent 6.0.2 or an earlier version. For more details, see Retiring Old OSes: XP, Vista, Mac OS X 10.6 & 10.7.
  • SSL v3.0 disabled by default
    In Horizon Client 3.2 and earlier versions, SSL v3.0 was enabled by default. This change addresses CVE-2014-3566, commonly known as the POODLE attack. For more information, see Microsoft Security Advisory 3009008. If you need to enable SSLv3 in Horizon Client, you can use either a group policy setting or a Windows Registry setting to change the default ciphers and protocols. See Using VMware Horizon Client for Windows.

Top of Page

Internationalization

The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, and Korean.

Top of Page

Before You Begin

  • The OpenSSL library has been updated to version openssl-1.0.1j.
  • VMware Horizon Client for Windows requires one of the following operating systems:
    • 32-bit or 64-bit Windows 8, 8.1, or 8.1 Update, Enterprise or Pro edition
    • 32-bit or 64-bit Windows 7 SP1, Home, Enterprise, Ultimate, or Professional edition

    With Horizon Client 3.3, support for Windows XP and Windows Vista has been discontinued. See What's New.

  • VMware Horizon Client for Windows is supported with the latest maintenance release of Horizon View 5.3.x, VMware Horizon 6.0.x, or VMware Horizon 6 version 6.1.
  • To install, download the installer from the VMware Horizon Client download page.
  • For more system requirements and installation instructions, see Using VMware Horizon Client for Windows.

Top of Page

Resolved Issues

Resolved in Horizon Client 3.3

  • Previously, certain WIA scanning devices did not appear in the Scanner Redirection for VMware Horizon menu on the desktop after the devices' drivers were installed and the devices were plugged into the client computer. This issue has been resolved.

Resolved in Horizon Client 3.2

  • Previously, if you connected to a Windows Server 2008 R2 remote desktop, the virtual printing feature sometimes did not work correctly, so that instead of having a redirected virtual printer as the default, the Printers and Devices list in the remote desktop showed the location-based printer as the default. This issue has been resolved

Resolved in Horizon Client 3.1

  • Previously, remote applications that depended on user interaction with the System Tray could not be shut down. This issue has been resolved. System tray items from the remote desktop now appear in the system tray of the client system.

Resolved in Horizon Client 3.0

  • Previously, the client did not support connections via proxy server if the proxy details were configured using group policy preferences. This issue has been resolved.
  • Previously, if you used the Log In as Current User feature, the connection might fail unless you logged in to the local operating system as an admin user. This issue occurred if the primary DNS name was different from the primary domain name. This issue has been resolved.
  • 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 Windows client, selecting "Send Ctrl-Alt-Delete" from the menu bar had no effect. Also, using the Ctrl+Alt+Insert key combination had no effect. These issues have been resolved.
  • Previously, if you used a Windows 8.1 client device and attempted to configure a Philips SpeechMike USB device to be split and redirected to the View desktop, the USB redirection would fail.
    This issue has been resolved.
  • Previously, the client could not connect to a server if the server short name was used. This issue has been resolved.
  • Previously, under certain connection failure conditions, the following error message appeared, even if the server did not provide a self-signed certificate: "Cannot verify your connection. The server provided a self-signed certificate instead of a verifiable certificate." This issue has been resolved so that the client no longer presents an incorrect failure message.
  • Previously, if you used a tablet client device, if you moved the mouse pointer within 10 mm of the top of the screen, the tab for the shade dropped down. This issue has been resolved so that the shade does not drop down unless you move the pointer to the very top of the screen.

Top of Page

Known Issues

  • On Windows 7 client systems, you cannot use the Windows Media MMR feature with videos that use Dolby AC3 audio. On Windows 7 clients, Windows Media Foundation does not have the proper codec to support Dolby AC3 audio files. This issue does not occur on Windows 8.x clients.
  • In the Settings dialog box, pressing the Tab key has no effect.
  • Sometimes the virtual printing feature and location-based printing feature are not able to display the correct list of printers in the Devices and Printers window of a remote, session-based desktop. This issue can occur with desktops provided by Windows Server 2012 RDS hosts. The printers shown within applications are correct, however.
    Workaround: Log off the desktop running on the Windows Server 2012 RDS host and reconnect to it.
  • 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 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. This problem also occurs for client-redirected virtual printers.
    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.
  • In a nested, or session-in-session, implementation of Horizon Client, the virtual printing feature works only for remote applications and not for desktops. An example of a session-in-session implementation is one in which an end user logs in to Horizon Client on a thin client, so that the Horizon Client interface is the only one the end user sees, and the end user then launches a nested version of Horizon Client in order to use a remote application provided by an RDS host.
  • If your client operating system is Windows 8.1 and you launch a Microsoft RDP session, pressing Ctrl+Alt+Insert does not send Ctrl+Alt+Del to the remote virtual desktop.
    Workaround: Upgrade the operating system by installing Windows 8.1 Update.
  • If you close an IE 8 browser in the desktop while Flash URL Redirection is in effect, the redirected video remains open on the client system.
    Workaround: Manually close the redirected video window.
  • If you use a touch-enabled screen on your client system to work in a View desktop, do not use the Enable Relative Mouse feature. This feature provides improved mouse performance for 3D and CAD applications, but for touch-enabled screens and tablets, the mouse coordinates are not translated properly, even in 3D and CAD applications.
  • If you have multiple monitors with different screen resolutions and expand Horizon Client to all monitors and then select the Enable Relative Mouse feature, occasionally, the mouse pointer might not be able to move downward beyond a certain position.
    Workaround: Press Ctrl+Alt.
  • For more information about known issues with features specific to Horizon 6 version 6.1, see the Release Notes for VMware Horizon 6 version 6.1.
  • For information about known issues with the scanner redirection and Windows Media multimedia redirection (MMR) features, see the Release Notes for VMware Horizon 6.0.2 (with View).

Top of Page