I am having very similar issues trying to do a vm horizon agent update.
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.
I have tried several variations but when from CLI no issue, and from Bigfix it always exits with a 1603 exit code.
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.
The server is Win2016, and BES client 10.0.4
I have rebuilt and tested many variations and am out of ideas.
The most basic action is: (same exit code with ‘waithidden’)
I’m going to take it on faith that all your command-line options are correct, because you said it works manually in a command prompt window and I don’t have a Horizon client to validate them.
It could be a problem parsing the quoted command lines; I think I’ve had similar problems before, so I fall back on the cmd.exe parser handling quotes. Try
I will push it back to the app team to validate with Vmware the silent install options and that it can really be run from 'SYSTEM" and not have to be a real user.
User context is the only other thing i can think of, as some examples have user/pw in the installer options but i was not provided any.