Author: jrmarquart
Subject: Psexec -i 0 Changed Behaviour in 2.1?
Posted: 18 March 2014 at 5:22pm
I'm not sure if this is a bug or feature change in Psexec, but I'm encountering the following behaviour/issue change between versions of Psexec:
In Psexec versions 1.96 and 1.98 using the following command works:
start "" /wait psexec.exe -n 5 -i 0 \\computername "\\computername\c$\Windows\Temp\remoteinstall\executable.exe"
This launches the executable on the computername and I can interact with it without issue. This appears to work regardless of what session ID I am currently in and still displays the GUI of the executable.exe using the Interactive Services Detection service.
In Psexec 2.1 this fails and simply loads a shell and then it stalls never completing (I'm assuming this is because of session ID 0). I can change it to the following and this will work (remove the session ID):
start "" /wait psexec.exe -n 5 -i \\computername "\\computername\c$\Windows\Temp\remoteinstall\executable.exe"
Or
(assumes session ID is 2 for this session)
start "" /wait psexec.exe -n 5 -i 2 \\computername "\\computername\c$\Windows\Temp\remoteinstall\executable.exe"
The problem is that I want to spawn this process as another user (which has admin rights to the computer) installing this software, so staff can install specific software only without being a local administrator on a computer. I simply start the UI0Detect service (Interactive Services Detection) and this loads it into the separate session ID 0 so the software can be installed (with the user staying logged into the current session). This no longer will work due to the change in behaviour/bug in Psexec 2.1 version?
Subject: Psexec -i 0 Changed Behaviour in 2.1?
Posted: 18 March 2014 at 5:22pm
I'm not sure if this is a bug or feature change in Psexec, but I'm encountering the following behaviour/issue change between versions of Psexec:
In Psexec versions 1.96 and 1.98 using the following command works:
start "" /wait psexec.exe -n 5 -i 0 \\computername "\\computername\c$\Windows\Temp\remoteinstall\executable.exe"
This launches the executable on the computername and I can interact with it without issue. This appears to work regardless of what session ID I am currently in and still displays the GUI of the executable.exe using the Interactive Services Detection service.
In Psexec 2.1 this fails and simply loads a shell and then it stalls never completing (I'm assuming this is because of session ID 0). I can change it to the following and this will work (remove the session ID):
start "" /wait psexec.exe -n 5 -i \\computername "\\computername\c$\Windows\Temp\remoteinstall\executable.exe"
Or
(assumes session ID is 2 for this session)
start "" /wait psexec.exe -n 5 -i 2 \\computername "\\computername\c$\Windows\Temp\remoteinstall\executable.exe"
The problem is that I want to spawn this process as another user (which has admin rights to the computer) installing this software, so staff can install specific software only without being a local administrator on a computer. I simply start the UI0Detect service (Interactive Services Detection) and this loads it into the separate session ID 0 so the software can be installed (with the user staying logged into the current session). This no longer will work due to the change in behaviour/bug in Psexec 2.1 version?