I have been using psexec 1.94, now I am using psexec 2.34 an dalso seeing psexec64 . what has changed in the new psexec version and also what is psexec64. I am using win10 and win2016 machines. Should I change to psexec64?
Psexec 1.94 Download
I have been using psexec 1.94, now I am using psexec 2.34 an dalso seeing psexec64 . what has changed in the new psexec version and also what is psexec64. I am using win10 and win2016 machines. Should I change to psexec64?
Psexec 1.94 Download
Recently in our IT department we've noticed each others user accounts under documents and settings. Which is strange because we've never logged into each others machines. There were a few times I'd run psexec in order to apply BIOS/system settings, but never a full login. Also there hasn't been anyone else who has done any psexec/scripting that would connect to anyone else's machines(except for running management tools against the remote machine, like compmgmt.msc)
As a member of the domain admin's group, I dont explicitly authenticate each time I connect to a machine, but a profile is created for me anyway. The -e argument stops this from happening (and significantly speeds up the psexec session!).
I'm using psexec version 1.94 and I'm certain that the machinename, user, and password are correct. Does anyone know if there are known issues with psexec on Windows Server 2003 and whether or not there is a fix?
caa09b180b