Hello Claudio, > On 12/9/2011 2:29 PM, Claudio Ghirardi wrote: >> On 12/9/2011 1:47 PM, Falko Trojahn wrote: >>>>> I'd suggest to go to a target machine, run the psexec command locally >>>>> using cmd.exe instead of msiexec, and then within cmd.exe run msiexec >>>>> manually to get an idea what's wrong. >>>>> >> I don't understand what "run _psexec_ locally using _cmd.exe_ as >> parameter and then run msiexec from within cmd.exe." means. >> >> If i copy psexec to the target machine, add cmd.exe at some point in >> the original command line and then launch it from the target machine i >> receive a message "cmd.exe has started with ID number" as happened >> before with msiexec. > Maybe i understand what you're trying to say. > > - I went to the target machine > - I opened a dos prompt > - I went to the pstools directory (c:\pstools) > - I ran the command "psexec cmd.exe: another command prompt opened > - from that NEW commando prompt i ran the command: msiexec /i > "\\servername\wpkg\client\install\WPKG_Client_1.3.14-x64.msi" /qb > SETTINGSFILE="\\servername\wpkg\client\install\settings.xml" > - i received a pop-up windows saying: "The installation package could > not be opened. Verify that the package exists and that you can access it > or contact the application vendor to verify that this is a valid Windows > Installer package" with an "ok" button. > > That's weird: the normal command prompt can find the path to the msi but > the same command prompt invoked by psexec cannot? > I'm sorry if I wasn't clear enough. Now that you made this test we're getting closer. If the installation package cannot be opened: that means the user - perhaps the psexec-user "domain\useradmin" or whatever you supplied for "-u" switch on command line - has no/not enough rights to read/execute the WPKG_Client_1.3.14-x64.msi package. Or it has no access to the "wpkg" share or one of the subdirectories. Next (within the above mentioned cmd prompt from "psexec -u [domain\useradmin] ... cmd.exe") I'd try to map the wpkg share by: net use x: \\servername\wpkg If you get a prompt for username/passwort then the share is not accessible. If drive x: is present after that, try to descend into the x:\client\install\ directory and start WPKG_Client_1.3.14-x64.msi from there. Good luck, Falko |