Released 4 June 2015

Last Updated: 24 March 2016

These release notes include the following topics:

What's New in This Release of Horizon 6

VMware Horizon 6 version 6.1.1 resolves known issues in previous releases and provides the following new features and enhancements:

Client Drive Redirection

Users can share folders and drives on their local client systems with remote desktops and applications. Client Drive Redirection is supported on VDI desktops that run on single-user machines and on RDS desktops and applications. The feature is supported on Windows clients and, as a Tech Preview, on Mac OS X clients.

Users can share folders and drives on their local client systems with remote desktops and applications. Client Drive Redirection is supported on VDI desktops that run on single-user machines and on RDS desktops and applications. The feature is supported on Windows clients and, as a Tech Preview, on Mac OS X clients. Horizon 6 for Linux Desktops

You can now deploy Horizon 6 desktops on Linux virtual machines. With the View Agent for Linux installer, you can set up parent virtual machines or templates that run on Ubuntu, RHEL, CentOS, or NeoKylin and deploy Linux-based VDI desktop pools in View Administrator. You can configure Linux virtual machines to use vDGA to support 3D graphics applications running on NVIDIA GRID GPU cards. Some features such as SSO, automated provisioning, and local device redirection are not supported in this release. For details, see Setting Up Horizon 6 for Linux Desktops guide.

You can now deploy Horizon 6 desktops on Linux virtual machines. With the View Agent for Linux installer, you can set up parent virtual machines or templates that run on Ubuntu, RHEL, CentOS, or NeoKylin and deploy Linux-based VDI desktop pools in View Administrator. You can configure Linux virtual machines to use vDGA to support 3D graphics applications running on NVIDIA GRID GPU cards. Some features such as SSO, automated provisioning, and local device redirection are not supported in this release. For details, see Setting Up Horizon 6 for Linux Desktops guide. 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.

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.

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. HTML Access Support for Hosted Apps

Users can now connect to Hosted Apps from HTML Access Web clients. To take advantage of this feature, you must download and install a separate HTML Access installer from the Horizon 6 version 6.1.1 download page. For details, see To use HTML Access with Hosted Apps.

For information about the issues that are resolved in this release, see Resolved Issues.

Before You Begin

Important note about upgrading to ESXi 5.5 Update 3b or later If you plan to upgrade to ESXi 5.5 Update 3b or later releases, be aware that this version of View Agent as well as earlier versions are not compatible with the version of VMware Tools (10.0.0) that is bundled with ESXi Update 3b. To resolve the compatibility issue, see KB 2144518: Connecting to View desktops with Horizon View agent 6.0.x or 6.1.x hosted on ESXi 5.5 Update 3b or later fails with a black screen. SSLv3 is disabled by default on vSphere 5.5 Update 3b and later releases. This release of View is compatible with vSphere 5.5 Update 3b and later releases only if SSLv3 is enabled on vSphere. For instructions, see KB 2139396: Enabling SSLv3 protocol on vSphere 5.5.

The Horizon 6 release includes new configuration requirements that differ from past releases. Read the Readme document. This short overview can help you to avoid potential pitfalls when you install or upgrade to this release. The View Upgrades document provides upgrade instructions.

To use HTML Access with Hosted Apps: A separate HTML Access installer (version 3.4) is available on the Horizon 6 version 6.1.1 download page. Download and run this installer after you install or upgrade the other Horizon 6 components. Once you provide HTML Access version 3.4 to your users, they will not be able to connect to older View Agent desktops (version 6.1 or earlier) from their Web clients. Take these steps: Install or upgrade your View Connection Server instances to version 6.1.1. Note: When you install View Connection Server version 6.1.1 interactively, an older version of HTML Access (version 2.6) is installed. At this stage, Hosted Apps are not yet available through HTML Access. Users can continue to use HTML Access version 2.6 to connect to desktops running View Agent version 6.1. Install or upgrade View Agent to version 6.1.1 on all RDS hosts and VDI machines. Users of HTML Access version 2.6 can connect to desktops running View Agent version 6.1 or 6.1.1. From the Horizon 6 version 6.1.1 download page, download the HTML Access installer version 3.4 onto your View Connection Server instances and run the installer. Other important configuration steps are also required. For complete installation instructions, see Using HTML Access. For more information about the latest release of HTML Access, see the HTML Access Release Notes.

A separate HTML Access installer (version 3.4) is available on the Horizon 6 version 6.1.1 download page. Download and run this installer after you install or upgrade the other Horizon 6 components. Once you provide HTML Access version 3.4 to your users, they will not be able to connect to older View Agent desktops (version 6.1 or earlier) from their Web clients. Take these steps: For more information about the latest release of HTML Access, see the HTML Access Release Notes. To take advantage of Horizon 6 features such as Virtual SAN 2.0, GRID vGPU, and Virtual Volumes, install vSphere 6.0 and subsequent patch releases.

If your deployment uses RDS Per Device Client Access Licenses (CALs), follow the configuration guidelines in KB 2076660, Managing RDS Per Device CALs in View, before your end users begin connecting to RDS desktops and applications.

When you upgrade to this release, upgrade all View Connection Server instances in a pod before you begin upgrading View Agent, as described in the View Upgrades document.

The download page in this release includes a Horizon View HTML Access Direct-Connection file that provides web server static content for supporting HTML Access with View Agent Direct-Connection (VADC). For information about setting up HTML Access for VADC, see Setting Up HTML Access in the View Agent Direct-Connection Plug-in Administration guide.

