Vmware Horizon 4.7 Download

Posted on 10.02.2020 by admin

Vmware Horizon 4.7 Download 3,6/5 2265 reviews

Vmware Horizon Client 4.7 Msi Download
Vmware Horizon 4.7 Download For Laptop
Vmware Horizon 4.7 Download For Pc

Customers who have purchased VMware Horizon can download their relevant installation package from the product download tab below. VMware Desktop Clients - Windows, and Mac Visit the Horizon Clients download page to get your clients. I have a old version in my desktop. Today I can not log in. It said 'SSL error'. I thought this software may need to be updated. Then I download latest version 4.7. Because it found I have old version. Then installation ui show 'Agree &upgrade'. After a while, installation stopped on 'repairing VMware-Horizon-Client' about 10 minute.

Have you guys ran into this issue.

Here is what I have so far.

The client gets to the very end and then rolls back. I disabled Symantec Anti-Virus and installed as administrator still no luck. I tried installing in Safe mode but it didn't even get halfway before it failed. Here is what I have done so far. I removed all files and folders in C:ProgramDataVMware. C:Program FilesVMware. C:usersusernameappdateroamingvmware. C; usersusernamelocalvmware. I also went into the registry and deleted any entry that had VMware on it. I am at a loss. One machine is Windows 7 and the one in my office is Windows 10.

I found out when it gets to HTML 5 Multimedia redirection the installation rolls back. I went back and did customized install (unchecking HTML 5 multimedia redirection) then it installs OK.

HTML 5 multimedia installs by default and I would like to have this option installed.

Any help would be greatly appreciated.

Released 4 January 2018

Last Updated: 14 February 2018

These release notes include the following topics:

What's New in This Release

VMware Horizon 7 version 7.4 provides the following new features and enhancements. This information is grouped by installable component.

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

Horizon Connection Server

Cloud Pod Architecture
- The Cloud Pod Architecture feature now supports one-way Active Directory trust domains. Horizon administrators can implement one-way trust topologies in a Cloud Pod Architecture environment, and end-users can select and launch remote desktops and published applications across the trust.
- Users can now launch remote desktops and applications on a later version pod when connected to an earlier version pod in a Cloud Pod Architecture environment.
- You can enable the Session Collaboration feature for global desktop entitlements.
Published Desktops and Application Pools
- You can use NVIDIA GRID vGPU for 3-D rendering when you create an instant-clone farm.
- The 'Empty session timeout (applications only)' option provides a new “immediate” timeout value in the farm settings to log off the session when the last application window is closed.

Horizon Agent for Linux

Instant-Clone Floating Desktop Pool
You can create a Linux-based instant-clone floating desktop pool with Horizon 7 Agent for Linux. This feature is supported only on Ubuntu 14.04 and 16.04 systems.
Active Directory Integration with PBISO
Linux-based desktops are allowed to authenticate with Active Directory using PowerBroker Identity Services Open (PBISO). This feature is supported only on Ubuntu 14.04 and 16.04 systems.
3Dconnexion Mouse
The 3Dconnexion mouse support is available in Horizon 7 Agent for Linux using USB redirection.
Additional platform
SUSE Linux Enterprise Server 12 SP3 and SUSE Linux Enterprise Desktop 12 SP3 are supported.

Horizon Agent

Session Collaboration
With the Session Collaboration feature, users can invite other users to join an existing remote desktop session.
Fingerprint Scanner Redirection by Using the Device Bridge BAS Plugin
You can redirect biometric devices, specifically fingerprint scanners, that are plugged into a serial port on a Windows client system to virtual desktops, published desktops, and published applications by using the device bridge feature. You can install the Device Bridge BAS Plugin by selecting the Device Bridge BAS Plugin custom setup option in the Horizon Agent installer.
Secure boot enabled machines supported with URL Content Redirection
URL content can now be redirected from machines that have secure boot enabled.
URL Content Redirection with Chrome
URL content can now be redirected in the Chrome browser. Both agent-to-client and client-to-agent redirection are supported. To use this feature, the VMware Horizon URL Content Redirection Helper extension must be installed and enabled in Chrome.

Horizon GPO Bundle

Configure Session Collaboration group policy setting
Use the Collaboration group policy setting in the VMware View Agent Configuration ADMX template file (vdm_agent.admx) to configure Session Collaboration on remote desktops.
Device Bridge BAS Plugin group policy setting
Use the Disable Device Bridge BAS Plugin group policy setting in the VMware View Agent Configuration ADMX template file (vdm_agent.admx) to disable the Device Bridge BAS Plugin.
Server clipboard memory size group policy settings for VMware Blast and PCoIP
Use the Clipboard memory size on server group policy setting for VMware Blast sessions, and the Configure clipboard memory size on server for PCoIP sessions, to specify the server's memory size value for clipboard redirection in bytes or kilobytes. The VMware Blast setting is in the VMware Blast ADMX template file (vdm_blast.admx). The PCoIP setting is in the PCoIP ADMX template file (pcoip.admx).
H264 High Color Accuracy
The VMware Blast setting in the VMware Blast ADMX template file (vdm_blast.admx) increases color accuracy when using H.264 encoding by using the YUV 4:4:4 colorspace instead of 4:2:0.

Horizon Client

For information about new features in Horizon Client 4.7, including HTML Access, see the Horizon Clients Documentation page.

Before You Begin

