![]() ![]() Uninstall the previous version of the Horizon Agent first if upgrading to a newer version.Check for a “ghosted” network adapter on the gold master template VM and remove it – more info can be found here.Verify the Horizon Agent services are running on the guest VMs – a list of these can be found here.Verify the required TCP ports are opened on the guest VMs with the Horizon Agent installed – a list of these can be found here.If you have VMs displaying a “Protocol failure” status within Horizon Administrator do one or more of the following 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. 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. ![]() 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. Steps to manually remove the hcmon. Workaround 3: Manually remove the hcmon.sys driver from your server. Workaround 2: Right click on the installer setup file for vSphere Client and click on ' Run as administrator '. I searched and found the downloadable for 5.2 and tried that and it was immediately successful, so I have it working under V5.2.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. NET Framework 3.5.1 Service Pack 1 is installed. This service may not function properly'.įurther to this problem I noticed my old laptop was running V5.2 the newest version which was failing was 8.1. However, the system is configured to not allow interactive services. 'The VMware Horizon Client service is marked as an interactive service. I therefore went through a 'repair' of this software and lo and behold the VMUSBARBService loaded successfully, but the install STILL FAILED this time with a different error on the eventviewer this time: I found a different error on the EventViewer and I found a threat that suggested problem might be with Vision C++. The installation file is called 'VmWAre-Horizon-Client-2012-8.1.0-17349995.exe'įurther to the above the problem has moved on. Any ideas why this happens or how I might work around it? I've tried running as Admin and tried turning off A/V protection but no joy. I updated Windows 10 to the may update (1909 to 2004) I am trying to install VMWare Horizon client and it keeps on crashing and sending me a message Installation failed. T10:41:44.814Z| USBDeviceInstUtil-build-17308015| I0: VMUSBArbService service not running ' from regedit Reboot the client machine. Delete the VMware VDM folder under 'ComputerHKEYLOCALMACHINESOFTWAREVMware, Inc. T10:41:44.814Z| USBDeviceInstUtil-build-17308015| E1: Inst_QueryServiceRunningStatus: Service could not be opened: ERROR_SERVICE_DOES_NOT_EXIST Clear the following path C:Program Files(X86)VMware (client folder) delete the old Horizon client folder after the un-installation. T10:41:44.814Z| USBDeviceInstUtil-build-17308015| I2: Inst_QueryServiceRunningStatus: Attempting to query service: VMUSBArbService T10:41:44.814Z| USBDeviceInstUtil-build-17308015| I0: - VMStopUSBArbSvc(): Stopping USB arbitrator service I've had no problems in the past, but on the new laptop the Install fails with : Existing user of Horizon Client, but have bought a new Windows 10 laptop so need to install a copy of VMWare Horizon Client on it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |