VMware Horizon Client for Windows Release Notes
Horizon Client for Windows 4.5 | 08 June 2017
Last Updated: 08 June 2017
These release notes cover the following topics:
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.
Top of Page
What's New in This Release
- Next Generation Horizon Client for Windows installer
The Horizon Client for Windows installer has been updated to provide an enhanced user experience.
- Virtualization Pack for Skype for Business
You can run Skype for Business inside a virtual desktop without negatively affecting the virtual infrastructure and overloading the network. All media processing takes place on the Windows client machine, instead of in the virtual desktop, during Skype audio and video calls. To use this feature, you must install the Virtualization Pack for Skype for Business on the client machine during Horizon Client installation. A Horizon administrator must also install the Virtualization Pack for Skype for Business on the virtual desktop during Horizon Agent installation.
- 32-bit Core Remote Experience component
You can use the Horizon Client for Windows installer to install the 32-bit Core Remote Experience component on a 64-bit Windows client machine.
- Windows 10 Creators Update support
You can install Horizon Client for Windows on a Windows 10 Creators Update machine.
- Recursive Unlock feature
The Recursive Unlock feature unlocks all remote sessions after the client machine has been unlocked. This feature applies only after a user logs in to the server with the Log in as current user feature. To enable this feature, you set the Unlock remote sessions when the client machine is unlocked group policy setting.
- vdm_client.adm template file has been removed
The vdm_client.adm template file has been removed from Horizon Client for Windows. You must use the vdm_client.admx template file instead.
- Scrolling wheel pad support
You can use a scrolling wheel pad on a laptop with the VMware Blast and PCoIP display protocols.
- Support for Workspace ONE Mode
Beginning with Horizon 7 version 7.2, a Horizon administrator can enable Workspace ONE mode for a Connection Server instance. If you connect to a Workspace ONE mode enabled server in Horizon Client for Windows, you are redirected to the Workspace ONE portal to launch your entitled desktops and applications.
Top of Page
The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.
Before You Begin
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.
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 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 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 you enable the URL content redirection feature, registry keys and values under HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\URLRedirection remain after you uninstall Horizon Client.
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.
- In certain circumstances, opening a local file with File
> Open in a remote desktop or remote application causes
the guest operating system on the Horizon Agent machine to
encounter a STOP error (blue screen) or to stop responding
(hang) when client drive redirection (CDR) is used. For more
information, see VMware Knowledge Base (KB) article 2149417: Agent
machine gets STOP error or stops responding when you open a
local file shared with CDR.
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.