Important note about installing VMware View Composer
If you plan to install or upgrade to View Composer 7.2 or later, you must upgrade the Microsoft .NET framework to version 4.6.1. Otherwise, the installation will fail.
Important note about installing VMware Tools
If you plan to install a version of VMware Tools downloaded from VMware Product Downloads, rather than the default version provided with vSphere, make sure that the VMware Tools version is supported. To determine which VMware Tools versions are supported, go to the VMware Product Interoperability Matrix, select the solution VMware Horizon View and the version, then select VMware Tools (downloadable only).
If you want to install View Composer silently, see the VMware Knowledge Base (KB) article 2148204, Microsoft Windows Installer Command-Line Options for Horizon Composer.
This Horizon 7 release includes new configuration requirements that differ from some earlier releases. See the View Upgrades document for upgrade instructions.
If you intend to upgrade a pre-6.2 installation of Horizon 7, and the Connection Server, security server, or View Composer server uses the self-signed certificate that was installed by default, you must remove the existing self-signed certificate before you perform the upgrade. Connections might not work if the existing self-signed certificates remain in place. During an upgrade, the installer does not replace any existing certificate. Removing the old self-signed certificate ensures that a new certificate is installed. The self-signed certificate in this release has a longer RSA key (2048 bits instead of 1024) and a stronger signature (SHA-256 with RSA instead of SHA-1 with RSA) than in pre-6.2 releases. Note that self-signed certificates are insecure and should be replaced by CA-signed certificates as soon as possible, and that SHA-1 certificates are no longer considered secure and should be replaced by SHA-2 certificates.
Do not remove CA-signed certificates that were installed for production use, as recommended by VMware. CA-signed certificates will continue to work after you upgrade to this release.
To take advantage of Horizon 7 features such as Virtual SAN 6.1, GRID vGPU, and Virtual Volumes, install vSphere 6.0 and subsequent patch releases.
When you upgrade to this release, upgrade all Connection Server instances in a pod before you begin upgrading Horizon Agent, as described in the View Upgrades document.
After you have performed a fresh install or upgraded all Connection Server instances to Horizon 7 version 7.2 or later, you cannot downgrade the Connection Server instances to a version earlier than Horizon 7 version 7.2 because the keys used to protect LDAP data have changed. To keep the possibility of downgrading Connection Server instances while planning an upgrade to Horizon 7 version 7.2 or later, you must perform an LDAP backup before starting the upgrade. If you need to downgrade the Connection Server instances, you must downgrade all Connection Server instances and then apply the LDAP backup to the last Connection Server that is downgraded.
The product build number for Horizon Agent in this release does not appear under the 'Version' column in the 'Add/Remove Programs' panel. To get the product build number, click 'VMware Horizon Agent' and view the comments section in the panel below.
The download page in this release includes a Horizon 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 document.
Selecting the Scanner Redirection setup option with Horizon 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 Horizon Agent.) For users who need the Scanner Redirection feature, configure a separate desktop pool and select the setup option only in that pool.
Horizon 7 uses only TLSv1.1 and TLSv1.2. In FIPS mode, it uses only TLSv1.2. You might not be able to connect to vSphere unless you apply vSphere patches. For information about re-enabling TLSv1.0, see Enable TLSv1 on vCenter Connections from Connection Server and Enable TLSv1 on vCenter and ESXi Connections from View Composer in the View Upgrade document.
FIPS mode is not supported on releases earlier than 6.2. If you enable FIPS mode in Windows and upgrade Horizon Composer or Horizon Agent from a release earlier than Horizon View 6.2 to Horizon 7 version 7.2 or later, the FIPS mode option is not shown. You must do a fresh install instead to install Horizon 7 version 7.2 or later in FIPS mode.
Linux desktops use port 22443 for the VMware Blast display protocol.
Starting with Horizon 7 version 7.2, it is possible that the ordering of cipher suites can be enforced by Connection Server. For more information, see the View Security document.
Starting with Horizon 7 version 7.2, Connection Server must be able to communicate on port 32111 with other Connection Servers in the same pod. If this traffic is blocked during installation or upgrade, installation will not succeed.
Starting with Horizon 7 version 7.3.2, TLS handshakes on port 443 must complete within 10 seconds, or within 100 seconds if smart card authentication is enabled. In previous releases of Horizon 7, TLS handshakes on port 443 were allowed 100 seconds to complete in all situations. You can adjust the time for TLS handshakes on port 443 by setting the configuration property handshakeLifetime. Optionally, the client that is responsible for an over-running TLS handshake can be automatically added to a blacklist. New connections from blacklisted clients are delayed for a configurable period before being processed so that connections from other clients take priority. You can enable this feature by setting the configuration property secureHandshakeDelay. For more information about setting configuration properties, see the View Security document.

Internationalization

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

Compatibility Notes