Selecting the Scanner Redirection setup option with View Agent installation can significantly affect the host consolidation ratio.

To ensure the optimal host consolidation, make sure that the Scanner Redirection setup option is only selected for those users who need it. (By default, the Scanner Redirection option is not selected when you install View Agent.) For the particular users who need the Scanner Redirection feature, configure a separate desktop pool and select the setup option only in that pool.

To ensure the optimal host consolidation, make sure that the Scanner Redirection setup option is only selected for those users who need it. (By default, the Scanner Redirection option is not selected when you install View Agent.) For the particular users who need the Scanner Redirection feature, configure a separate desktop pool and select the setup option only in that pool. You must configure the back-end firewall to open TCP port 4002 to allow JMS (Java Message Service) traffic between security servers and View Connection Server instances. If there is a firewall between View desktops and Connection Servers, port 4002 must be open as well.

Top of Page

Internationalization

The View Administrator user interface, View Administrator online help, and Horizon 6 product documentation are available in Japanese, French, German, simplified Chinese, traditional Chinese, and Korean. For the documentation, see the Documentation Center for VMware Horizon 6.

Top of Page

Compatibility Notes

For the supported guest operating systems for View Agent on single-user machines and RDS hosts, see Supported Operating Systems for View Agent in the View Installation document.

For the supported Linux guest operating systems for View Agent, see System Requirements for Horizon 6 for Linux in the Setting Up Horizon 6 for Linux Desktops document.

Note: NeoKylin 6 (x64) and NeoKylin 6 Update 1 (x64) are now fully supported as Horizon 6 for Linux desktops on vSphere 6.0 and later releases.

NeoKylin 6 (x64) and NeoKylin 6 Update 1 (x64) are now fully supported as Horizon 6 for Linux desktops on vSphere 6.0 and later releases. For the supported operating systems for View Connection Server, security server, and View Composer, see System Requirements for Server Components in the View Installation document.

Horizon 6 functionality is enhanced by an updated set of Horizon Clients provided with this release.

For example, Horizon Client 3.3 or later is required for IPv6 and USB redirection of storage devices to RDS desktops and Hosted Apps. See the VMware Horizon Clients Documentation page for information about supported Horizon Clients.

For example, Horizon Client 3.3 or later is required for IPv6 and USB redirection of storage devices to RDS desktops and Hosted Apps. See the VMware Horizon Clients Documentation page for information about supported Horizon Clients. See the VMware Product Interoperability Matrix for information about the compatibility of View with current and previous versions of VMware vSphere. For vSphere 5.5 and 5.1, certain minimum express patches are recommended: vSphere 5.5 Update 1a with Express Patch 4 or later

vSphere 5.1 Update 2 with Express Patch 5 or later



For the supported Active Directory Domain Services (AD DS) domain functional levels, see Preparing Active Directory in the View Installation document.

For more system requirements, such as the supported browsers for View Administrator and View Portal, see the View Installation document.

For View Composer, VMware recommends that SSLv3 be disabled in the hosting Microsoft Server operating system (see Microsoft Security Advisory 3009008). SSLv3 is disabled by default in all other View components. This change addresses CVE-2014-3566, commonly known as the POODLE attack. If you need to enable SSLv3 in View, additional steps are required. See SSLv3 Is Disabled in View in the View Security document.

If a PCoIP Secure Gateway (PSG) has been deployed for PCoIP connections, zero client firmware must be version 4.0 or later.

When accessed from outside the corporate network, Client Drive Redirection (CDR) data is sent over an encrypted virtual channel from the remote client machine to the PCoIP security server. However, within the corporate network, the data is sent from the security server to the remote desktop without encryption. To ensure that this data cannot be monitored on the internal network, use CDR only on a secure network.

You can disable CDR by configuring a Microsoft Remote Desktop Services group policy setting in Active Directory. For details, see Managing Access to Client Drive Redirection in the Setting Up Desktop and Application Pools in View document.

You can disable CDR by configuring a Microsoft Remote Desktop Services group policy setting in Active Directory. For details, see Managing Access to Client Drive Redirection in the Setting Up Desktop and Application Pools in View document. The USB Redirection setup option in the View Agent installer is deselected by default. You must select this option to install the USB redirection feature. For guidance on using USB redirection securely, see Deploying USB Devices in a Secure View Environment in the View Security document.

The Global Policy, Multimedia redirection (MMR), defaults to Deny . To use MMR, you must open View Administrator, edit Global Policies, and explicitly set this value to Allow . To control access to MMR, you can enable or disable the Multimedia redirection (MMR) policy globally or for an individual pool or user.

Multimedia Redirection (MMR) data is sent across the network without application-based encryption and might contain sensitive data, depending on the content being redirected. To ensure that this data cannot be monitored on the network, use MMR only on a secure network.

. To use MMR, you must open View Administrator, edit Global Policies, and explicitly set this value to . To control access to MMR, you can enable or disable the Multimedia redirection (MMR) policy globally or for an individual pool or user. Multimedia Redirection (MMR) data is sent across the network without application-based encryption and might contain sensitive data, depending on the content being redirected. To ensure that this data cannot be monitored on the network, use MMR only on a secure network. Before you set the level of Transparent Page Sharing (TPS) in View Administrator, VMware recommends that the security implications be understood. For guidance, see the KB article, Security considerations and disallowing inter-Virtual Machine Transparent Page Sharing (2080735).

