How psexec.exe works?
I have an .EXE that I wrote using Wise Script Editor. This .EXE will do a few things to the machine and then run a vendor's .MSI install package. If this compiled .EXE is pushed to machines using psexec what happens to the spawned vendor .MSI when it runs? Does it too run in the same user context that psexec is using for the parent .EXE?
so if I run:
psexec \\mypcname -d -c -s MyCustomProgram.exe will everything MyCustomProgram.exe does run in the System Account? Or since it spawns an .MSI will that .MSI run in the Logged On Users account?
Thank you.
so if I run:
psexec \\mypcname -d -c -s MyCustomProgram.exe will everything MyCustomProgram.exe does run in the System Account? Or since it spawns an .MSI will that .MSI run in the Logged On Users account?
Thank you.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
It will run in System context unless you pass credentials on the command line with -u and -p arguments.
Posted by:
mhsl808
13 years ago
Great, thank you. now, aother question. It seems that the EULA is killing us when using psexec. We downloaded the newest version from Microsoft too. Here is what I am talking about.
I have written a Wise Script Editor .EXE. Inside of this I need to run a few .MSI files and I am running each one with psexec. My .EXE will do this.
explode Myfile1.msi; Myfile2.msi; Myfile3.msi; psexec.exe to the c:\temp folder
Then, from a command line I run c:\temp :> psexec.exe -s MyFile1.msi /qn etc...etc...
And since psexec has never been run it is throwing up the EULA and it hangs.
Is there a way around that? Or do I need to code it differently and NOT use a Wise Script?
I have written a Wise Script Editor .EXE. Inside of this I need to run a few .MSI files and I am running each one with psexec. My .EXE will do this.
explode Myfile1.msi; Myfile2.msi; Myfile3.msi; psexec.exe to the c:\temp folder
Then, from a command line I run c:\temp :> psexec.exe -s MyFile1.msi /qn etc...etc...
And since psexec has never been run it is throwing up the EULA and it hangs.
Is there a way around that? Or do I need to code it differently and NOT use a Wise Script?
Posted by:
anonymous_9363
13 years ago
Why are you copying PSEXEC.EXE when it's very raison d'etre is to remotely execute processes? Once you've run it on a master console and accepted the EULA, that's it. If all you want to do is run the MSIs, do that with MSIEXEC.EXE.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.