Is There A Way To Shut Down A Specific Program Running On Another PC?

Topic

New Reply

Hi,

I have a big house and I’m partially disabled so it’s kinda hard to get around. I have a few programs that are loaded on a ‘server’ (actually running Windows 7) but which can only safely be run by one machine at a time (they use a database that is not ‘shareable’). So, naturally, I’ll be in one room and want to use a program and find that it won’t run because I left it running on =another= computer at the other end of the property.

Is there a way to be sitting at PC ‘A’ (running Windows 7) and shut down a program that is running on PC ‘B’?

Note that I don’t mean -reboot- PC ‘B’, I mean, just ‘cancel the process which is running on PC ‘B”.

On Windows Server, I know I used to be able to do this via Remote Desktop—you could go into Terminal Services and actually ‘see’ every process running on the server -and- on any remote clients. But that’s not what I got. It’s kinda what I want, though.

TIA,

—JC

Reply | Quote

Replies

If these PC are all on one home network I would think you could use something like TeamViewer, set up for unattended access so its very much just like remote desktop, access the remote PC just as if you were sitting in front of it and perform any operation you wish. TeamViewer is free for home (non-commercial) use.

I use it all the time for just the opposite reason; to start long, cpu-intensive operations on remote computers without having to visit each one in person.

Reply | Quote

If you enable Remote Desktop, you could do the same:

Turn on Remote Desktop in Windows 7

Using Remote Desktop Connection In Windows 7

Configure Remote Desktop Access on Windows 7 Systems

Bruce

Reply | Quote

Use PSKill from Sysinternals.

Reply | Quote

Interesting. I guess I -could- do that. I figured that would make the ‘controllee’ PC run slow as molasses. I guess I could give it a shot. Thanks.

Any other suggestions? I know there used to be applications that could ‘broadcast’ what processes were going via IP.

—JC

Reply | Quote

There’s no reason why using PSKill would slow down the source machine.

In addition to PSKill you could take a look at PSInfo also from Sysinternals. In fact it might be easier to download the Sysinternals Suite and take a look at the utilities such as PSList, PSInfo, PSkill, PSExec etc.

Reply | Quote

Yes, no reason, and even TeamViewer or Remote Desktop do not slow down either the server or client machine to any appreciable degree, though the connection feedback usually has a noticeable delay. I wouldn’t be using them if they did.

Reply | Quote