To use View Storage Accelerator in a vSphere 5.5 or later environment, a desktop virtual machine must be 512GB or smaller. View Storage Accelerator is disabled on virtual machines that are larger than 512GB. Virtual machine size is defined by the total VMDK capacity. For example, one VMDK file might be 512GB or a set of VMDK files might total 512GB. This requirement also applies to virtual machines that were created in an earlier vSphere release and upgraded to vSphere 5.5.

Horizon 6 does not support vSphere Flash Read Cache (formerly known as vFlash).

Top of Page

Prior Releases of View

Features that were introduced in prior releases of View are described in the release notes for each release, along with existing known issues.

Resolved Issues

The resolved issues are grouped as follows:

Configuration and View Administrator

In the Add Pool wizard in View Administrator, the monitor resolution drop-down list showed a 3840 X 2160 option, but this resolution is not supported. The unsupported option has been removed from View Administrator.

RDS Desktops and Applications

When you added an application pool in View Administrator, Windows Media Player could not be added.

Windows Media MMR

When you played a redirected video or audio file on a remote desktop, changing the playing speed in Windows Media Player (WMP) had no effect. The WMP timer displayed the changed playing speed, but the video or audio file continued to play at the original speed.

Smart Card

Smart card SSO failed when connecting over PCoIP to a Windows 8.1 desktop after the guest operating system was updated with a Microsoft update. This issue could be caused by various Windows 8.1 updates such as Microsoft KB 3013769.

View Persona Management

In Horizon 6.0.x and 6.1, synchronization of a user profile failed when the remote profile repository was mapped to the user's %HOMESHARE% directory. As a result, folder redirection did not work.

vSphere Platform Support

When disk space reclamation was enabled on Windows 8.1 linked clones, space reclamation operations ran every hour and did not shrink the virtual machine disks.

Windows 8/8.1 Support

After recent Windows updates were applied to Windows 8.1 desktops, Horizon Client users saw a black screen instead of the Windows 8.1 log-in screen and could not log in to their desktops. Other symptoms included Windows Event Viewer reporting unexpected termination of Windows services on the desktop operating system.

Top of Page

Known Issues

The known issues are grouped as follows:

Installation, Upgrade, and Uninstall Operations

When you upgrade View Agent 6.1 to View Agent 6.1.1 on an RDS host running on Windows Server 2012 or 2012 R2, the upgrade fails with an "Internal Error 25030" message.

Workaround: Uninstall View Agent 6.1, restart the RDS host, and install View Agent 6.1.1.

Uninstall View Agent 6.1, restart the RDS host, and install View Agent 6.1.1. If the scanner redirection feature was installed with View Agent 6.0.2, an in-place upgrade from View 6.0.2 to this release of View will not be possible. In this situation, you will have to uninstall View Agent 6.0.2 before you can install the View Agent 6.1.1 version.

The USB HUB device driver might not be installed properly when you install View Agent on a desktop in a manual desktop pool. This issue can occur if, during the View Agent installation, you restart the system before the USB HUB device driver is fully installed.

Workaround : When you install View Agent and you are prompted to restart the system, check the system tray to see if the USB HUB device driver software is still being installed. Wait until the device driver software is completely installed (typically about 30 seconds) before you restart the system.

If you use a command-line script to install View Agent silently, make sure to wait or sleep the script for long enough to allow the driver installation to complete before you restart the system.

If you encounter this issue after View Agent is installed, or you could not delay the system restart during a silent installation, update the USB HUB device driver by taking these steps:

1. In the Device Manager, under Other Devices , right-click VMware View Virtual USB Hub .

2. Click Update Driver Software > Browse my computer for driver software .

3. Go to C:\Program Files\VMware\VMware View\Agent\bin\drivers and click Next to let Windows install the driver.

: When you install View Agent and you are prompted to restart the system, check the system tray to see if the USB HUB device driver software is still being installed. Wait until the device driver software is completely installed (typically about 30 seconds) before you restart the system. If you use a command-line script to install View Agent silently, make sure to wait or sleep the script for long enough to allow the driver installation to complete before you restart the system. If you encounter this issue after View Agent is installed, or you could not delay the system restart during a silent installation, update the USB HUB device driver by taking these steps: 1. In the Device Manager, under , right-click . 2. Click . 3. Go to and click to let Windows install the driver. To upgrade a desktop from Windows 8 to Windows 8.1, you must uninstall View Agent, upgrade the operating system from Windows 8 to Windows 8.1, and then reinstall View Agent. Alternatively, you can perform a fresh installation of Windows 8.1 and then install View Agent.

If you upgrade to vSphere 5.5 or a later release, verify that the domain administrator account that you use as the vCenter Server user was explicitly assigned permissions to log in to vCenter Server by a vCenter Server local user.

USB redirection fails in linked-clone images after you upgrade the master image from View Agent 5.1. x or earlier to the current View Agent version. This issue does not occur if you upgrade from View Agent 5.2 or later to the current version.

Workaround : See KB 2062215: USB redirection fails in linked-clone images after you upgrade to View Agent 5.3.

or earlier to the current View Agent version. This issue does not occur if you upgrade from View Agent 5.2 or later to the current version. : See KB 2062215: USB redirection fails in linked-clone images after you upgrade to View Agent 5.3. When you run the View Agent installer on a Windows 8 virtual machine, the Windows desktop appears black when the video driver is being installed. The Windows desktop might appear black for several minutes before the installation completes successfully.

Workaround : Apply the Windows 8.0 May 2013 roll-up before you install View Agent. See Microsoft KB article 2836988.

