VMware Horizon View 5.2 Release Notes

Released 4 March 2013 | View Manager Build 987719, View Composer Build 983460

Last Updated: 26 March 2016

These release notes cover the following topics:

What's New in Horizon View 5.2

VMware Horizon View 5.2 delivers valuable enhancements to end user experience and ease of management, while further driving down the total cost of ownership for VDI.

What's New with End User Experience

  • Support for Windows 8 based desktops1
  • Hardware Accelerated 3D Graphics1
  • Improved video and VOIP communications with Microsoft Lync 2013 support4
  • Streamlined access to View Desktops from Horizon2
  • Easily connect to desktops from any device with HTML Access3
  • Enhanced productivity from mobile devices with new 'Unity Touch' functionality3 and 4

What's New with Ease of Management

  • Large pool creation with elimination of 8 host limits, and multiple vLAN support
  • View Administrator performance improvements with large numbers of desktops
  • Accelerated provisioning and recompose operations.
  • Tech Preview of a new Integrated Service Console in the vSphere Web Client1
  • Support for vCenter Server Virtual Appliance based deployments

What's New with Total Cost of Ownership

  • Substantial storage capacity savings for persistent desktops with space-efficient (SE sparse) disk technology1
1 Requires use of vSphere 5.1 and subsequent patches
2 Requires use of VMware Horizon Suite
3 Requires use of additional VMware Horizon View 5.2 Feature Pack
4 Requires use of latest VMware Horizon View Clients

Before You Begin

Important note about upgrading to ESXi 5.5 Update 3b or later

VMware View 5.1 and later releases include new configuration tasks and requirements that differ from past releases. Please read the Horizon View Readme First document. This short overview can help you to avoid potential pitfalls when you install Horizon View 5.2 or upgrade to Horizon View 5.2 from View 5.0.x or earlier releases.

To take advantage of the latest Horizon View enhancements, be sure to use the latest View Clients and vSphere releases.

  • Install the latest Horizon View Client releases (as of March 2013, 5.3 for Windows or 2.0 for Linux, Mac, iOS, Android, and Windows Store). This includes installing the latest software/firmware updates for your Thin clients or Zero clients, as appropriate.
  • Install the latest version of vSphere 5.1 and subsequent patch releases to take advantage of the latest storage and graphics capabilities in Horizon View.

Top of Page


The View Administrator user interface and View Administrator online help are available in Japanese, French, German, simplified Chinese, traditional Chinese, and Korean. The following Horizon View documents are also available in these languages: VMware Horizon View Readme, VMware Horizon View Administration, VMware Horizon View Installation, VMware Horizon View Upgrades, VMware Horizon View Security, and VMware Horizon View Architecture Planning.

Top of Page

Compatibility Notes

  • VMware Horizon View 5.2 is supported on the following versions of VMware vSphere:
    • vSphere 5.5
    • vSphere 5.1 with download patch ESXi510-201210001 or later
      Space efficient disk technology and the disk space reclamation feature require the use of vSphere 5.1 with download patch ESXi510-201212001 or later.
    • Earlier vSphere releases
      See the VMware Product Interoperability Matrix for more details about the compatibility of VMware Horizon View 5.2 with current and previous versions of VMware vSphere.
  • For the supported browsers for View Administrator and View Portal, see the VMware Horizon View Installation document.
  • For more system requirements, see the VMware Horizon View Installation document.
  • For more compatibility guidelines, see the Horizon View Readme First document.
  • The functionality of VMware Horizon View 5.2 is enhanced by an updated set of VMware Horizon View Clients and a new VMware Horizon View 5.2 Feature Pack. These components will be made available shortly after the general availability of VMware Horizon View 5.2 and may subject to app availability in various mobile device application stores. See footnotes "3" and "4" under What's New in Horizon View 5.2 for guidance on which pieces of functionality are enabled by these components.
  • In addition to the supported databases listed in the installation documentation, VMware Horizon View 5.2 now also supports Oracle databases.
  • VMware Horizon View does not support Windows 2012 Active Directory. You can use Windows 2003 Active Directory and Windows 2008 Active Directory with VMware Horizon View.

Top of Page

Prior Releases of VMware Horizon View

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

Resolved Issues

The resolved issues are grouped as follows:

View Administrator

  • In the Korean View Administrator, online help links displayed the help in English.

View Client

  • If a View Client for iOS device was rotated quickly while the client was in the process of connecting to a View desktop, the device could disconnect.
  • If you configured USB device splitting, and a USB device such as the Philips Speechmike was physically unplugged from the client system while the device was assigned to View, View Client locked up and could not access the View desktop. (A device that is assigned to View has a tick beside its name in the View Client USB menu.)
  • If you locked and then unlocked the client system while playing a video in the desktop with multi-media redirection (MMR) enabled, playback did not continue.

View Composer

  • If automatic recovery was enabled, and if a refresh operation failed, the affected desktops could be restarted and presented in a Ready state, even though they were not refreshed. Now the desktops will be left in an error state if the failure cannot be recovered.

Top of Page

Known Issues

The known issues are grouped as follows:

Installation and Upgrade

  • If you use View Client 4.6 or earlier to connect to a View 5.1 or later desktop, and the Use PCoIP Secure Gateway for PCoIP connections to desktop setting is enabled, View Connection Server must be View 5.0 or later. If the PCoIP Secure Gateway is configured on a security server, the security server also must be View 5.0 or later.
    Workaround: Upgrade View Connection Server and security server to View 5.1 or later, or disable the Use PCoIP Secure Gateway for PCoIP connections to desktop setting.
    Note: Upgrade View Connection Server and security server to View 5.1 or later before you upgrade View Agent or View Client components.
  • 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.

Configuration and View Administrator

  • The View PCoIP ADM (pcoip.adm) group policy setting, Configure SSL connections to satisfy Security Tools, is not supported in Horizon View 5.2. 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 Horizon View 5.2.
  • In View Administrator, if you enter a non-ASCII DNS server name in the network share path for a ThinApp repository, View fails to access the network path and does not add it as a ThinApp repository.
    Workaround: Create a DNS alias (CNAME) with ASCII characters to point to the server name. Use the CNAME in the network path.
  • An authentication error is displayed if a non-ASCII value for the external URL is entered when configuring a View Server in View Administrator.
    Workaround: Use only ASCII characters in the View Server External URL.

View Client and Remote Desktop Experience

  • Under certain conditions such as a heavy CPU load or network connections with high latency, the VMware Virtual Audio (DevTap) driver can experience a reduction in quality, ranging from distortion to audio drop-outs.
    Workaround: See KB 2045764: Audio issues with the VMware Virtual Audio (DevTap) driver running on a Horizon View desktop
  • USB redirection might not be supported on View desktops when users plug a USB device into a USB 3.0 port on the client.
    Workaround: Plug the USB device into a USB 2.0 port on the client.
  • When users play full-screen videos or 3D applications on View desktops in a vSphere 5.1 environment, freezes can occur, or the videos can stutter. Typically, the freezes last about one second.
    Workaround: Follow the instructions to modify the registry described in the Microsoft KB 235257, "Server Does Not Use All Bandwidth Available When Streaming Files with Bit Rates over 100 Kbps" at http://support.microsoft.com/kb/235257. You must restart the virtual machine to enable the modified registry setting to take effect.
    Note: Following this workaround delivers performance improvements in both ESXi 5.x and ESXi 5.1, but it is required for ESXi 5.1.
  • Applications that require 16-bit color depth on Windows 7 guest operating systems are not supported on virtual hardware version 7 or earlier.
    Workaround: Configure the application to use 32-bit color depth mode.
  • View 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.
  • If View Connection Server is configured to enable SSO (allow clients to save password credentials), some third-party Zero clients might fail to connect to View Connection Server.
    Workaround: Check with your third-party client vendor to make sure that you have the latest software and firmware updates that are compatible with enabling SSO (the client password-saving feature). Alternatively, you can disable the SSO global setting in View Administrator. See "Global Settings for Client Sessions" in the VMware Horizon View Administration document.
  • On Japanese systems with the following configuration there is a problem with Japanese proportional fonts in Internet Explorer 9 on a View desktop: The client system can be any number of supported platforms, such as iPad, Windows, zero client. The display protocol must be PCoIP, and the Windows7 3D rendering option must be enabled in View Administrator. This issue is fixed in vSphere 5 Update 1 or later.
  • 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 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.
  • Although you can use multiple monitors for View desktops that have Windows XP and Windows Vista operating systems, some monitor configurations have issues. You must configure the maximum display resolution correctly. For example, to have a 1200x1920 monitor stacked on top of a 1920x1200 monitor, you must configure the maximum resolution to accommodate this combined height. A resolution of 2560x1600 would be appropriate in this case. This issue does not occur with Windows 7 View desktops.
  • When the PCoIP group policy setting, "Disable sending CAD when users press Ctrl+Alt+Del," is enabled, the Send Ctrl+Alt+Del option in the Options menu in View Client does not work. This group policy setting is intended to disable sending CAD only when users press the Ctrl+Alt+Del keys in the View desktop, but it also disables sending CAD from the Options menu.
  • If you use PCoIP connections, audio input works with USB devices only.
  • When certain codecs are installed on the client system and MMR is enabled, View Client might crash when playing a video in Windows Media Player.
    Workaround: Uninstall the codec.
  • In Windows 7 desktops when connected using PCoIP in multiple-monitor display mode, if you choose Show On: Monitor Generic Non-PnP Monitor for any monitor other than the primary monitor in PowerPoint 2010, a black screen is displayed instead of a slide show.
    Workaround: If you are using PowerPoint 2010 in a Windows 7 desktop, you must use Show On: Primary Monitor for a slide show.
  • When connected to a Windows 7 64-bit View desktop from View Client for Mac OS X, audio does not work.
  • If you redirect a local USB drive to a desktop session, and disconnect or log out of the desktop session while writing data to the drive, an exFAT file system on the drive might be corrupted. You might see an error such as the following when you attempt to write to the USB drive: Error 0x80071AC3: The operation could not be completed because the volume is dirty. Please run chkdsk and try again.
    Workaround: Before you redirect a USB drive to a desktop session, back up the files on the USB drive to another local drive. If the file system on the USB drive does become corrupted, you can try to copy any valuable data from the USB drive to another local drive, although this operation might fail. Reformat the USB drive, and restore the data from the backup copy.
  • For some newer USB printers, if the color setting for the printer on the local machine is different from the color setting in the Virtual Printer settings for the View desktop, the local client settings take precedence. For example, if the client computer setting is to print in color but the Virtual Printer setting is to print gray-scale, the document is printed in color.
  • Multi-media redirection (MMR) does not play properly in a View Client PCoIP desktop when you connect a projector or external monitor to a laptop computer with certain ATI graphics cards. Sometimes it displays only a black box.
  • If you try to connect to an NLA-enabled Vista machine from an NLA-enabled Windows XP client, the connection fails with the error message An authentication error has occurred (Code: 0x80090303). Remote Computer: <IP.Address>. The same error occurs if you try to connect directly with RDP to the NLA-enabled Vista machine.
    Workaround: You can connect from Windows Vista clients.
  • If you are running View Client on Windows Vista build 6.0.6000, you might encounter the following problems:
    • It is not possible to add a printer in the Control Panel.
    • If you try to connect to a desktop using RDP, View Client hangs. The system log will include the error An internal communication error occurred. Redirected printing will no longer function for a single user session. Check the status of the Terminal Services Device Redirector in the System folder of Device Manager.
    Workaround: Upgrade your client system to Windows Vista SP1 or higher.
  • If View Client is started from the command line using a command such as wswc.exe -serverURL <IP.Address> -domainName <domain_name>, the user is prompted for a user name and password. If the user waits about 15 seconds and then clicks Cancel, the wswc.exe process remains running until another View Client is launched interactively or from the command line.
    Workaround: Manually stop the wswc.exe process.
  • View Client fails to connect to the View security server if a standard server FQDN with localized characters is specified during security server installation.
    Workaround: Specify the IP address of the standard server during security server installation.

