siegfried_hello
It looks exactly like that Siegfried.
If I try to run a process on a remote pc that DOES NOT require elevation, with psexec 2.20, I work as before (see my post of 20 Jan) but omit the -h parameter (note the -h is gone now as I don't want demoprogram.exe run elevated).
psexec \\RemoteSystem -u user -p password c:\demoprogram.exe
But with 2.32, if I try that as before:
psexec \\RemoteSystem -u user -p password c:\demoprogram.exe
Again I get a login failure and again I have to use the -i parameter with version 2.32. 😞
psexec \\RemoteSystem -i -u user -p password c:\demoprogram.exe
So in a nutshell it looks like -i is almost always required now in 2.32, and this tends to beg the question why it's an option any more (if it's always required!) instead of silently active in 2.32 to avoid back compatibility problems!!!! Perhaps a question for lukekim and the SysInternals developers?