Horizon Client for Windows 4.0.1 | 31 March 2016
Last Updated: 31 March 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 systems - Windows XP and Windows Vista are supported only with Horizon Client 3.2.1 and earlier. See Resolved in Horizon Client 3.2.1.
- 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.
New Features in Horizon Client 4.0.1
- TLSv1.0 is enabled by default
Enabling TLSv1.0 ensures that by default Horizon Client can connect to VMware Horizon Air servers. You do not need to upgrade to Horizon Client 4.0.1 unless you use Horizon Client to connect to Horizon Air cloud-hosted desktops and applications.
Note: The Configures SSL protocols and cryptographic algorithms setting in the Horizon Client Configuration ADM template file can override the default setting. For more information, see Using VMware Horizon Client for Windows.
New Features in Horizon Client 4.0
- VMware Blast Extreme
End users can select the VMware Blast display protocol when they connect to a remote desktop or application in Horizon Client, and they can configure decoding and network protocol options for VMware Blast sessions. Administrators can create vmware-view URIs to launch a remote desktop or application with the VMware Blast display protocol. This feature requires Horizon Agent 7.0.
- High Resolution Display Scaling
Display scaling is supported at higher DPI in remote desktops and applications and is applicable when the Windows client is set to be "System DPI-aware" and the scaling level is greater than 100%.
- Client drive redirection feature enhancements
You can now share client-side USB storage devices' folders with remote desktops and applications.
- URL Content Redirection
For specific URLs, an administrator can configure whether the links always open on the client or in a remote desktop or application. URLs can be links to Web pages, telephone numbers, email addresses, and more. The URLs redirected are those that are typed into the Internet Explorer browser's address bar or when user clicks a link in an application such as Outlook or Word. This feature requires Horizon Agent 7.0 and works with Horizon Client for Windows only.
- Flash Redirection (Tech Preview)
For specific URLs, Flash content in an Internet Explorer browser is sent to the Windows-based client and played in a Flash container window, thereby offloading demand on the ESXi host. Configuration is done through group policy. This feature also requires Horizon Agent 7.0.
- Support for Windows Server 2012 as a client
This client support has been added for the purposes of running Horizon Client in nested mode. This mode is sometimes used for zero clients or thin clients. Some limitations apply. See the system requirements in Using VMware Horizon Client for Windows.
- Multiple monitors in different modes
If you use more than 2 monitors, the monitors are no longer required to have the same resolution and mode (portrait or landscape).
- TLSv1.0 disabled by default
TLSv1.0 is disabled by default for communications between Horizon Client and View Connection Server and View Agent or Horizon Agent. SSLv3 is removed.
- OpenSSL 1.0.2f support
The OpenSSL library is updated to version openssl-1.0.2f.
- Tunnel connection performance improvement
The data transfer rate has significantly improved when Horizon Client connects through a secure tunnel.
New Features in Horizon Client 3.5.2
This release contains bug fixes.
New Features in Horizon Client 3.5.1
This release contains an important bug fix. See Resolved Issues.
New Features in Horizon Client 3.5
- Open local files with remote applications
The client drive redirection feature for Windows clients now also includes the ability to open files on the local system using a remote application. You can configure files to open with the remote application when you double-click the file in your client system's Windows Explorer. Or you can right-click the file and select to open the file with the remote application. (If Horizon Client is not running, it will start up.) Requires View Agent 6.2 or later.
- Windows 10 support for remote desktops and local client system
You can install Horizon Client in a Windows 10 system, and you can use Horizon Client to connect to Windows 10 remote desktops
- Expanded Microsoft Lync support
You can now also run Microsft Lync on multi-session desktops provided by Microsoft RDS hosts and on Windows 10 single-user desktops.
- TLSv1.2 enabled by default
TLSv1.2 is enabled by default for communication between Horizon Client and View Connection Server and View Agent. In addition, the default cipher control string is changed to "!aNULL:kECDH+AES:ECDH+AES:RSA+AES:@STRENGTH".
- OpenSSL 1.0.2d support
The OpenSSL library is updated to version openssl-1.0.2d.
- Support for 4K resolution for the remote desktop or application
You can use a 4K display when accessing a remote desktop or application with the PCoIP display protocol. This feature also requires Horizon 6 version 6.2.
- Virtual printing changes
Virtual printers appear as <printer_name> in single-user virtual machine desktops and as <printer_name>(s<session_ID>) in session-based desktops on RDS hosts if View Agent 6.2 or later is installed.
- Access Point integration
Horizon Client can use the new Access Point appliance instead of a security server to connect to a View Connection Server instance. This feature also requires Horizon 6 version 6.2.
New Features in Horizon Client 3.4
- Client drive redirection
Users can now share folders and drives on their Windows client systems with remote desktops and applications. This feature is called client drive redirection. Requires View Agent 6.1.1 or later.
- Serial port redirection
With serial port redirection, users can redirect locally connected serial (COM) ports such as built-in RS232 ports or USB-to-serial adapters. Devices such as printers, bar code readers, and other serial devices can be connected to these ports and used in the remote desktops.
- Support for Windows Media Multimedia Redirection (MMR) for RDS desktops
Windows Media MMR is now supported for videos playing on RDS desktops. In past releases, this feature was supported only on VDI desktops that run on single-user machines. For details about supported desktops, see see System Requirements for Windows Media MMR in the Setting Up Desktop and Application Pools in View guide.
- Linux remote desktops
Administrators can set up a Linux virtual machine as a remote desktop. End users can log in to a Linux remote desktop from Horizon Client for Windows. Requires View Agent 6.1.1 or later and Horizon Client for Windows 3.4. Not all features are supported in this release. For more information, see Setting Up Horizon 6 for Linux Desktops.
- Usability enhancements when using multiple monitors
You can now change the display mode, such as from All Monitors mode to Fullscreen mode, without having to disconnect from the desktop. Also, if you have Horizon Client use only one monitor, the client remembers which monitor was used the last time you launched the desktop. This preference is remembered on a per-desktop basis.
- Shade menu bar can be repositioned
When you use All Monitors mode or Fullscreen mode, a shade menu bar appears at the top of the window, in the center. You can now drag the shade menu bar horizontally if you need to slide it out of the way.
- Temporary removal of FIPS mode support
For security reasons, this release does not support FIPS (Federal Information Processing Standard) mode. If your company requires that clients be FIPS-enabled, do not upgrade to Horizon Client 3.4. Upgrade to Horizon Client 3.5.
New Features in Horizon Client 3.3
- 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.
New Features in Horizon Client 3.2
- Windows Media Multimedia redirection (MMR) -- Windows Media MMR, provided for Windows 7 and Windows 8/8.1 desktops and clients, redirects the multimedia stream directly to the client computer. Users can play videos in Windows Media Player or Internet Explorer. The feature supports the media formats that are supported on Windows Media Player. Windows Media MMR is supported on both 2D- and 3D-enabled desktops. Windows Media MMR is also supported on View Agent Direct-Connection desktops.
- Scanner redirection -- Scanner redirection allows View users to scan information in their remote desktops and applications with scanners that are connected locally to their client computers. This feature is supported on VDI desktops running on single-user machines and on RDS desktops and applications.
- Persistent settings in location-based printing -- Printer settings for location-based printers are retained after a user logs out or disconnects from the desktop. After the user logs in to the desktop again, the location-based printer continues to use the previously configured settings.
- Local IME support for remote applications -- When using non-English keyboards and locales, you can use an IME (input method editor) installed in your local system to send non-English characters to a remote hosted application. No IME is required on the RDS host.
Note: All of these features require that View Agent 6.0.2 be installed in the remote desktop. For more information, see the Release Notes for VMware Horizon 6.0.2 (with View).
New Features in Horizon Client 3.1
- Expanded virtual printing and location-based printing support -- The virtual printing and location-based printing features are now supported for single-session Windows Server 2008 R2 desktops, RDS desktops (that are hosted on virtual machine RDS hosts), and remote applications. You must be connected to an Horizon 6.0.1 with View server to use these features.
- USB 3.0 support -- Horizon Client 3.1, together with Horizon 6.0.1 with View, supports USB 3.0 devices plugged into USB 3.0 ports. USB 3.0 devices are supported only with a single stream. Because multiple stream support is not implemented in this release, USB device performance is not enhanced.
- USB channel encryption configuration -- You can now use the advanced SSL options that you use to encrypt communications between Horizon Client and the View server and View Agent to select security protocols and specify a cipher control string for the USB channel.
- Support for remote applications with system tray functionality -- Windows system tray items for remote applications now appear in the system tray of the Windows client system. This new feature enables important functionality that, for applications such as Skype and Evernote, is available only from the system tray.
- Hide the Horizon Client window after remote desktop or application launch -- After you launch a remote desktop or application from Horizon Client, you can now hide the Horizon Client window by clicking the X icon in the upper-right corner of the window. Clicking the X icon does not disconnect your sessions. You can also set a preference to always hide the Horizon Client window after a remote desktop or application has launched.
- New group policy setting for screen resolution -- You can use the client GPO template setting called Locked Guest Size to disable remote desktop auto-fit functionality if you use a PCoIP connection. Some restrictions apply. See Using VMware Horizon Client for Windows.
- Keyboard shortcuts added -- Keyboard shortcuts are now available for all actions and menu commands you can perform with Horizon Client. For a complete list, see Using VMware Horizon Client for Windows.
- Microsoft Lync integration is now also supported for Windows 8.x remote desktops.
New Features in Horizon Client 3.0
- Support for hosted applications -- With this release of Horizon Client for Windows, you can securely access remote Windows-based applications and remote desktops running in a VMware Horizon 6.0 environment.
- After launching Horizon Client for Windows and logging in to a Horizon 6.0 View server, you see all the remote applications that you are entitled to use, in addition to remote desktops. Selecting an application opens a window for that application on your Windows device. A remote application looks and behaves as if it were locally installed.
- A new -appName option has been added so that you can create URIs for connecting to a remote application by clicking a link in a Web page.
- Favorite remote desktops and applications - You can select remote desktops and applications as favorites in Horizon Client. Favorites are identified by a star. The star helps you quickly find your favorite desktops and applications. Your favorite selections are saved, even after you log off from the View server.
- Other user experience enhancements - In addition to the redesigned user interface with improved toolbar layout, the following features make connecting to a remove desktop or application quicker and easier:
- Create desktop shortcuts for remote applications and desktops and place them on your local Windows desktop.
- Right-click Horizon Client in your taskbar to use a jump list of recently used servers, desktops, and applications.
- Support for Windows Server 2008 R2 as a desktop
- Video enhancements -- If you connect to a Horizon 6 View desktop, the Real-Time Audio-Video feature uses a new kernel-mode webcam driver on View desktops that provides better compatibility with browser-based video apps and other third-party conferencing software.
- Idle session timeout enhancements -- For security purposes, administrators can set timeouts that log end users off of a server after a certain number of hours (the default is 10 hours) and that lock remote applications after a certain number of minutes of inactivity (the default is 15 minutes of inactivity).
The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, and Korean.
- VMware Horizon Client 4.0 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.
Resolved in Horizon Client 4.0
- Previously, if you used a Windows 10 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.
- A certificate authority name with a trailing space causes a mismatch between the certificate presented by Connection Server and the smart card certificate.
- When Horizon Client exits, it does not terminate the vmware-view.exe process.
Resolved in Horizon Client 3.5.1
- In Horizon Client 3.5.0, if you changed the default port from 443 to another port number and attempted to connect to a Horizon 6.2 desktop or application pool, you would temporarily see the application and desktops and then the client would exit unexpectedly. This issue has been resolved.
Resolved in Horizon Client 3.5
Previously, if you installed Horizon Client by using the command-line installer and specified that you wanted to use the "Log in as current user" feature, the "Log in as current user" check box would not be selected in the Login box. For example, entering the following command would not cause the "Log in as current user" check box to be selected after the client was installed:
VMware-Horizon-View-Client-x86_64-3.x.x-yyyyyyy.exe /s /v"/qn REBOOT=ReallySuppress ADDLOCAL=ALL LOGINASCURRENTUSER_DISPLAY=1 LOGINASCURRENTUSER_DEFAULT=1"This issue has been resolved.
- Previously, if you used the client drive redirection feature to share files on a USB device, if you disconnected from the remote desktop, unplugged the USB device, plugged in a different USB device to the same port, and then reconnected to the remote desktop, you would not be able to access files on the new USB device. This issue has been resolved.
Resolved in Horizon Client 3.4
- Previously, the mouse pointer would sometimes jump to the middle of a remote desktop window. For example, this issue could occur if you minimized or closed a window for an application other than Horizon Client, or if you restored a remote desktop window that had been minimized, or if you move your mouse pointer from another window to a remote desktop window, or while inside a remote desktop window, you pressed the Caps Lock key or Scroll Lock key so that the lock status on the client system is different from the lock status in the remote desktop. This issue has been resolved.
- Previously, the scanner redirection feature did not work with the Microsoft Fax and Scan application. This issue has been resolved.
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.
- Horizon Client for Windows 3.2.1 is the last version of Horizon Client that is supported for installing on Windows XP and Vista client operating systems. For more details, see Retiring Old OSes: XP, Vista, Mac OS X 10.6 & 10.7.
- Previously, if you wanted to change the display mode, such as from All Monitors mode to Fullscreen mode, you had to first disconnect from the desktop. This issue has been resoved only in Horizon Client 3.2.1 and 3.4. You can now right-click the system tray (notification area) icon on the client system to open the Settings window and change the display mode. For more information, see the online help topic called "Change the Display Mode While a Desktop Window Is Open." Although this topic states that you must have Horizon Client 3.4, the feature is also available in Horizon Client 3.2.1.
- Previously, the mouse pointer would sometimes jump to the middle of a remote desktop window. For example, this issue could occur if you minimized or closed a window for an application other than Horizon Client, or if you restored a remote desktop window that had been minimized, or if you move your mouse pointer from another window to a remote desktop window, or while inside a remote desktop window, you pressed the Caps Lock key or Scroll Lock key so that the lock status on the client system is different from the lock status in the remote desktop. This issue has been resolved only in Horizon Client 3.2.1 and Horizon Client 3.4.
- 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 in Horizon Client 3.2.0 and later releases.
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.
After you install Horizon Agent 7.0 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.
- With the multimedia redirection feature, if playback performance is slow, you might need to select an alternative graphics card. When two graphics cards are available, by default with one of the graphics cards, regular multimedia redirection is used. With Horizon Client 4.0 and later, you can select the alternative graphics card and the new shared surface multimedia redirection feature is used, which improves performance.
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 ate 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.
- For more information about known issues with features specific to Horizon 7 version 7.0, see the Release Notes for VMware Horizon 7 version 7.0.
- For more information about known issues with features specific to Horizon 6 version 6.2, see the Release Notes for VMware Horizon 6 version 6.2.
- 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).