For the supported guest operating systems for Horizon Agent on single-user machines and RDS hosts, see VMware Knowledge Base (KB) article 2150295, Supported Windows Versions for Remote Desktop Systems for Horizon Agent.
If you use Horizon 7 servers with a version of View Agent older than 6.2, you will need to enable TLSv1.0 for PCoIP connections. View Agent versions that are older than 6.2 support the security protocol TLSv1.0 only for PCoIP. Horizon 7 servers, including connection servers and security servers, have TLSv1.0 disabled by default. You can enable TLSv1.0 for PCoIP connections on these servers by following the instructions in VMware Knowledge Base (KB) article 2130798, Configure security protocols for PCoIP for Horizon 6 version 6.2 and later, and Horizon Client 3.5 and later.
For the supported Linux guest operating systems for Horizon Agent, see System Requirements for Horizon 7 for Linux in the Setting Up Horizon 7 for Linux Desktops document.
For the supported operating systems for Connection Server, security server, and View Composer, see System Requirements for Server Components in the View Installation document.
Horizon 7 functionality is enhanced by an updated set of Horizon Clients provided with this release. For example, Horizon Client 4.0 or later is required for VMware Blast Extreme connections. See the VMware Horizon Clients Documentation page for information about supported Horizon Clients.
The instant clones feature requires vSphere 6.0 Update 1 or later.
Windows 7 and Windows 10 are supported for instant clones, but not Windows 8 or Windows 8.1.
See the VMware Product Interoperability Matrix for information about the compatibility of Horizon 7 with current and previous versions of vSphere.
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 Horizon Administrator, see the View Installation document.
RC4, SSLv3, and TLSv1.0 are disabled by default in Horizon 7 components, in accordance with RFC 7465, 'Prohibiting RC4 Cipher Suites,' RFC 7568, 'Deprecating Secure Sockets Layer Version 3.0,' PCI-DSS 3.1, 'Payment Card Industry (PCI) Data Security Standard', and SP800-52r1, 'Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations.' If you need to re-enable RC4, SSLv3, or TLSv1.0 on a Connection Server, security server, View Composer, or Horizon Agent machine, see Older Protocols and Ciphers 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 using Client Drive Redirection (CDR), deploy Horizon Client 3.5 or later and View Agent 6.2 or later to ensure that CDR data is sent over an encrypted virtual channel from an external client device to the PCoIP security server and from the security server to the remote desktop. If you deploy earlier versions of Horizon Client or Horizon Agent, external connections to the PCoIP security server are encrypted, but within the corporate network, the data is sent from the security server to the remote desktop without encryption. 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 Configuring Remote Desktop Features in Horizon 7 document.
The USB Redirection setup option in the Horizon 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 Horizon 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.
Before you set the level of Transparent Page Sharing (TPS) in Horizon Administrator, VMware recommends that the security implications be understood. For guidance, see the VMware Knowledge Base (KB) article 2080735, Security considerations and disallowing inter-Virtual Machine Transparent Page Sharing.
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 7 does not support vSphere Flash Read Cache (formerly known as vFlash).
In Horizon (with View) version 6.0 and later releases, the View PowerCLI cmdlets Get-TerminalServer, Add-TerminalServerPool, and Update-TerminalServerPool have been deprecated.
Screen DMA is disabled by default in virtual machines that are created in vSphere 6.0 and later. View requires screen DMA to be enabled. If screen DMA is disabled, users see a black screen when they connect to the remote desktop. When Horizon 7 provisions a desktop pool, it automatically enables screen DMA for all vCenter Server-managed virtual machines in the pool. However, if Horizon Agent is installed in a virtual machine in unmanaged mode (VDM_VC_MANAGED_AGENT=0), screen DMA is not enabled. For information about manually enabling screen DMA, see VMware Knowledge Base (KB) article 2144475, Manually enabling screen DMA in a virtual machine.
vGPU enabled instant clone desktop pools are supported for vSphere 2016 and later.
Microsoft Windows Server requires a dynamic range of ports to be open between all Connection Servers in the Horizon 7 environment. These ports are required by Microsoft Windows for the normal operation of Remote Procedure Call (RPC) and Active Directory replication. For more information about the dynamic range of ports, see the Microsoft Windows Server documentation.
In Horizon 7 version 7.2 or later, the viewDBChk tool will not have access to vCenter or View Composer credentials and will prompt for this information when needed.
The forwarding rules for HTTP requests received by Connection Server instances and security servers have changed at this release. If you have defined custom frontMapping entries in locked.properties, you should remove them before upgrading. If you wish to disallow administrator connections to certain Connection Server instances, then instead of defining custom frontMapping entries, add this entry to locked.properties:
frontServiceWhitelist = tunnel ajp:broker ajp:portal ajp:misc moved:* file:docroot
On security servers, this entry is applied automatically and does not need to be set in locked.properties.
Horizon Persona Management is not compatible with User Writable Volumes created with the UIA + Profile template.

Supported Windows 10 Operating Systems

For an updated list of supported Windows 10 operating systems, see VMware Knowledge Base (KB) article 2149393, Supported Versions of Windows 10 on Horizon 7.
For more information on upgrade requirements for Windows 10 operating systems, see VMware Knowledge Base (KB) article 2148176, Upgrade Requirements for Windows 10 Operating Systems here.

Prior Releases of Horizon 7

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

Resolved Issues

When different major Horizon versions are installed on the pods in a Cloud Pod Architecture environment, users cannot launch remote desktops and applications on a later version pod when connected to an earlier version pod. For example, if pod A is running Horizon 6 version 6.x and pod B is running Horizon 7 version 7.x, users cannot launch desktops and applications on pod B when they connect through pod A. Magnetic field simulation software free trial.
The HTML5 Multimedia Redirection feature cannot redirect websites that use restricted Content Security Policy (CSP), such as Facebook and Twitter.
The HTML5 Multimedia Redirection feature cannot redirect HTML5 multimedia content from http://www.independent.co.uk/us and http://www.dailymotion.com/us.
When creating a pool or a farm, if you select No for the option 'Allow users to chose protocol' then a pool or application can only be launched via the default protocol selected. The PCOIP protocol disallows any connections via HTML access and in the case of VGPU enabled pools, the 'Allow users to chose protocol' option was disabled, so an administrator could not change it back to Yes. This change has been reverted.
Applications included in a global application entitlement are not listed in the Open with.. menu in Horizon Client.
Attempts to create or update pools or global entitlements fail with the NoSuchAttributeException error.
For more information, see VMware Knowledge Base (KB) article 52077, Creating or updating pools or global entitlements fails with error 'NoSuchAttributeException'.
The disable option is grayed out in the Admin UI for an Instant Clone Pool or Linked Clone Pool if the option for default protocol is set to RDP and 'User can't choose Protocol' is selected. This problem has been resolved.
In an Horizon 7 environment configured with Persona Management, the favorite links deleted from Internet Explorer before first replication is invoked still appear in the remote profile after log off and log in.
An Horizon 7 environment configured with Persona Management causes a delay in log off and user settings saved after a delayed log off do not appear after log in.
An error message appears while connecting to a desktop pool with the RDP display protocol in a domain with a one-way trust when the AllowDirectRDP setting is disabled.
It takes 5 minutes to launch a powered off linked-clone desktop when the power policy is set to 'Power Off' in the desktop pool settings.
Trace logging for instant-clone logs is not enabled even though Connection Server has the trace level set for Connection Server logs.
The True-SSO dashboard displays a red status for the Certificate Authority but does not display the reason why Horizon 7 cannot connect to the Certificate Authority when it does not support the required template.
After an upgrade to Horizon 7 version 7.2, the VM name reuse functionality with naming pattern configuration does not work, which causes provisioning issues. This issue was resolved in Horizon 7 version 7.3.2.
A published desktop launches with a black screen after you install Horizon Agent with the 3D RDSH custom option on a Windows Server 2016 RDS host.
When launching RDSH desktops with PCOIP, PSG becomes unresponsive after a number of iterations, causing desktop connections to fail. Horizon Administrator reports the event with the following message: Unable to launch from Pool [Pool Name] for user [User Name]: There were no machines available that reported protocol [Protocol Name] as ready.

Known Issues

The known issues are grouped as follows.

Horizon Persona Management Vmware Horizon 4.7 Download

Horizon 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 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, Persona Management no longer works for that user.
Workaround: See VMware Knowledge Base (KB) article 2058932, Granting domain administrators access to redirected folders for View Persona Management.
Persona Management is not supported on session-based desktop pools that run on RDS hosts.
Workaround: Install Persona Management in automated or manual desktop pools that run on single-user machines.
After every login, Persona Management takes a long time to replicate the first user persona on a guest operating system that uses the 'v6' version of the user profile.
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 you log in to a Windows 10 LTSB machine using a persona profile and try to access redirected folders from Quick Access, such as Downloads or My Documents, you get this error:
C:Usersvdiuser7Downloads is unavailable. Microsoft doesn't provide the API to add folder or file to Quick Access.
Workaround: None
When you log into a VM configured with Persona Management for the second time, the Microsoft Edge browser crashes and an error message that states the OneDrive application has never been used appears. Additionally, the files and folders cannot be replicated properly. This happens only with Windows 10 build 1709 November 2017 update.
Workaround: Disable the Persona Management setting Roam Local Settings Folders. When you disable this setting, the Microsoft Edge browser works properly but the OneDrive application is only available when you log in for the first time.
Offline icons are not displayed for files on a Windows Server 2012 virtual machine with Horizon Persona Management setting enabled.
Workaround: None known.

View Composer

When Horizon Administrator provisions a linked-clone pool with thousands of desktops, a few machines (one or two per thousand) might fail with a 'Customization timed out' error. If automatic recovery is enabled (the recommended setting for production environments), machines in error are automatically recreated and provisioned. No workaround is required.
Workaround: If automatic recovery is disabled, manually delete the machines in error in Horizon Administrator. Horizon Administrator will provision new machines as part of normal pool management.
When deleting a large desktop pool, a number of folders containing a .hlog file and an empty sub folder named.sdd.sf might remain undeleted.
Workaround: Manually delete the folders that are left behind after a deletion operation. For instructions, see the Solution in VMware Knowledge Base (KB) article 2108928, Rebalance operation leaves VM folders in previous data stores.
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 clone scannot 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.
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.
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.
When you run View Composer installer on Windows Server 2016 with the latest Windows update from command line, you get a Microsoft
.NET 4.6 framework error. This issue occurs because the CLI installer is not able to recognize latest version of Microsoft .NET 4.7.
Workaround: Use the View Composer installer user interface to run the installer.
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 data stores for the OS disk and the user data disk and the data store 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 data store or by not changing the data store selections before a View Composer rebalance operation.
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.
When you attach or recreate a View Composer persistent disk stored on a Virtual SAN data store, 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.
When a space reclamation operation is run for Windows 8.x 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.
Creating or recomposing desktop pools fails after you upgrade the parent virtual machine from build 1511 to build 1607 of the Windows 10 operating system. Build 1607 is the Windows 10 Anniversary Update operating system.
Workaround:
- Option 1. Perform a fresh installation of Windows 10 Build 1607 on the parent virtual machine.
- Option 2. Do not select 'Redirect disposable files'in the desktop pool creation wizard.
After a recompose, refresh, or rebalance operation with a persistent disk, Windows 10 desktops might fail to start, or become untiled from the Start menu. Windows applications can include applications such as Windows Store, native applications, Edge Browser, and Cortana Search. This issue affects multiple version of Windows 10 intermittently, depending on applications used. This problem affects the following desktop types:
- Linked-clone dedicated desktops with a persistent disk where the persistent disk is used to store app settings.
- Linked-clone floating desktops with Persona Management enabled that use a persistent disk as a local disk and the Persona Management setting Roam Local Settings Folders enabled.
- This issue is not seen with floating or dedicated linked-clone desktop pools where the user profile is redirected to network share with or without Persona Management enabled. If Persona Management is enabled, the user profile is set to roam with VMware Persona GPO settings.
- This issue is not seen when persistent disk and/or Persona Management are used to persist only My Documents and Exchange 365 .pst/ost files.
Virtual SAN data stores 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 data store to another Virtual SAN data store in a different cluster is not supported.
In an environment where a large virtual desktop pool (for example, 2,000 desktops) is created on Virtual Volumes data stores that reside on a NetApp storage system running ON TAP 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.
Provisioning of virtual machines based on View Composer desktop pools or instant clone desktop pools configured to use NVIDIA GRID vGPU fails with the following error: The amount of graphics resource available in the parent resource pool is insufficient for the operation.
Workaround: Use a single vGPU profile for all virtual desktops configured for 3D rendering in a cluster.
If multiple vGPU profiles are required, design the multiple cluster topologies such that each cluster only has virtual machines with the same profile.
To resolve the error messages in Horizon 7, you must delete the failed desktop pool. Decide which vGPU profile you want to use for each cluster, then delete the pool that does not have the correct vGPU profile from the cluster, and create the pool for that vGPU profile again in the correct cluster.
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'MicrosoftWindowsAppxDeploymentClientPre-staged appcleanup'
The rebalance operation from a vSAN datastore to a non-vSAN datastore with VMFS6 file system fails in the vSAN cluster.
Workaround: None.
Connection to View Composer fails when you run the following command: viewdbchk.cmd –findMachine
Workaround: Import the self-signed certificate for View Composer into Connection Server's keystore or use a custom CA certificate.

Horizon Connection Server

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.
During provisioning of an instant-clone desktop pool, if there is not enough space available on the data stores, the error message that is displayed in Horizon Administrator is 'Cloning of VM <VM name> has failed -VC_FAULT_FATAL: Failed to extend swap file from 0 KB to 2097152 KB.' This message does not clearly indicate the root cause of the problem.
Workaround: Not required.
In Horizon Administrator, if you go to Catalog> Desktop Pools, double-click an instant-clone desktop pool, go to the Inventory tab and click Machines (Instant Clone Details), the window displays details of the instant clones. However, the OS Disk data store column displays no information.
Workaround: None
In a large scale environment, some of the desktops in an instant-clone desktop pool might go into the Invalid IP state.
Workaround: In Horizon Administrator, go to Pool Inventory, select the desktops in the Invalid IP state and click Recover.
When you restart a virtual machine for which an end user session exists in a desktop pool from vCenter Server, the virtual machine restarts but the status of the virtual machine might appear in the “Already Used” state in Horizon Administrator.
This problem can occur for the following pool types:
- Instant-clone desktop pools.
- Linked-clone floating desktop pools with 'Delete on log Off' enabled.
- Linked-clone floating desktop pools with 'Refresh on log Off' enabled.
- Full-clone floating desktop pools with 'Delete on log Off' enabled.
Workaround: Use Horizon Administrator or Horizon Client to restart the virtual machine in the desktop pool. If the virtual machine is already in the “Already Used”state, remove the virtual machine. This action automatically creates a new virtual machine based on the pool provisioning settings.
Instant-clone desktop pool creation fails when the OU or sub-OU name contains the special character 'ß'.
Workaround: Remove 'ß' in the OU or sub-OU name when you create instant clones.
If you provision instant clones on local datastores, the corresponding hosts cannot be put into maintenance mode. This occurs because the internal VMs and the instant clones are stored on local datastores so they cannot be migrated.
Workaround: Delete the instant-clone desktop pool. This will delete the related VMs and enable the corresponding hosts to enter maintenance mode.
ESXi host remediation that uses VUM fails if the instant-clone Parent VM is present on the host in a powered-on state
Workaround: For more information,see the VMware Knowledge Base (KB) article 2144808, Entering and exiting maintenance mode for an ESXi host that has Horizon instant clones.
For this release, Windows Universal apps are not supported as hosted remote applications. For example, Universal apps do not appear in the list of apps provided by a Windows Server 2016 RDS farm. Universal apps, such as the Edge browser or the Calculator included with Windows 10 or a Windows Server 2016 RDS host, are built on the Universal Windows Platform (UWP).Universal apps require Windows Explorer to be run. In addition, manually launching Universal apps through the Command Prompt will show an error message.
If you deploy an automated farm from a Windows Server 2012 parent virtual machine that has the RDS role enabled, Sysprep customization will fail on the deployed linked-clone virtual machines. This 3rd-party issue does not occur on other Windows Server versions that have the RDS role enabled.
Workaround: On the Windows Server 2012 parent virtual machine, apply the Microsoft hotfix available at https://support.microsoft.com/en-us/kb/3020396.
For True SSO, the connectivity status between the Connection Server instance and the enrollment server is displayed only on the System Health Status dashboard for the connection server that you are using to access Horizon Administrator. For example, if you are using https://server1.example.com/admin for Horizon Administrator, the connectivity status to the enrollment server is collected only for the server1.example.comconnection server. You might see one or both of the following messages:
- The primary enrollment server cannot be contacted to manage sessions on this connection server.
- The secondary enrollment server cannot be contacted to manage sessions on this connection server.
It is mandatory to configure one enrollment server as primary. Configuring a secondary enrollment server is optional. If you have only one enrollment server, you will see only the first message (on error). If you have both a primary and a secondary enrollment server and both have connectivity issues, you will see both messages.
When you set up True SSO in an environment with CAs and SubCAs with different templates setup on each of them, you are allowed to configure True SSO with a combination of template from a CA or SubCA with another CA or SubCA. As a result, the dashboard might display the status of True SSO as green. However, it fails when you try to use True SSO.
When using Horizon 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.
If you change the Blast Secure Gateway (absg.log) log level on a Connection Server instance from Infoto Debug, the log level remains Info. (You change the log level by opening the Set View Connection Server Log Levels on a 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.
On rare occasions, the system health status of Event Database maybe displayed as red on the Horizon 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.
Workaround: None.
When you use F5 or the Refresh button to refresh Horizon Help Desk Tool, sometimes the Horizon Help Desk Tool icon disappears and you get a STRING_ID issue on the Web page.
Workaround: Logout and login to Horizon Help Desk Tool.
When you click the Help Desk icon from Horizon Administrator, single sign-on to Horizon Help Desk Tool fails. This can occur because your UPN does not exist in Active Directory.
Workaround: Use your user name and password to login to Horizon Help Desk Tool.
In Horizon Help Desk Tool, the pod name does not appear if the session is a local session or a session running in the local pod.
Workaround: Set up the Cloud Pod Architecture environment to view pod names in Horizon Help Desk Tool.
Login fails if you use a case insensitive user name to login to Horizon Help Desk Tool.
Workaround: Login to Horizon Help Desk Tool with a case sensitive user name.
The Workspace ONE mode setting does not get reflected in the replica server from Workspace ONE.
Workaround: Configure the Workspace ONE mode in Connection Server.
If NVIDIA drivers are installed on a virtual machine that you use as a parent or template to deploy a desktop pool, and the machines are deployed on non-NVIDIA GRID hardware on the ESXi hosts,users might not be able to start desktop sessions correctly.This issue might occur if the virtual machine was used previously in an NVIDIA GRID vGPU deployment.
Workaround: Remove the NVIDIA drivers from the virtual machine before you take a snapshot or make a template and deploy the desktop pool.
When you create full-clone desktop pools, sometimes wrong templates are displayed and valid templates are hidden due to a cache issue.
Workaround: Restart Connection Server.
When you use the vdmutil command to create a URL content redirection setting, you must name the setting url-filtering. If the setting name is not url-filtering, there will be no redirection. For example:
vdmutil --createURLSetting --urlSettingName url-filtering --urlScheme http --entitledApplication iexplore2012 --agentURLPattern 'http://google.*' --urlRedirectionScopeLOCAL --authAs johndoe --authDomain mydomain --authPasswordsecret
VMware does not recommend creating more than one URL content redirection setting in this release.
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 Horizon 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 Horizon Administrator (Pool Settings page) and not through vSphere Client.
Workaround: Either upgrade the hardware version of the virtual machines in vSphere Client, or use Horizon Administrator to set the proper value for video memory based on the current virtual machine hardware version.
When you try to add a SAML authenticator in Horizon Administrator, the Add button is disabled on the Manage SAML Authenticators page.
Workaround: Log in to Horizon Administrator as a user who has the Administrators or Local Administrators role.
The ViewDbChk utility can display an 'Archiving persistent disks..' message while removing machines from an automated linked-clone pool with floating assignment or an automated farm.
Workaround: None.
Cloud Pod Architecture configuration changes made by another Horizon administrator while you are logged in to Horizon Administrator are not visible in your current Horizon Administrator session.
Workaround: Log out of Horizon Administrator and log in again to see the changes.
In a Cloud Pod Architecture environment, pre-launched application sessions from global application entitlements are not shown in Inventory > Search Sessions in Horizon Administrator.
Workaround: Log in to the Horizon Administrator user interface for a Connection Server instance in the hosting pod and select Monitoring > Events to view pre-launched session information.
Users that are assigned to 20 to 50 Cloud Pod Architecture global application entitlements have a 20 to 30 second delay while being authenticated to Horizon 7 when connecting through any version of Horizon Client.
Note: In Horizon 7 version 7.2, this connection time is slightly improved.
Workaround: None.
When using Internet Explorer 10 or 11 on a Windows 8 or later computer, if you set the browser locale to Traditional Chinese, and you log in to Horizon Administrator, the navigation panel might be displayed in Simplified Chinese.
Workaround: Use an alternate browser to log in to Horizon Administrator.
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.
For Intel vDGA, only the Haswell and Broadwell series of Intel integrated GPUs are supported. Broadwell integrated GPUs are supported only on vSphere 6 Update 1b and later. Haswell integrated GPUs are supported on vSphere 5.5 and later. The GPU must be enabled in the BIOS before it can be recognized by ESXi. For more information, see the documentation for your specific ESXi host. Intel recommends leaving the graphics memory settings in the BIOS set to their default values. If you choose to change the settings, keep the aperture setting at its default (256M).
View Storage Accelerator might take tens of minutes to generate or regenerate the digest files for large virtual disks (for example, a 100 GB 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.
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.
In a hybrid vSAN environment, about three percent of the virtual machines might not use View Storage Accelerator. These machines will take few seconds longer to start up.
Workaround: Delete and recreate the virtual machines that failed to use View Storage Accelerator.
In this release, View Storage Accelerator is not supported on Virtual Volume datastores.
Workaround: None
An instant-clone desktop pool configured to use NVIDIA GRID vGPU fails to launch instant-clone virtual desktops or instant-clone virtual desktops with black screen and never recovers with the PCoIP or Blast display protocol using non h264 hardware encode. Non h264 hardware encode is uncommon for Blast. An example of non h264 hardware encode is any NVIDIA GPU profile that limits frame buffer to 512MB and has Windows 10 as the remote desktop operating version.
Workaround: Use the VMware Blast display protocol with h264 hardware encode to launch the instant-clone virtual desktops in the desktop pool configured with NVIDIA GRID vGPU.
For vCenter Server 6.0 U3 or later, including vCenter Server 6.5, internal parent VMs migrate to another host during failure. This migration causes an issue because unnecessary parent VMs reside on the destination host.
Workaround: Manually remove these parent VMs. For more information, see the Setting Up Virtual Desktops in Horizon 7 document.
To reduce the possibility of memory exhaustion, vGPU profiles with 512 MB or less of frame buffer support only one virtual display head on a Windows 10 guest operating system.
The following vGPU profiles have 512 Mbytes or less of frame buffer:
- Tesla M6-0B, M6-0Q
- Tesla M10-0B, M10-0Q
- Tesla M60-0B, M60-0Q
- GRID K100, K120Q
- GRID K200, K220Q
Workaround: Use a profile that supports more than one virtual display head and has at least one GB of frame buffer.
Published desktops and application pools fail to launch if they have the client restriction feature enabled and are entitled to a domain that is configured with a one-way AD trust.
Workaround: None
After an upgrade, the option to add a farm is grayed out if you have a role with the 'Manage Farms and Desktops and Application Pools' (object-specific privilege).
Workaround: Edit the role or create the role again with the 'Manage Farms and Desktops and Application Pools' privilege, which also adds the “Manage Global Configuration and Policies” privilege.
After an upgrade, the bookmarks do not appear in Workspace ONE.
Workaround: Add the bookmarks from the catalog in Workspace ONE again.
Searching for users in one-way or two-way trusted domains does not provide any search results if you use the Single Sign-On link to access Horizon Help Desk Tool.
Workaround: To search for users in one-way or two-way trusted domains, log in with the user name and password to the Horizon Help Desk Tool.
After you disconnect and reconnect the network cable and click 'Disconnect and Log Off' on the client machine, the remote desktop does not disconnect and log off.
Workaround: Manually close the window of the remote desktop and disconnect from the remote session.
An error dialog window appears in Horizon Administrator when you cancel the Add vCenter Server operation and then add the same vCenter server again. When you click OK in the error dialog, close the Add vCenter Server wizard and invoke the wizard again to add the same vCenter server and click Next, an error message for identifying the validity of the server appears.
Workaround: Click OK in the error dialog that appears for identifying the validity of the server, click Next, and follow the prompts in the wizard to add the same vCenter server again.
With the FIPS mode enabled, a pod that just joined a pod federation appears as having a status of red and offline when viewed from the Horizon Administrator dashboard of the first initialized pod in the same Cloud Pod Architecture environment.
Workaround: None.
When a desktop pool is assigned multiple VLANs, Horizon Agent VMs on desktops that could get assigned to a VLAN different from the parent VM, don’t get a valid IP address.
Workaround: Disconnect and reconnect the NIC of the Horizon Agent VM.
When you create linked clones and full clones with the Sysprep customization method, customization and domain joining sometimes fails on Windows 10 guest operating systems.
Workaround: This occurs because of a Microsoft Windows issue. To resolve this issue, follow the steps in the Microsoft Knowledge Base (KB) article: https://support.microsoft.com/en-us/help/2769827.
After upgrading from vCenter Server, the instant clone virtual machine provisioning operation fails with the error: 'The operation is not allowed in the current state. ForkParentNotEnabledOnSource'
Workaround: Use the steps in the VMware Knowledge Base (KB) article https://ikb.vmware.com/s/article/52573.

Horizon Agent for Linux

This section describes issues that might occur with Horizon Agent for Linux or when you configure a Linux desktop.

When you configure a Linux virtual desktop for multi-monitor support with a maximum 2560x1600 screen resolution, the submenu dialog boxes do not open.
If you configure two monitors with different resolutions, and the resolution of the primary screen is lower than that of the secondary screen, you might not be able to move the mouse or drag application windows to certain areas of the screen.
Workaround: Make sure that the primary monitor's resolution is at least as large as the secondary monitor's.
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.
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.
The Linux agent's keyboard layout and locale do not synchronize with the client if the Keyboard Input Method System is set to fcitx.
Workaround: Set the Keyboard Input Method System to iBus.
Single Sign On (SSO) does not work well on a RHEL/CentOS 7.2 desktop when you add a domain using System Security Services Daemon (SSSD).
Workaround: After you add a domain using SSSD, modify the /etc/pam.d/password-auth file using the information in the VMware Knowledge Base article 2150330 SSO configuration changes required when using SSSD to join AD on RHEL/CentOS 7.2 Desktops.
The following issues occur with the Horizon Agent for Linux installer when FIPS mode is selected:
- If the FIPS mode is selected during an interactive installation process, there are some instances when the warning dialog about the FIPS validation status is not displayed and the administrator is unable to confirm whether to proceed with the installation. This occurs when the EULA confirmation is bypassed.
- If the FIPS mode is specified to be installed on a platform other than RHEL, the FIPS mode installation fails silently. The feature does not get installed and no error message is displayed.
Workaround: None known.
The single sign-on (SSO) feature does not work when you try to connect to a remote desktop that has Horizon for Linux installed with the FIPS feature enabled.
Workaround: Manually log in to your Active Directory (AD) user account.

Horizon Agent

The USB HUB device driver might not be installed properly when you install Horizon Agent on a desktop in a manual desktop pool. This issue can occur if, during the Horizon Agent installation, you restart the system before the USB HUB device driver is fully installed.
Workaround: When you install Horizon 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 Horizon 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 Horizon 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:ProgramFilesVMwareVMware ViewAgentbindrivers and click Next to let Windows install the driver.
To upgrade a desktop from Windows 8 to Windows 8.1, you must uninstall Horizon Agent, upgrade the operating system from Windows 8 to Windows 8.1, and then reinstall Horizon Agent. Alternatively, you can perform a fresh installation of Windows 8.1 and then install Horizon Agent.
When you run the Horizon 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 Horizon Agent. See Microsoft KB article 2836988.
When you run any Horizon 7 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.
When you uninstall Horizon 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 Horizon Agent. As a best practice, ensure that all RDS sessions are logged off before you uninstall Horizon Agent.
In FIPS mode, Horizon Agent fails to pair with Connection Server and the pool status is not available when Horizon Agent is installed to a drive other than the C drive.
Workaround: When operating in the FIPS mode, install Horizon Agent on the C drive.
A warning message about applications in use appears when you uninstall Horizon Agent on Windows Server 2016.
Workaround: Click “Ignore” in the dialog box that appears when you use Windows Add or Remove Programs to uninstall Horizon Agent. If you uninstall Horizon Agent from the command line, use the command msiexec /x /qn {GUID of Agent} instead of the command msiexec /x {GUID of Agent}.
When you uninstall the Horizon Agent, the mouse speed becomes slow and jerky. Uninstalling Horizon Agent also uninstalls the vmkbd.sys driver.
Workaround: Repair VMware Tools on the Horizon Agent virtual machine.
When upgrading from Horizon Agent 7.1 to Horizon Agent 7.2 on a Windows 7 guest operating system, a 'Files in Use' dialog appears. The dialog states that the VMware Horizon Agent application is using files that need to be updated by the setup.
Workaround: Click 'Ignore' to proceed with the upgrade.
Horizon Agent cannot install the virtual printing feature on RDS hosts that are physical machines. Virtual printing is supported on RDS desktops when Horizon Agent is installed on RDS hosts that are virtual machines.
Workaround: Configure RDS hosts on virtual machines and install Horizon Agent.
The virtual printing feature is supported only when you install it from Horizon Agent. It is not supported if you install it with VMware Tools.
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.
Selecting the Scanner Redirection setup option with Horizon Agent installation can significantly affect the host consolidation ratio. By default, the Scanner Redirection option is not selected when you install Horizon Agent.
Workaround: Make sure that the Scanner Redirection setup option is not selected for most users. For users who need the Scanner Redirection feature, configure a separate desktop pool and select the setup option only in that pool.
When you uninstall Horizon Agent 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 Horizon Agent.
Client drive redirection does not work with Horizon Agent installed on a 32-bit Windows 10 operating system.
Workaround: None. This is a Microsoft Windows Server issue.
Windows 10 32-bit Horizon Agent installation throws 'the arguments are invalid' exception and the installation continues after you click OK. This error occurs because the print spooler service is disabled.
Workaround: Enable the print spooler service for the installation to work as expected.
If you install Horizon Agent on a Windows 10 or Windows Server 2016 operating system, and the scaling is not set to 100%, you cannot drag and drop applications from the primary monitor in a multi-monitor setup to another monitor. This issue can occur because of incorrect cursor input.
Workaround: Set the Horizon Agent DPI setting to 100% scaling.
With the Session Collaboration feature, if a session owner grants control to a collaborator, and the collaborator experiences connection loss and network recovery while the session owner is attempting to regain control of the session, both the session owner and collaborator might have input control of the session at the same time.
Workaround: Disconnect and reconnect the collaborative session, or toggle the input check box in the Session Collaboration user interface.
When you set a timeout value for HKLMSoftwareVMware, Inc.VMware VDMAgentUSBUemTimeouts, it fails to take effect.
Workaround: Reboot the Agent VM.
The HTML5 Multimedia Redirection feature cannot redirect HTML multimedia content from http://huffingtonpost.com. The HTML5 Multimedia Redirection feature can redirect HTML5 multimedia content from http://www.yahoo.com, but you might see a 'Page Unresponsive' message.
Workaround: None.
If you set URL Content Redirection rules to .*.acme.com, all URLs that include acme.com are redirected, but the URLs .acme.com and acme.com are not redirected.
Workaround: To redirect the URLs acme.com and .acme.com, set the URL Content Redirection rule to acme.com, not .*.acme.com.
If a session owner is watching a video that has been accelerated using MMR during a collaboration session, the collaborators see a black screen instead of the video.
Workaround: As a session owner, if you need to play a video during a collaboration session, do not use Windows Media Player or Internet Explorer to play the video, or disable MMR on pools where collaboration is enabled.
If a collaborator joins a multimonitor session and enables relative mouse mode on their client, it is possible for the mouse to move to a secondary monitor that the collaborator cannot see.
Workaround: Move the mouse back on to the screen. Alternatively, don't use relative mouse mode in a multimonitor session.
If you use Chrome with URL Content Redirection, and you set '.*.google.*' for the https protocol in filtering rules and you set Google as your home page in Chrome, redirection to google.com occurs each time you open a new tab.
Workaround: Change the home page or the filtering rules.
When setting up a session collaboration, adding a collaborator by the email address from a two-way trusted domain fails.
Workaround: Add the collaborator using domainuser.

Vmware Horizon Client 4.7 Msi Download

Horizon GPO Bundle

Computer-based global policy objects (GPOs) that require a reboot to take effect are not applied on instant clones.
Workaround: See the VMware Knowledge Base (KB) article, 2150495.
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. Do not set the TCP or UDP port value to 4172. Resetting this value to 4172 will adversely affect PCoIP performance in RDS sessions.
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 Horizon Agent has no effect. The remote desktop language always synchronizes with the language used on the client system.
Workaround: None.
A GSSAPI_ERROR message appears when you initially login with username and password and try to recursively unlock using smart card authentication to login to a local machine that has the group policy setting 'Unlock remote sessions when the client machine is unlocked' enabled, and then Log In As Current User from Horizon Client.
Workaround: Disable Log In As Current User from Horizon Client and manually unlock the virtual desktop using the username and password.
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 baud rate used by each device.
Workaround: None.
In a nested mode configuration where the first-level desktop (the machine where Horizon Client and Horizon Agent are installed) is a virtual desktop and the second-level desktop is a published desktop, the “Specify a filter in redirecting client printers” group policy setting does not affect the second-level desktop if you configure it in the first-level virtual desktop.
Workaround: If you want to filter printers for the second-level desktop, configure the “Specify a filter in redirecting client printers” group policy in the second-level desktop.