Smart Card

  • On Windows 7 client machines, View Client exits when the smart card removal policy is triggered.
  • If users remove their smart cards while they are logged in, the View desktop exits as expected. However, on busy Windows Vista desktops, the following informational message might be delayed for one or two minutes: Your smart card was removed, so you have been logged out of the View Connection Server.

View Client with Local Mode and View Transfer Server

  • When you first log in to a checked out local desktop, the desktop might display the following error: There are currently no logon servers available to service the logon request. This issue is most likely to occur for a Windows Vista or Windows 7 guest operating system on a full virtual machine from a manual or automatic pool.
    Workaround: Below the error message on the guest desktop, click OK and log in manually. The error does not reoccur on subsequent logins.
  • Occasionally with Windows 7 View desktops that have Windows Aero enabled, if you are using a laptop as a client system and you close the laptop, when you later open the laptop, the local mode desktop stops responding. Suspending the client system causes the local mode desktop to freeze.
    Workaround: Resize the View Client window or minimize it and then restore it. The View desktop becomes locked and you can press Ctrl+Alt+Ins to log in again.
  • If you set an SSO timeout limit for View users in View Administrator, and a user checks out a desktop for use in local mode, a checkout operation that takes longer than the SSO timeout value causes the user's SSO credentials to expire.
    Workaround: Extend the SSO timeout limit in the SSO global setting in View Administrator. For details, see "SSO Timeout Limits and Local Mode Desktops" in the VMware Horizon View Administration document.
  • Do not reconfigure a powered off View Transfer Server using vSphere Client, for example to add memory. Reconfiguration will cause View Transfer Server's required SCSI controllers to be removed.
    Workaround: Make sure that View Transfer Server virtual machines do not require reconfiguration after they are put into use. If reconfiguration is required, remove and re-add the View Transfer Server from View Administrator. This will require a reboot.

