![]() ![]() 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. Thanks for reading and hopefully this helps someone else out.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. Verify Composer service is still running. Once Guest OS successfully rebooted check the composer service is running. Power Down the Virtual Machine that has the guest OS of Windows Server 2016 you’re trying to install composer on.Tested Virtual Machine Version 13 and 14.I then created a desktop pool and was able to use linked clones successfully! After rebooting, I turned Secure Boot back on and the composer service was still running. After a successful install, I looked at the “vstor2-ufa.sys” and dug into the digital signature which was signed by “VMware Inc” and was issued by “verisign” which is already trusted. After disabling Secure Boot, I was able to successfully install Composer 7.5. Right away I either knew it was one of two things: Secure boot or VBS (Virtual Based Security). The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.įile Name:\Device\HarddiskVolume4\Program Files (x86)\Common Files\VMware\VMware Universal File Access\vstor2-ufa.sys" “Code integrity determined that the image hash of a file is not valid. I noticed a weird audit failure in security log which was Event ID “5038” and had the following description: So I decided to check the event viewer one more time. Looking through the logs, I found no errors for ODBC or SSLbind settings. I started verifying the SSLbind and ODBC Connection. So after finding this entry, I started looking at VMware Doc’s and KB articles. “CustomAction InstallVstor2Driver.5ACA97E0_7C64_4970_A763_840E81DAAF0B returned actual error code 1603 ” After doing some digging, I found this in the log: So I started digging into the event viewer and vmmsi.log which is located at (c:\users%username%\Appdata\Local\Temp) I started to notice 1603 setup exit code errors. I would run into the composer installer failing and attempting “Roll Back Action”. When I went to install Composer 7.5 (This also happened with 7.4) on a composer standalone configuration. Recently I have been testing moving Horizon View to Server 2016 since we will be migrating soon from 2012R2 to 2016 in production sometime this year. So why is VMware Horizon View Composer Failing to Install ? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |