opksample.blogg.se

I have rebuilt and tested many variations and am out of ideas. The server is Win2016, and BES client 10.0.4

one variation was to create a batch to run the exe, and copy both the exe and batch to another folder on the C: drive… I can run the batch from interactive login and dos admin command window, but when bigfix executes it still gets the same ‘1603’ error.I have tried several variations but when from CLI no issue, and from Bigfix it always exits with a 1603 exit code. When i run the commands from the Admin dos window they run clean - but have 3-4 cmd windows popups flash by without need for input they disappear. Secure Boot can be enabled after a reboot, and check if the View Composer service is still running with Secure Boot enabled.I am having very similar issues trying to do a vm horizon agent update. This time, there should be no issue with the Composer installation. Go to Edit Settings -> VM Option -> Boot Option.If yes, disable the secure boot option in the VM. 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Īlso check the View Composer installation log to see if the following error is shown in the log:ĬustomAction InstallVstor2Driver.5ACA97E0_7C64_4970_A763_840E81DAAF0B returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) If you see a VMware Horizon 7.x View Composer installation failure with the error code 1603 when you install it on a Windows Server VM, you should check if an audit failure event is logged with the following message in the Windows Security log:Ĭode integrity determined that the image hash of a file is not valid.