Horizon Client for Windows 4.2 | 15 September 2016
Last Updated: 15 September 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 Windows makes it easy to access your Windows or Linux virtual desktop or hosted Windows desktops and applications with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).
- Support for Windows 10, Windows 8 and 8.1 (with Updates), and Windows 7
- Unmatched performance - The adaptive capabilities of the PCoIP display protocol and the Blast Extreme 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 and Horizon 7 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. You can also install Horizon Client for Windows so that the client runs in FIPS mode.
- DPI Synchronization
The DPI Synchronization feature ensures that the remote desktop's DPI setting matches the client machine's DPI setting for new remote sessions. This feature is enabled by default. An administrator can disable this feature by disabling the Horizon Agent DPI Synchronization group policy setting. For more information, see "Horizon Agent Configuration ADM Template Settings" in Setting Up Desktop and Application Pools in View.
- Configure Real-Time Audio-Video settings in Horizon Client
You can now select your preferred webcam and microphone in the Horizon Client Settings dialog box.
- Physical client information is sent to remote desktops in a double-hop scenario
If Horizon Client is running inside of a remote desktop session, it sends some physical client information (instead of virtual machine information) to the remote desktop. For information about the physical client information that Horizon Client sends to the second-hop desktop, see "Client System Information Sent to Remote Desktops" in Setting Up Desktop and Application Pools in View.
- Username hint field support for smart card authentication
Smart card users that use a single smart card certificate to authenticate to multiple user accounts can enter their user name in the Username hint field in the Horizon Client login dialog box during smart card sign-in. To make the Username hint field appear on the Horizon Client login dialog box, an administrator must enable the smart card user name hints feature for the Connection Server instance. This feature also requires Horizon 7 version 7.0.2.
- Pass command-line arguments when launching a remote application from a URI
You can use the args query to pass command-line arguments when you launch a remote application from a URI.
- Spanish language support
Both the Horizon Client for Windows user interface and the documentation are now available in Spanish.
The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.
- This release of Horizon Client for Windows requires one of the following operating systems:
- 32-bit or 64-bit Windows 10, Home, Pro, Enterprise, or IoT (Internet of Things) Enterprise
- 32-bit or 64-bit Windows 8, 8.1, or 8.1 Pro, Enterprise, or Industry Embedded
- 32-bit or 64-bit Windows 7 SP1, Home, Enterprise, Ultimate, or Professional edition
- Windows 2012 Server SP2
- VMware Horizon Client for Windows 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 or 6.2.x, and VMware Horizon 7.
- 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.
- The error message "No valid certificates were found on this smart card" appears on the Horizon Client for Windows when you use a PIV smart card to authenticate to Windows 8 or Windows Server 2012 R2 and above desktops that do not have middleware installed. This problem is resolved when you install Horizon Agent 7.0.2 in the remote desktops and enable Windows auto update to let Windows install the PIV smart card minidriver on both the Windows client and Horizon agent.
After you install Horizon Agent 7.0.x in a Windows 7 or Windows Server 2008 R2 remote desktop, you can no longer use the Microsoft RDP display protocol to connect to the remote desktop. This problem occurs because TLSv1.0 is disabled by default in Horizon 7 version 7.0 and later.
Workaround: Install Microsoft update 3080079: Update to add RDS support for TLS 1.1 and TLS 1.2 in Windows 7 or Windows Server 2008 R2 in the Windows 7 or Windows Server 2008 R2 virtual machine and in any Windows 7 client machines.
When attempting to use the Real-Time Audio-Video feature on a Surface Pro 4 device, you see only a black screen. This issue occurs because the client needs to be configured to accommodate the default screen resolution for a Surface Pro 4, which is 1920 X 1080.
Workaround: On the Windows client machine, edit the following registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\RTAV:
- Set srcWCamFrameHeight to 1080.
- Set srcWCamFrameWidth to 1920.
The serial port redirection group policy setting Bandwidth Limit does not set a limit on the bandwidth.
Workaround: Use third-party software to limit the bandwidth.
With serial port redirection, at a high baud rate such as 115200, the performance of VMware Blast is significantly worse than PCoIP, and the connection might sometimes hang.
Workaround: Use a baud rate of 9600.
In an IPv6 environment, if you configure IP address mapping for location-based printing, users might encounter a problem accessing the printer because the client can have multiple IPv6 addresses. Anytime the client connects, it can use any one of the addresses.
Workaround: Use the location-based printing group policy setting IP Range to include the multiple addresses. However, the printing problem might still occur because the client might use a temporary address, which is not in the specified range.
- 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.
On Windows 7 and Windows Server 2008 R2 desktops, if you remove a drive from being shared on the desktop, Windows Explorer continues to display the removed drive in the guest operating system.
Workaround: Close and reopen Windows Explorer.
On Windows 7 and Windows Server 2008 R2 desktops, if you open files in a shared folder on the desktop, disconnect from the desktop, and reconnect to the desktop, the left navigation pane in Windows Explorer displays duplicate entries for the shared drive.
Workaround: Close and reopen Windows Explorer.
- 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 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 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.
When a user connects to a desktop using PCoIP shortly after the desktop is powered on, autofit of the desktop window might not work. This issue happens most often if the desktop or network is under stress shortly after power-on (to start multiple applications or to map network drives, for example).
Workaround: Double-click the desktop window's title to go into window mode and double-click the title bar to go into all-monitor mode.
On Windows 10, Windows Fax and Scan hangs when using a CardScan 800 device.
When you use the Flash redirection feature to play a video, you cannot exit full-screen mode because the Exit Full Screen button does not appear in the Flash player toolbar.
Workaround: Press Ctrl+Alt+Delete and unlock the client side to see the Horizon Client toolbar and then adjust the window size to
make the Flash player window smaller.
When you use the Flash redirection feature to play a video, if you click the Ad link at the bottom of the screen or the More Info link in the Flash player, the advertisment page does not pop up and the playback pauses.