: Apply the Windows 8.0 May 2013 roll-up before you install View Agent. See Microsoft KB article 2836988. When you run any View installer on a Windows 8.1 or Windows Server 2012/2012 R2 virtual machine (deployed as an RDS host or VDI desktop), the installer can take an unusual amount of time to finish. This problem occurs if the virtual machine's domain controller, or another domain controller in its hierarchy, is unresponsive or unreachable.

Workaround : Verify that the domain controllers have the latest patches, enough free disk space, and can communicate with each other.

: Verify that the domain controllers have the latest patches, enough free disk space, and can communicate with each other. When you uninstall View Agent from an RDS host, an error dialog can be displayed, which prevents the uninstall operation from being completed. The dialog states that the uninstall operation failed to stop an RDS video driver. This issue can occur when disconnected desktop sessions are still running on the RDS host.

Workaround: Reboot the RDS host to complete the uninstallation of View Agent. As a best practice, ensure that all RDS sessions are logged off before you uninstall View Agent.

RDS Desktops and Applications

Persistent settings for location-based printers are not supported if the settings are saved in the printer driver's private space and not in the DEVMODE extended part of the printer driver, as recommended by Microsoft.

Workaround: Use printers that have the user preference settings saved in the DEVMODE part of the printer driver.

Use printers that have the user preference settings saved in the DEVMODE part of the printer driver. View Agent cannot install the virtual printing feature on RDS hosts that are physical machines. Virtual printing is supported on RDS desktops when View Agent is installed on RDS hosts that are virtual machines.

Workaround: Configure RDS hosts on virtual machines and install View Agent.

Configure RDS hosts on virtual machines and install View Agent. A single client device connecting to RDS desktops and applications over PCoIP can use up more than one RDS Per Device Client Access License (CAL). This issue does not occur if your deployment uses RDS Per User CALs, if the clients connect to View through RDP, or if you deploy only one license server and all your RDS hosts run the same guest operating system.

Workaround: Follow the configuration guidelines in KB 2076660, Managing RDS Per Device CALs in View, before your end users begin connecting to RDS desktops and applications.

Follow the configuration guidelines in KB 2076660, Managing RDS Per Device CALs in View, before your end users begin connecting to RDS desktops and applications. In a desktop session running on a Windows Server 2008 R2 SP1 RDS host, you cannot play back an H.264 video file, or play back AAC audio with a video file, in Windows Media Player. This is a known third-party issue.

Workaround: Go to the Microsoft KB article 2483177 and download the Desktop Experience Decoder Update for Windows Server 2008 R2 package.

Go to the Microsoft KB article 2483177 and download the package. When you play a YouTube video in a Chrome browser in a desktop session running on a Windows Server 2012 R2 RDS host, the video display can be corrupted. For example, black boxes might pop up in the browser window. This issue does not occur on any other browser or on Windows Server 2008 R2 SP1 RDS hosts.

Workaround: In your Chrome browser, select Chrome > Settings > Show advanced settings > System , and deselect Use hardware acceleration when available .

In your Chrome browser, select , and deselect . If you play a video in a desktop running on a Windows 2008 R2 SP1 physical RDS host, and you move the video display from the main monitor to another monitor, the video stops playing or the visual frames stop updating (although the audio might continue to play). This issue does not occur on a virtual machine RDS host or in a single monitor configuration, and it only occurs on Windows Server 2008 R2 SP1.

Workaround: Play videos on the main monitor only, or configure your RDS desktop pool on a virtual machine RDS host.

Play videos on the main monitor only, or configure your RDS desktop pool on a virtual machine RDS host. If you launch a remote application that becomes unresponsive and then launch another application, the second application's icon is not added to the taskbar on the client device.

Workaround: Wait for the first application to become responsive. (For example, an application might be unresponsive while large files are being loaded.) If the first application continues to be unresponsive, terminate the application process on the RDS virtual machine.

Wait for the first application to become responsive. (For example, an application might be unresponsive while large files are being loaded.) If the first application continues to be unresponsive, terminate the application process on the RDS virtual machine. The application Lync 2013 that does not have the February, 2013 update and is hosted on an RDS host running Windows Server 2012 R2 will crash shortly after launch with the error message "Microsoft Lync has stopped working." This is a known issue with Lync 2013. Workaround: Apply the February, 2013 update of Lync. The update is available at Microsoft KB article 2812461.

Configuration and View Administrator

When using View Administrator from a Firefox browser, if you enter Korean characters in a text field using the Korean Input Method Editor (IME), the Korean characters are not displayed correctly. This issue occurs only with Firefox. This is a 3rd-party issue.

Workaround: Use a different browser. If you still want to use Firefox, input Korean characters one by one.

Use a different browser. If you still want to use Firefox, input Korean characters one by one. If you change the VMware View Blast Secure Gateway ( absg.log ) log level on a View Connection Server instance from Info to Debug , the log level remains Info . (You change the log level by opening the Set View Connection Server Log Levels on a View Connection Server instance, changing the absg log level, and restarting the VMware View Blast Secure Gateway service.) Changing the log level from Debug to Info works properly.

Workaround: None.

) log level on a View Connection Server instance from to , the log level remains . (You change the log level by opening the on a View Connection Server instance, changing the log level, and restarting the VMware View Blast Secure Gateway service.) Changing the log level from to works properly. None. The View PCoIP ADM ( pcoip.adm ) group policy setting, Configure SSL connections to satisfy Security Tools , is not supported in this release of View. If you attempt to implement certain options in this group policy setting, unexpected results might occur in your View deployment.

Workaround: Do not use this setting in this release of View.

) group policy setting, , is not supported in this release of View. If you attempt to implement certain options in this group policy setting, unexpected results might occur in your View deployment. Do not use this setting in this release of View. Setting the size of the retry port range to 0 when configuring the Configure the TCP port to which PCoIP Server binds and listens or Configure the UDP port to which PCoIP Server binds and listens group policy causes a connection failure when users log in to the desktop with the PCoIP display protocol. Horizon Client returns the error message The Display protocol for this desktop is currently not available. Please contact your system administrator . The help text for the group policies incorrectly states that the port range is 0 through 10.

Note : On RDS hosts, the default base TCP and UDP port is 4173. When PCoIP is used with RDS hosts, a separate PCoIP port is used for each user connection. The default port range that is set by the Remote Desktop Service is large enough to accommodate the expected maximum of concurrent user connections.

Workaround :

PCoIP on single-user machines : Set the retry port range to a value between 1 and 10. (The correct port range is 1 through 10.)

PCoIP on RDS hosts : As a best practice, do not use these policy settings to change the default port range on RDS hosts, or change the TCP or UDP port value from the default of 4173. Most important, do not set the TCP or UDP port value to 4172. Resetting this value to 4172 will adversely affect PCoIP performance in RDS sessions.

or group policy causes a connection failure when users log in to the desktop with the PCoIP display protocol. Horizon Client returns the error message . The help text for the group policies incorrectly states that the port range is 0 through 10. : On RDS hosts, the default base TCP and UDP port is 4173. When PCoIP is used with RDS hosts, a separate PCoIP port is used for each user connection. The default port range that is set by the Remote Desktop Service is large enough to accommodate the expected maximum of concurrent user connections. : : Set the retry port range to a value between 1 and 10. (The correct port range is 1 through 10.) : As a best practice, do not use these policy settings to change the default port range on RDS hosts, or change the TCP or UDP port value from the default of 4173. Most important, do not set the TCP or UDP port value to 4172. Resetting this value to 4172 will adversely affect PCoIP performance in RDS sessions. On rare occasions, the system health status of Event Database may be displayed as red on the View Administrator dashboard, with the error message "Cannot drop the view 'VE_user_events', because it does not exist or you do not have permission." This condition does not indicate a real error and will resolve itself after a short period of time. Workaround: None.

Horizon Client and Remote Desktop Experience

If vDGA is enabled on a Windows 7 virtual machine that is configured to use NVIDIA driver version 347.25, the desktop session can be disconnected. This issue does not occur on Windows 8.1 or on other NVIDIA driver versions.

Workaround: Do not use NVIDIA driver version 347.25.

Do not use NVIDIA driver version 347.25. Microsoft Lync does not pair properly when Microsoft Office 2013 SP1 update KB 2850036 is installed on a Windows 7 Horizon Client for Windows. This issue does not occur on Windows 8 Horizon Client for Windows.

Workaround: Uninstall the update (KB 2850036) from Microsoft Office 2013 SP1.

Uninstall the update (KB 2850036) from Microsoft Office 2013 SP1. On Windows 8/8.1 desktops, 3D screensavers operate even when the 3D Renderer setting is disabled, and the screensavers do not render correctly. This issue does not occur on Windows 7 desktops.

Workaround: Make sure your end users do not use 3D screensavers, or enable the 3D Renderer setting for the desktop pool.

Make sure your end users do not use 3D screensavers, or enable the 3D Renderer setting for the desktop pool. If a Linux client 2.3.4 connects to a Horizon 6.0.1 View Agent, and the status of the remote desktop is "available" (not "disconnected"), clipboard redirection between the desktop and client device does not work. This issue occurs even when the View PCoIP General Session Variable group policy setting, Configure clipboard redirection , is set to Enabled in both directions .

Workaround: Disconnect and reconnect to the desktop, or upgrade the Linux client to version 3.1.

, is set to . Disconnect and reconnect to the desktop, or upgrade the Linux client to version 3.1. Horizon clients cannot connect to View Connection Server if the server name or fully qualified domain name (FQDN) for View Connection Server contains non-ASCII characters.

Workaround: None.

None. On desktops that connect using PCoIP and are configured with multiple monitors, if a user plays a slide show in Microsoft PowerPoint 2010 or 2007, specifies a resolution, and plays the slides on the second monitor, part of each slide appears on each monitor.

Workaround: On the host client system, resize the screen resolution on the second monitor to the desired resolution. Return to the View desktop and start the slide show on the second monitor.

On the host client system, resize the screen resolution on the second monitor to the desired resolution. Return to the View desktop and start the slide show on the second monitor. On desktops that connect using PCoIP, if users play slides in Microsoft PowerPoint 2010 or 2007 and specify a resolution, the slides are played at that chosen resolution and are not scaled to the current resolution.

Workaround: Choose "Use current resolution" as the playback resolution.

Choose "Use current resolution" as the playback resolution. The virtual printing feature is supported only when you install it from View Agent. It is not supported if you install it with VMware Tools.

When you play videos in Windows Media Player on a desktop, PCoIP disconnections might occur under certain circumstances.

Workaround : On the desktop, open the Windows registry and navigate to the HKLM\Software\Wow6432Node\Policies\Teradici\PCoIP\pcoip_admin_defaults registry key for 64-bit Windows or the HKLM\Software\Policies\Teradici\PCoIP\pcoip_admin_defaults registry key for 32-bit Windows. Add the pcoip.enable_tera2800 DWORD registry value and set the value to 1.



