Share this post

Link to post

Share on other sites

AdamUL 52

Are you compiling it as a x86 or x64 bit? If you are compiling it as x86, and trying to run it with PsExec on a remote x64 system, it will not run due to PsExec copying the file to admin$/temp. This directory is actually C:\windows\system32\temp on the remote system, which is for x64 executable only. To get around this, compile as x64 or copy the file to another directory with AutoIt and use PsExec to execute from there without the -c option.

Share this post

Link to post

Share on other sites

NeuroToxic 0

Are you compiling it as a x86 or x64 bit? If you are compiling it as x86, and trying to run it with PsExec on a remote x64 system, it will not run due to PsExec copying the file to admin$/temp. This directory is actually C:\windows\system32\temp on the remote system, which is for x64 executable only. To get around this, compile as x64 or copy the file to another directory with AutoIt and use PsExec to execute from there without the -c option.

Adam

If the script is compiled in x64, its works, but I would like one script for both architecture, its possible ?

Share this post

Link to post

Share on other sites

Jeff987 0

Thanks for putting this together. I have been messing around with run(psexec...) with quotes spaces, x86 or x64, admin, interactive, etc blah blah blah for an eternity, and learning alot, but overcoming all these hurtles is like extremely time consuming.

also capturing any stdin stderr as well is frustrating.

Thanks guys for this wonderful package, I'm extremely thankful to you for your efforts here!!!!!