Horizon Client for Windows 2006 | 11 August 2020

These release notes cover the following topics:

Key Features

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 (32-bit and 64-bit), Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
  • 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 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.

Top of Page

What's New in This Release

Beginning with this release, version numbering is based on the year and the planned month of the release. For example, 2006 represents the year 2020 and the month of June.

Horizon Client for Windows 2006 includes the following new features:

  • Configure the maximum latency for mouse coalescing
    The Configure maximum latency for mouse coalescing group policy setting enables you to configure the maximum latency allowed, in milliseconds, when coalescing mouse movement events. See General Settings for Client GPOs.
  • Windows 10 2004 support
    You can install Horizon Client for Windows on a Windows 10 2004 client system.
  • Client version restriction
    A warning message appears in Horizon Client if you try to connect to a server that does not support your Horizon Client version. For information about setting up client version restrictions, see Global Client Restriction Settings for Client Sessions.
  • Certificate revocation changes
    When the Ignore certificate revocation problems group policy setting is enabled, the client might only use a cached URL during server certificate verification. Horizon Client now passes additional certificate flags to handle time outs.
  • Video support in Media Optimization for Microsoft Teams
    Both audio and video are supported. Previously, only audio was supported. This feature requires Horizon Agent 2006. To use this feature, the Enable Media Optimization for Microsoft Teams option must be selected during Horizon Client for Windows installation. See Install Horizon Client for Windows.

Unsupported Operating Systems and Features

You can no longer install Horizon Client for Windows on the following operating systems:

  • Windows 7
  • Windows 8.1
  • Windows 10 version 1809 SAC
  • Windows Server 2008 R2
  • Windows Server 2012

The following features are no longer supported in Horizon Client for Windows in this release:

  • Flash URL Redirection
  • Flash Redirection
  • Virtual Printing (you can use VMware Integrated Printing instead)

You cannot use the Software Updates feature in Horizon Client for Windows to upgrade from Horizon Client for Windows 5.x to Horizon Client for Windows 2006. You can download Horizon Client for Windows 2006 from the VMware Horizon Client download page.

Internationalization

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

Resolved Issues

The number provided before each resolved issue refers to the VMware internal issues tracking system.

  • 2411931, 2439350, 2452774: In specific environments, Horizon Client might receive an SSL error.

Known Issues

  • 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 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.

    Workaround: None.

  • 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.

    Workaround: None

  • 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.

  • 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.

  • 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:
    "aaa
    bbb
    ccc"

    Workaround: None.

  • 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.

    Workaround: None.

  • If you select Connect USB Device > Automatically Connect at Startup for a camera, Horizon Client stops responding when you start the remote desktop.

    Workaround: None.

  • When using Horizon Client with Media Teams Optimization enabled, if the client wakes from hibernation during a Teams call, the Teams call continues, but sometimes self preview video in the remote desktop, and the remote peer's incoming video, freezes.

    Workaround: To fix the frozen video problem, click the video button from the call monitor to turn it off and then click the video button again to turn it back on.

check-circle-line exclamation-circle-line close-line
Scroll to top icon