![]() My gut guess is the exe is goosed, expecting user input or isn't passing on the arguments supplied to it (I assume you've tried runmsi.exe /? from a command line, just in case it gives you extra info). ![]() that would be the next thing to check is happening. So you MAY find that your /quiet and /norestart flags are passed on and work fine. Often when they do they pass the command arguments to the to invoked MSI. Psexec \\travel1 -u "universal\administrator" -p "password" -c -f "runmsi.exe" /quiet /norestartĮXE's can wrap MSI's. Might be easier if you have the file locally and use the second method. First attempts to run the file off the UNC, the second copies it from the UNC to the remote machine then runs it. Psexec \\travel1 -u "universal\administrator" -p "password" -c -f "\\filesrv\Networkdata\vpn setup\runmsi.exe" /quiet /norestartįor ease of escaping and quotes I'd consider running on an UNC path without the spaces. Psexec \\travel1 -u "universal\administrator" -p "password" "\\filesrv\Networkdata\vpn setup\runmsi.exe" /quiet /norestart ![]() So does it work at all in any circumstances, such as when you launch it on the desktop manually?Īssuming NO user input is asked for, that the exe wrapper passes on command line arguments to the invoked msiexec and that everything is correct with the file then as others have mentioned given it's an exe shouldn't you run it directly? >that gives me an error code 1620, and I know because it is not an msi file, but if I try that just as an exe it just hangs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |