Top 20

Top 20 Horizon View articles for October 2016

Top 20

Here is our Top 20 Horizon View articles list for October 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.


  1. Virtual machine application runs slower than expected in ESXi
  2. Restart order of the View environment to clear ADLDS (ADAM) synchronization in Horizon View
  3. The View virtual machine is not accessible and the View Administration console shows the virtual machine status as Already Used
  4. Generating a Horizon View SSL certificate request using the Microsoft Management Console (MMC) Certificates snap-in
  5. Removing a standard (replica) connection server or a security server from a cluster of connection/security servers
  6. Using Microsoft Certreq to generate signed SSL certificates in VMware Horizon View
  7. Linked Clone pool creation and recomposition fails with VMware Horizon View 6.1.x and older releases
  8. Finding and removing unused replica virtual machines in the VMware Horizon View
  9. Installation order of End User Computing Agents for User Environment Manager (UEM) and App Volumes
  10. Troubleshooting SSL certificate issues in VMware Horizon View 5.1 and later
  11. Unable to save pool settings or create new pools in VMware View
  12. Manually deleting replica virtual machines in VMware Horizon View 5.x
  13. Disabling the HotAdd/HotPlug capability in ESXi 5.x and ESXi/ESX 4.x virtual machines
  14. Changing the log file behavior in the VMware View components
  15. Confirming that the userinit string is configured properly
  16. Determining which replica disk is used for a linked clone virtual machine
  17. Setting up an IPsec tunnel between a security server and a VMware View Connection Server instance
  18. Troubleshooting Persona Management
  19. View Manager Admin console displays the error: Error during provisioning: Unexpected VC fault from View Composer (Unknown)
  20. Creating a large number of Linked Clones in a single vApp fails with the error: Unable to access file xxx.vmdk since it is locked


Leave a Reply

Your email address will not be published.