: On the desktop, open the Windows registry and navigate to the registry key for 64-bit Windows or the registry key for 32-bit Windows. Add the registry value and set the value to 1. For Windows 2008 R2 SP1 desktop pools hosted on an RDS host, the language sync setting (from client to guest) is turned on by default and cannot be turned off. Therefore, disabling the group policy "Turn on PCoIP user default input language synchronization" for View Agent has no effect. The remote desktop language always synchronizes with the language used on the client system.

Workaround: None.

None. On a Windows 8, Windows 8.1 or WIndows 2012 desktop, if you change the display DPI from the default value, the mouse may stop working.

Workaround: See KB 2060701: Erratic mouse movement causes issues with VMware Horizon View 5.2 PCoIP connections.

Horizon 6 for Linux Desktops

Configuring four monitors at 2560x1600 resolution on RHEL 6.6 or CentOS 6.6 virtual machines in vSphere 6.0 is not supported.

Workaround : Use 2048x1536 resolution or deploy this configuration in vSphere 5.5.

: Use 2048x1536 resolution or deploy this configuration in vSphere 5.5. If you configure two or more monitors at 2560x1600 resolution on RHEL 6.6 virtual machines in a vDGA environment, desktop performance is poor. For example, application windows do not move smoothly. This issue occurs when RHEL Desktop Effects are enabled.

Workaround: Disable Desktop Effects by going to System > Preference > Desktop Effects and selecting Standard.

Windows Media MMR

Windows Media MMR does not perform ideally on certain graphics cards, such as certain AMD models, which have slow video memory read back performance.

Workaround: None

None If you switch browser tabs while playing a redirected video in Internet Explorer, part of the video window continues to be displayed behind or next to the browser window. This issue only occurs on Windows 7 desktops.

Workaround: Use Windows 8.1 desktops. Alternatively, do not switch to another tab while a redirected video is playing.

Smart Card

Using a smart card to log in to an RDS desktop takes longer than with a VDI, single-user desktop. This issue is less acute on Windows clients than other clients.

Workaround: None.

None. On Windows 7 client machines, Horizon Client exits when the smart card removal policy is triggered.

Client Drive Redirection

If you disable client drive redirection with the Microsoft Remote Desktop Services group policy setting, Do not allow drive redirection, users can still select the Options > Share Folders option in Horizon Client and use the UI to select shared drives. The drives are not shared and do not appear in the remote desktop. This issue does not occur if you do not install the Client Drive Redirection option when you install View Agent.

Workaround: None.

Scanner Redirection

Selecting the Scanner Redirection setup option with View Agent installation can significantly affect the host consolidation ratio. By default, the Scanner Redirection option is not selected when you install View Agent.

Workaround: Make sure that the Scanner Redirection setup option is not selected for most users. For the particular users who need the Scanner Redirection feature, configure a separate desktop pool and select the setup option only in that pool.

Make sure that the Scanner Redirection setup option is not selected for most users. For the particular users who need the Scanner Redirection feature, configure a separate desktop pool and select the setup option only in that pool. Sometimes the scanner settings do not take effect on WIA scanners. For example, if you select grayscale mode and select a partial area of the original image, the scanner might use color and scan the whole image.

Workaround: Use a TWAIN scanner.

Use a TWAIN scanner. In some environments, if you switch to a different WIA scanner, the images might continue to be scanned from the original scanner.

Workaround: Log off the View desktop session. Launch a new desktop session and perform the scan using the selected scanner.

Log off the View desktop session. Launch a new desktop session and perform the scan using the selected scanner. When you uninstall View Agent 6.1.1 with the Scanner Redirection feature installed, the uninstall process requires you to close any running applications.

Workaround: None. You must close the listed applications before you continue to uninstall View Agent.

Serial Port Redirection

The Bandwidth limit group policy setting does not take effect. The value you enter in the setting is ignored, and the existing bandwidth is used for serial port redirection. The bandwidth consumption depends on the number of concurrently used serial port devices and the baudrate used by each device.

Workaround: None.

View Persona Management

View Persona Management might not correctly replicate a user persona to the central repository if the desktop virtual machine is extremely low on disk space.

With View Persona Management, you can use group policy settings to redirect user profile folders to a network share. When a folder is redirected, all data is stored directly on the network share during the user session. Windows folder redirection has a check box called Grant user exclusive rights to folder-name , which gives the specified user exclusive rights to the redirected folder. As a security measure, this check box is selected by default. When this check box is selected, administrators do not have access to the redirected folder. If an administrator attempts to force change the access rights for a user's redirected folder, View Persona Management no longer works for that user .

Workaround : See KB 2058932: Granting domain administrators access to redirected folders for View Persona Management.

, which gives the specified user exclusive rights to the redirected folder. As a security measure, this check box is selected by default. When this check box is selected, administrators do not have access to the redirected folder. If an administrator attempts to force change the access rights for a user's redirected folder, View Persona Management no longer works for that user : See KB 2058932: Granting domain administrators access to redirected folders for View Persona Management. View Persona Management is not supported on session-based desktop pools that run on RDS hosts.

Workaround: Install View Persona Management in automated or manual desktop pools that run on single-user machines.

vSphere Platform Support

View Storage Accelerator might take tens of minutes to generate or regenerate the digest files for large virtual disks (for example, a 100GB virtual disk). As a result, the desktop might be inaccessible for longer than expected.

Workaround : Use the blackout period to control when digest regeneration operations are allowed. Also, use the digest regeneration interval to reduce the frequency of these operations. Alternatively, disable View Storage Accelerator in desktop pools that contain very large virtual machines.

