WSE 3.0 Silent push /Windows XP
Hey guys, I come here alot to check out the latest headlines and basically just to poke around, I signed up today because i am in need of a little help.
I am trying to rollout WSE 3.0 runtime and im getting the typical :
"msiexec exited on x.x.x.x with error code 1603."
Im using this : PSEXEC \\x.x.x.x msiexec /q /i c:\some_app.msi
I can install this locally, however, it needs to get installed on about 800 systems.
Anyone here have success with this package?
I am trying to rollout WSE 3.0 runtime and im getting the typical :
"msiexec exited on x.x.x.x with error code 1603."
I can install this locally, however, it needs to get installed on about 800 systems.
Anyone here have success with this package?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
bearden3
13 years ago
Im using this :PSEXEC \\x.x.x.x msiexec /q /i c:\some_app.msi
Just thinking out loud...
Hmmm, not sure about using an IP address... ;) You might have a syntax error. I use this in a batch file (as an example for you):
psexec \\machinename c:\windows\system32\msiexec.exe /unregister
This will use PSExec on the LOCAL machine to run the msiexec on the REMOTE machine (\\machinename) to unregister the WI Service. I also use the full path to the msiexec.
If your path has any white spaces in it you should put it in double quotes.
You could also add an MSI log file (/l*v c:\temp\some_app.msi) then look at the full paths to see what is causing the 1603.
You might have a permissions problem too.
Posted by:
scripteaze
13 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.