Author: chief
Subject: PsExec and Windows 2000 /7
Posted: 23 July 2014 at 12:14pm
Hello,
I have a Windows 2000 computer peer-to-peer with a Windows 7 Pro computer. I am trying to run an executable on the Windows 7 computer (graphical interface) from the Windows 2000 computer using the following in a Windows 2000 CMD window: psexec \\teradyne -i c:\hold\responder.exe. The first time this is executed a message appears on the Windows 7 computer stating: "A program running on this computer is trying to display a message". If the "View this message" option is selected the program interface appears as expected. Once the application is closed the CMD window on the Windows 2000 computer shows a return value of 0 from psexec. If the same is entered again: "psexec \\teradyne -i c:\hold\responder.exe" psexec responds with "Error communicating with PsExec service on teradyne: The pipe has ended.". At this point the only way to get it to work again is by rebooting both computers.
The version of PsExec being used is 1.71. I downloaded version 2.11 and attempted the same procedure as described above (after rebooting both computers) and the first time the Windows CMD window entered: "psexec \\teradyne -i c:\hold\responder.exe" psexec responded with: "Error deriving session type: Provider type not defined".
Is there any way to remote-execute a graphical-user-interface application on the Windows 7 computer via PsExec on the Windows 2000 computer?
Subject: PsExec and Windows 2000 /7
Posted: 23 July 2014 at 12:14pm
Hello,
I have a Windows 2000 computer peer-to-peer with a Windows 7 Pro computer. I am trying to run an executable on the Windows 7 computer (graphical interface) from the Windows 2000 computer using the following in a Windows 2000 CMD window: psexec \\teradyne -i c:\hold\responder.exe. The first time this is executed a message appears on the Windows 7 computer stating: "A program running on this computer is trying to display a message". If the "View this message" option is selected the program interface appears as expected. Once the application is closed the CMD window on the Windows 2000 computer shows a return value of 0 from psexec. If the same is entered again: "psexec \\teradyne -i c:\hold\responder.exe" psexec responds with "Error communicating with PsExec service on teradyne: The pipe has ended.". At this point the only way to get it to work again is by rebooting both computers.
The version of PsExec being used is 1.71. I downloaded version 2.11 and attempted the same procedure as described above (after rebooting both computers) and the first time the Windows CMD window entered: "psexec \\teradyne -i c:\hold\responder.exe" psexec responded with: "Error deriving session type: Provider type not defined".
Is there any way to remote-execute a graphical-user-interface application on the Windows 7 computer via PsExec on the Windows 2000 computer?