: Use the blackout period to control when digest regeneration operations are allowed. Also, use the digest regeneration interval to reduce the frequency of these operations. Alternatively, disable View Storage Accelerator in desktop pools that contain very large virtual machines. If a linked-clone pool consists of vSphere 5.5 virtual machines, a View Composer rebalance operation can fail with a FileAlreadyExists error. This problem occurs only when the desktop pool uses different datastores for the OS disk and the user data disk and the datastore selection for the user data disk changes before the View Composer rebalance operation takes place.

Workaround : Detach the persistent disk from the linked clone desktop that has the FileAlreadyExists error. Later, you can attach the archived disk to a new virtual machine and recreate the linked-clone desktop or attach it to an existing linked-clone desktop as a secondary disk. You can prevent this problem from occurring by either keeping the OS disk and user data disk on the same datastore or by not changing the datastore selections before a View Composer rebalance operation.

error. This problem occurs only when the desktop pool uses different datastores for the OS disk and the user data disk and the datastore selection for the user data disk changes before the View Composer rebalance operation takes place. : Detach the persistent disk from the linked clone desktop that has the error. Later, you can attach the archived disk to a new virtual machine and recreate the linked-clone desktop or attach it to an existing linked-clone desktop as a secondary disk. You can prevent this problem from occurring by either keeping the OS disk and user data disk on the same datastore or by not changing the datastore selections before a View Composer rebalance operation. After you upgrade to vSphere 5.5, a heap size error can occur if you use space-efficient virtual disks and you have more than 200 linked-clone virtual machines per ESXi host. For example: Error: Heap seSparse could not be grown by 12288 bytes for allocation of 12288 bytes

Workaround: Reduce the number of linked-clone virtual machines that use space-efficient virtual disks to less than 200 per ESXi host.



View Composer

If you upgrade a virtual machine with an IDE controller from Windows XP to Windows 7, take a snapshot of the virtual machine, and create a linked-clone pool, the linked clones cannot be customized, and pool creation fails.

Workaround: Add a SCSI controller and a disk to the virtual machine. Next, launch VMware Tools and install a VMware SCSI controller driver on the virtual machine. Next, take a snapshot and create the linked-clone pool.

Add a SCSI controller and a disk to the virtual machine. Next, launch VMware Tools and install a VMware SCSI controller driver on the virtual machine. Next, take a snapshot and create the linked-clone pool. When you provision linked-clone desktops that are customized by Sysprep, some desktops might fail to customize.

Workaround: Refresh the desktops. If a small number of desktops still fail to customize, refresh them again.

Refresh the desktops. If a small number of desktops still fail to customize, refresh them again. Do not change the log on account for the VMware View Composer Guest Agent Server service in a parent virtual machine. By default, this is the Local System account. If you change this account, the linked clones created from the parent do not start.

Desktop pool provisioning fails with the error message Polling progress failure: Unable to connect to View Composer server <https://machine-name:18443>: java.net.ConnectException: Connection refused: connect.

Workaround: Restart the VMware vCenter Server service and then reprovision the desktop pool.

Windows 8 and 8.1 Support

On some occasions, when you reconnect to a Windows 8 or 8.1 desktop session, you might not see the desktop display immediately. A black screen might be displayed for up to 20 seconds.

Workaround: None

None When a space reclamation operation is run for Windows 8 or 8.1 linked clone virtual machines, the size of the system disposable disk and user persistent disk might increase to its maximum capacity. This space increase only happens the first time space reclamation is done. For the OS disk, space reclamation works as expected and reclaims the unused space. This issue does not affect View Composer desktops that do not use system disposable disks or user persistent disks.

Workaround : When you configure View Composer desktops on Windows 8 or 8.1 virtual machines and enable space reclamation, do not configure system disposable disks or user persistent disks.

: When you configure View Composer desktops on Windows 8 or 8.1 virtual machines and enable space reclamation, do not configure system disposable disks or user persistent disks. Adobe Flash optimization settings that use high quality and aggressive throttling are not fully enabled when end users use Internet Explorer 10 or Internet Explorer 11 on Windows 8 or Windows 8.1 desktops.

Workaround : None.

: None. On a Windows 8 desktop, if you enable the View Persona Management setting, Remove local persona at logoff , and a user creates a PDF file, logs off of the desktop, and logs back in again, the user cannot open the offline PDF file. The Windows 8 Reader cannot download the offline PDF content.

Workaround : Manually download the file by right-clicking the file and selecting Properties or selecting Open with... Adobe Reader .

, and a user creates a PDF file, logs off of the desktop, and logs back in again, the user cannot open the offline PDF file. The Windows 8 Reader cannot download the offline PDF content. : Manually download the file by right-clicking the file and selecting or selecting . When using Internet Explorer 10 on a Windows 8 computer, if you set the browser locale to Traditional Chinese or Simplified Chinese, and you log in to View Administrator, the UI is displayed in English. Note: This issue occurs with IE 10 on Windows 8 and is not a VMware View issue.

Workaround : Use an alternate browser to log in to View Administrator.

: Use an alternate browser to log in to View Administrator. If a user of a Windows 8 View desktop logs in using Kerberos authentication, and the desktop is locked, the user account for unlocking the desktop that Windows 8 shows the user by default is the related Windows Active Directory account, not the original account from the Kerberos domain. The user does not see the account he or she logged in with.

This is a Windows 8 issue, not directly a View issue. This issue could, but does not usually, occur in Windows 7.

