You can view Horizon Client logs for troubleshooting. You cannot connect to a server directly through Horizon Client, or your remote desktop and published application entitlements are not visible in Horizon Client. Connecting to a Server in Workspace ONE Mode.Horizon Client quits even if you do not close it. What to Do If Horizon Client Quits Unexpectedly.When you type in a remote desktop or published application, none of the keystrokes seem to work. If repairing Horizon Client does not solve the problem, you might need to uninstall and reinstall Horizon Client. Sometimes you can resolve problems with Horizon Client by repairing Horizon Client. You might need to reset a remote desktop if the desktop operating system stops responding and restarting the remote desktop does not solve the problem. Reset Remote Desktops or Published Applications.The remote desktop operating system usually prompts you to save any unsaved data before it restarts.
#Vmware horizon client loading failed windows#
Restarting a remote desktop is similar to using the Windows operating system restart command. If the remote desktop operating system stops responding, you might need to restart a remote desktop.
So with that here are some takeaways from this after doing some extensive reading. This time after the VMs had passed their customizing stage and I was then presented with the “Available” status as normal. 12 Identifying the Problem Domain View Client Network View Manager View Composer vCenter Server Compute.
#Vmware horizon client loading failed install#
Thinking that perhaps the upgrade from 6.1.1 to 7.3.1 had affected something I decided to completely uninstall the agent, reboot and install 7.3.1 again from fresh then recompose the VMs in desktop pools from the new snapshot. vCenter is reporting an error My desktop is slow 12. Verifying that everything within the environment was how it should be I then turned my attention back to the Horizon agent on the gold master VM template. In my case PCoIP was being used and all required ports between the guest VM agent and Horizon Connection servers were opened. On doing a bit of research it appears this error can be generated if the firewall ports for a particular display protocol aren’t opened between the Horizon guest VM agent and Horizon Connection servers – in the case of Horizon this can be the Remote Desktop Protocol or PCoIP (PC over Internet Protocol) depending on how you have configured your desktops. Recently I went through the process of upgrading a VMware Horizon 6.1.1 VDI environment to 7.3.1 which was just released, and apart from some small teething issues with licensing during the upgrade due to a slight oversight in the VMware documentation everything else appeared to go smoothly.Īs this environment uses View Composer Linked-Clones for non-persistent desktop pools part of the upgrade involves installing the new Horizon 7.3.1 agent onto the gold master VM template for each desktop pool then performing a recompose of the VMs in those pools.This is where I ran into an issue.Īfter upgrading the agent and performing a recompose operation on the VMs within each desktop pool they then displayed a Protocol failure” status within Horizon Administrator although I could still login to them as normal through the Horizon Client.