Horizon Client 5.4 for Windows | 17 March 2020
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 remote desktops and published 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.1, and Windows 7
- Unmatched performance - The adaptive capabilities of the PCoIP display protocol and the VMware Blast display protocol are optimized to deliver the best user experience, even over low-bandwidth and high-latency connections. Your remote desktops and published applications are 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 device. Horizon Client supports optional RADIUS and RSA SecurID authentication. You can also install Horizon Client so that it runs in FIPS mode.
- Two-factor authentication after remote session timeout
Beginning with Horizon 7 version 7.12, an administrator can configure two-factor authentication to occur after a remote session times out. For more information, see the VMware Horizon Console Administration document.
- OPSWAT integration support
You can use OPSWAT integration with Horizon Client for Windows. This feature requires Unified Access Gateway 3.9 or later. For more information, see OPSWAT Integration Requirements.
- Enhancements to the selective monitor feature for published applications
You can now select the monitors on which to display published application windows if you have two or more monitors. Previously, this feature required three or more monitors.
- Enhancements to the Real-Time Audio-Video feature with multiple device redirection
If a remote desktop supports multiple devices with the Real-Time Audio-Video feature, selecting a specific microphone in Horizon Client (Settings > Real-Time Audio-Video > Preferred microphone) redirects only that microphone and the selected preferred webcam to the remote desktop. You can select All to redirect all the available microphones and webcams to the remote desktop. For more information, see Select a Preferred Webcam or Microphone on a Windows Client System.
- Changes to the useExisting URI query and a new group policy setting
The default value of the useExisting URI query is changed from true to false. In addition, a new client group policy setting, Use existing client instance when connect to same server, is added. For more information, see Syntax for Creating vmware-view URIs and Scripting Definition Settings for Client GPOs.
The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.
- For the Windows operating systems that this release of Horizon Client for Windows supports, see the VMware Horizon Client for Windows Installation and Setup Guide document.
- Horizon Client for Windows is supported with the latest maintenance release of Horizon 6 version 6.2.x and later.
- To install Horizon Client for Windows, download the installer from the VMware Horizon Client download page.
- For installation instructions, see the VMware Horizon Client for Windows Installation and Setup Guide document.
- For information about the features that are supported in nested mode, see VMware Knowledge Base (KB) article 67248, "VMware Horizon Guidelines for Nested Mode."
- The Horizon Client for Windows installer requires .NET Framework version 4.5 or later. For more information, see VMware Knowledge Base article 65142: Horizon Client 4.10 installer requires .NET Framework version 4.5 or later.
The number provided before each resolved issue refers to the VMware internal issues tracking system.
2447408: Users who have a large number of entitled applications experience long login times.
2475304: If you use a remote desktop in full-screen mode, pressing Ctrl+Alt+Del does not work if you are connected to the remote desktop with the RDP display protocol.
2510911: Users cannot redirect VMware Blast connection traffic to the proxy specified in a PAC file, so a direct connection is used.
2492112: Users cannot connect to a remote desktop after upgrading Horizon Client 5.2 or 5.3. The error message that they receive is "The connection to the remote computer ended."
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.
- 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.
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.
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 remote 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 on some websites, such as www.ted.com, 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.
If LockedGuestSize is set to 640x480 on the client machine and you launch a remote desktop in Window - Small mode, the resolution helper tooltip does not appear when you drag the window edge.
If you install Horizon Agent and then install Horizon Client on the same Windows machine (a nested mode installation), and you later uninstall Horizon Agent, the client's "log in as current user" function is lost after Horizon Agent is uninstalled. This problem occurs because the wsnotify.dll file is removed after Horizon Agent is uninstalled.
Workaround: Reinstall Horizon Agent or Horizon Client to bring back the "log in as current user" function.
The DPI synchronization feature does not work with a Windows Server 2008 R2 remote desktop.
Workaround: Install Microsoft Hotfix You cannot change the DPI setting through a Remote Desktop session on a computer that is running Windows 7 or Windows Server 2008 R2 in the remote desktop.
If you connect multiple USB devices to the client system, select Automatically connect at startup in Horizon Client, and then connect, disconnect, and quickly reconnect to a remote desktop, not all of the USB devices are redirected to the remote desktop after you reconnect.
Workaround: Wait for the USB devices to be redirected back to the client machine (for example, wait for the devices to appear in the device manager) and then reconnect to the remote deskop. Alternatively, you can manually redirect any unredirected USB devices to the remote desktop.
After you disconnect and reconnect multiple remote desktops, you see an error message that states that an error occurred when connecting a USB device to your remote desktop. This problem typically occurs when multiple USB devices are connected to the client machine and you select Automatically connect at startup in Horizon Client.
Workaround: Close the error message box and manually redirect the USB devices to the remote desktop.
If you use the RDP protocol to connect to a published desktop from a physical machine, and then you try to connect to the same published desktop from a zero client, the RDP session ends on the physical machine and the zero client cannot connect.
Workaround: Relaunch the same desktop pool with RDP from the physical machine, select Options > Disconnect and logoff in the launched RDP session, and then reconnect to the same desktop pool from the zero client.
A “Pending session expired” error might occur when you try to connect to a remote desktop with the Microsoft RDP display protocol. This problem only occurs in large-scale environments where a Unified Access Gateway appliance is used and virtual printing is enabled.
Workaround: Establish a connection to the remote desktop without using a Unified Access Gateway appliance, or disable virtual printing and establish a connection using RDP.
When virtual printing is used in Horizon Client, the client processes might not end when you disconnect and close Horizon Client. This problem is caused by a hang that occurs when the virtual printing feature is unloaded.
Workaround: See VMware Knowledge Base (KB) article 2003626: Disabling virtual printing (ThinPrint) in VMware Horizon Client for Windows.
With the clipboard audit feature, the event log reports one byte more than the actual length of the data that was copied from the agent machine to the client machine. For example, if you copy 10 bytes of data from a remote desktop to the client machine, the event log reports "XXX copy 11 bytes CPFORMAT_TEXT data from Horizon Agent to Horizon Client XXX with clipboard." Also, if "\r\n" is in the copied text, the event log records only the length of "\r." For example, if you copy the following text, the audit message records the length as 12 bytes:
You cannot use the device bridge feature to redirect fingerprint scanner devices to remote desktops and published applications. When you use the DeviceTester application to test the connected devices in a remote desktop or published application, the error message "Status: Please connect the device first" appears.
Workaround: None. This problem is a third-party issue.
With the Browser Redirection feature, the context menu options on right click are limited to open link in new tab, open link in new window, back, and forward.
If you select Connect USB Device > Automatically Connect at Startup for a camera, Horizon Client stops responding when you start the remote desktop.