View Persona Management

  • View Persona Management features such as folder redirection, offline file population during logon, background download, and replication of local profile files to the remote profile repository fail to function properly if the Windows Client-Side Caching system is in effect on the local system.
    Workaround: Synchronize the local Windows client-side cache of profile data and disable the Windows Offline Files feature. For instructions, see KB 2016416: View Persona Management features do not function when Windows Client-Side Caching is in effect.
  • 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.

vSphere Platform Support

  • When you provision a linked-clone pool in a vSphere 5.1 environment with View Storage Accelerator enabled, a portion of the pool may fail to be provisioned. The following error message is displayed: "Error during provisioning: Configuration failure: Cannot open the disk..." This issue is more likely to happen in environments in which a large number of virtual machines are deployed per host.
    Workaround: Disable View Storage Accelerator before provisioning.
  • Virtual machine disk space reclamation is disabled for Windows 8 desktops in a vSphere 5.1 environment.
    Workaround: None.
  • 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.
  • 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

  • In Horizon View 5.2, raising the Max concurrent View Composer maintenance operations and Max concurrent View Composer provisioning operations limits to much higher values than the defaults might increase the stress on the vCenter Server workload. This issue can occur because Horizon View performance and desktop pool scalability have increased significantly in Horizon View 5.2. See the VMware Horizon View Installation document for the current default values and related information.
    Workaround: Set the View Composer concurrent operations limits to the default values. If you raised these limits in an earlier release of Horizon View, revisit the values that you set previously and adjust them to the current default values.
  • When provisioning a large linked-clone pool in a vSphere environment with Distributed Resource Scheduler (DRS) enabled, the linked clones might be distributed unevenly across ESXi hosts in the cluster.
    Workaround: You can set the VMware DRS MinGoodness option to 0, as described in VMware KB article 1017291 at http://kb.vmware.com/kb/1017291. However, this solution does not work in every environment.
  • 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.
  • 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.
  • 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.
  • vSphere optimizes virtual machine cloning by using the SCSI data mover extended-copy feature. However, a side effect of this optimization is that linked clone pool provisioning can be slowed down by concurrent full cloning tasks.
    Workaround: Do not concurrently provision a linked clone pool and a large full clone pool if the two pools are on the same SCSI array, sharing the same data mover. Similarly, do not configure a linked clone pool to share a SCSI array with a full clone pool that uses the delete-desktop-after-logoff policy.
  • Linked clones that use BusLogic controllers might become unusable when recomposed to a base image that uses an LSI Logic controller. Linked clones affected by this issue are unable to boot their operating systems, and the administration interface shows errors such as: View Composer agent initialization state error (-1): Illegal state (waited 360 seconds). There is no workaround. Changing SCSI type during a recompose is not a supported operation.

Windows 8 Support

  • Reconnecting to a Windows 8 desktop session over PCoIP can take up to 24 seconds. While waiting to reconnect, the user sees a black screen and a mouse pointer. This issue only occurs when a user reconnects to an active desktop session. It does not occur when a user logs off and logs in again.
    Workaround: None
  • Adobe Flash optimization settings that use high quality and aggressive throttling are not fully enabled when end users use Internet Explorer 10 on Windows 8 desktops.
    Workaround: Use Internet Explorer 9 or earlier on Windows 8 desktops.
  • 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.
  • 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 Admnistrator.
  • When a user logs off of a Windows 8 desktop that was connected through RDP, the desktop might display the following error during the logoff: The connection to the remote computer failed. There was an unexpected RDP disconnection. Microsoft RDP error code = 1028 This issue does not occur on Windows 7 or Windows XP desktops or on desktops using PCoIP.
    Workaround: None.
  • 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 does not occur on Windows 7 or Windows XP, which show the correct user name from the Kerberos domain.
    Workaround: The user must unlock the desktop by selecting "Other user." Windows 8 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.

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 View Client or HTML Access.
    Workaround: 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.
    1. Remove any trusted certificates for the Metadata URL from the Trusted Root Certificate Authorities folder in the Windows certificate store.
    2. Remove the SAML Authenticator with the self-signed certificate.
    3. Add the trusted certificate for the Metadata URL to the Trusted Root Certificate Authorities folder in the Windows certificate store.
    4. Add the SAML Authenticator again.


  • On Windows 7, if you pin a View Connection Server or View Client desktop session in a jump list and reconnect to it with different connection settings, the item might appear under both Pinned and Recent servers in the jump list.
  • To ensure that non-English versions of virtual applications that are captured by ThinApp display the correct language user interface, during the ThinApp capture you must open the natively installed version on the capture machine before you start the post-scan operation.

Top of Page