Workaround : The user must unlock the desktop by selecting "Other user." Windows then shows the correct Kerberos domain and the user can log in using the Kerberos identity.

This is a Windows 8 issue, not directly a View issue. This issue could, but does not usually, occur in Windows 7. : The user must unlock the desktop by selecting "Other user." Windows then shows the correct Kerberos domain and the user can log in using the Kerberos identity. When provisioning 64- or 32-bit Windows 8 desktops in a vSphere 5.1 environment, the Sysprep customization can fail. The desktops end up in an ERROR state with a Customization timed out error message. This issue occurs when anti-virus software is installed in the parent virtual machine or template. The issue applies to full clone and linked clone desktops. It does not apply to linked clone desktops customized with QuickPrep.

Workaround : Uninstall the anti-virus software on the parent virtual machine or template and recreate the pool.

error message. This issue occurs when anti-virus software is installed in the parent virtual machine or template. The issue applies to full clone and linked clone desktops. It does not apply to linked clone desktops customized with QuickPrep. : Uninstall the anti-virus software on the parent virtual machine or template and recreate the pool. When recomposing Windows 8.1 desktops, the Sysprep customization can fail with a Customization operation timed out error message. This problem is caused by a Windows 8.1 scheduled maintenance task that recovers disk space by removing unused features.

Workaround: Use the following command to disable the maintenance task immediately after completing Setup: Schtasks.exe /change /disable /tn "\Microsoft\Windows\AppxDeploymentClient\Pre-staged app cleanup"

Windows Server for Desktop Use

You cannot connect to a Windows Server 2008 R2 SP1 desktop, or you encounter a black screen the first time that you use Horizon Client, even though the desktop that you are connecting to is in the Available state.

Workaround: Shut down and power on the Windows Server 2008 R2 SP1 virtual machine. When the desktop is in the Available state, try to connect again. Note: Resetting or restarting the virtual machine does not solve this problem. You must shut down the virtual machine first and then power it back on.

Horizon Workspace Integration

If you change the default HTTPS port, 443, on a View Connection Server instance or security server, and Horizon users try to start their desktops from the Horizon User Portal, the desktops fail to launch. This issue occurs when users attempt to access their desktops via Horizon Workspace with either Horizon Client or HTML Access.

Workaround : Keep the default HTTPS port 443.

: Keep the default HTTPS port 443. When you add a SAML Authenticator in View Administrator, an "Invalid certificate detected" window might be displayed, even when the Metadata URL points to a trusted certificate in the Trusted Root Certificate Authorities folder in the Windows certificate store. This issue can occur when an existing SAML Authenticator with a self-signed certificate was using the same Metadata URL when the trusted certificate was added to the Windows certificate store.

Workaround: Remove any trusted certificates for the Metadata URL from the Trusted Root Certificate Authorities folder in the Windows certificate store. Remove the SAML Authenticator with the self-signed certificate. Add the trusted certificate for the Metadata URL to the Trusted Root Certificate Authorities folder in the Windows certificate store. Add the SAML Authenticator again.



Virtual SAN and Virtual Volumes

In this release, View Storage Accelerator is not supported on Virtual Volume datastores.

Workaround: None

None Provisioning View Composer linked clones fails on some Virtual Volumes storage arrays. The following message is displayed: "Error creating disk Error creating VVol Object. This may be due to insufficient available space on the datastore or the datastore's inability to support the selected provisioning type." View Composer creates a small internal disk in thick-provisioned format, although all other linked clone disks use thin provisioning. This issue occurs if the 3rd-party Virtual Volumes storage array does not support thick-provisioned disks by default.

Workaround : Enable thick provisioning on the storage array to allow Virtual Volumes to create thick-provisioned disks.

: Enable thick provisioning on the storage array to allow Virtual Volumes to create thick-provisioned disks. When you attach or recreate a View Composer persistent disk stored on a Virtual SAN datastore, the virtual disk's storage policy in vCenter Server is shown as "Out of date." The original storage profile is not preserved.

Workaround: In vSphere Web Client, reapply the storage policy to the virtual disks.

In vSphere Web Client, reapply the storage policy to the virtual disks. Virtual SAN datastores are only accessible from hosts that belong to the Virtual SAN cluster, and not from hosts that belong to a different cluster. Therefore, rebalance of pools from one Virtual SAN datastore to another Virtual SAN datastore in a different cluster is not supported.

In an environment where a large VDI desktop pool (for example, 2,000 desktops) is created on Virtual Volumes datastores that reside on a NetApp storage system running ONTAP 8.2.x or earlier, a recompose operation may fail for a small number of desktops with the error message "The VVol target encountered a vendor specific error."

Workaround: Upgrade the NetApp storage system to ONTAP 8.3 or later.

Cloud Pod Architecture

Cloud Pod Architecture configuration changes made by another View administrator while you are logged in to View Administrator are not visible in your current View Administrator session.

Workaround: Log out of View Administrator and log in again to see the changes.

Miscellaneous

For virtual machines that have hardware version 8, the maximum allowed video RAM is 128MB. For virtual machines that have hardware version 9 and later, the maximum allowed video RAM is 512MB. If you configure a value from View Administrator that exceeds the video RAM limit for a virtual machine's hardware version, errors appear in the vSphere Client Recent Tasks pane and the configuration operation keeps repeating. This problem occurs only if you configure the video memory value through View Administrator (Pool Settings page) and not through vSphere Client.

Workaround: Either upgrade the hardware version of the virtual machines in vSphere Client, or use View Administrator to set the proper value for video memory based on the current virtual machine hardware version.

Top of Page