psexec, is not interactive in win7
Hi,
Is now more than 3 days I'm trying to run remotely with psexec in interactive mode iexplore on a windows 7 X64 enterprise edition from an xp32 pro edition
When I install the win7 last week I try with this command:
psexec -u user -P password -i 1 -d \\my-ip C:\progra~1\intern~1\iexpl
HKLM\Software\Microsoft\Wi
After this change it was running perfectly !
Today i try again with the same parameter then is not interactive anymore, I means the process PID is generated in the task manager for the current user however is not showing anything on screen.
The only changes was MS update
Please help
Is now more than 3 days I'm trying to run remotely with psexec in interactive mode iexplore on a windows 7 X64 enterprise edition from an xp32 pro edition
When I install the win7 last week I try with this command:
psexec -u user -P password -i 1 -d \\my-ip C:\progra~1\intern~1\iexpl
HKLM\Software\Microsoft\Wi
After this change it was running perfectly !
Today i try again with the same parameter then is not interactive anymore, I means the process PID is generated in the task manager for the current user however is not showing anything on screen.
The only changes was MS update
Please help
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I found the solution, the problem was located in the "-i" parmatter need to be folowed by the sesssion number.
To solve my issue I create a VBS with :
for i=0 to 20 and "i" i is used like this :
for vi=0 to 20
Return = WshShell.Run("psexec -u "&vUser&" -P "&vpassWord&" -i "& Vi &" -d \\"&IP&" "&chr(34) & vBrowserPath & chr(34) &" "& vlink,0,true)
if Return = 2 then WScript.Quit
next
To solve my issue I create a VBS with :
for i=0 to 20 and "i" i is used like this :
for vi=0 to 20
Return = WshShell.Run("psexec -u "&vUser&" -P "&vpassWord&" -i "& Vi &" -d \\"&IP&" "&chr(34) & vBrowserPath & chr(34) &" "& vlink,0,true)
if Return = 2 then WScript.Quit
next
Glad youre fixed....
http://blogs.msdn.com/b/patricka/archive/2010/04/27/what-is-interactive-services-detection-and-why-is-it-blinking-at-me.aspx
http://forum.sysinternals.com/psexec-windows-7_topic19020.html
WINDOWS 7 - Run Explorer in SYSTEM account on Windows Vista or 7 using Sysinternal’s psexec tool?
http://efreedom.com/Question/3-172437/Run-Explorer-SYSTEM-Account-Windows-Vista-Using-Sysinternals-Psexec-Tool
Its the Session0 isolation thats new to Windows 7. Least thats what it looks like, not sure why that reg mod made it work..... Did the update by any chance alter that value?