PSExec 2.4: option -i does not start process in console session

Question

PSExec says the following about option -i: "If no session is specified the process runs in the console session."

This used to work way back in version 2.11, but with recent releases the process is started in the services session (ID 0). Is there any fix or work-around? I need to run PSExec from a batch file and cannot determine the session ID manually.

Answer 1

I have 2.2 and 2.4 and can recreate the behaviour.

You could run quser and parse the output to get the session id.

C:\Temp\test>psexec \\test10  -u admin -p admin quser.exe  
  
PsExec v2.4 - Execute processes remotely  
Copyright (C) 2001-2022 Mark Russinovich  
Sysinternals - www.sysinternals.com  
  
  
 USERNAME              SESSIONNAME        ID  STATE   IDLE TIME  LOGON TIME  
 admin                                     1  Disc            1  10/11/2022 7:54 AM  
 testuser              console             2  Active      none   10/18/2022 2:23 PM  
quser.exe exited on test10 with error code 0.