How to kill a remote process running on PC A from PC B or share ap

  • Thread starter Thread starter Enrique
  • Start date Start date
E

Enrique

Hi Folks,
I have PC A and B in the same UserGroup with full w/r access. When I don't
shut down a specific app running on PC A, and then try to launch it from PC
B it gives me an error. Basically the reources from PC A are tying it up.
I've played with the Sharing/Security paramaters on the specific file, but
all those "w/r privledges" doesn't allow the app to be shared. How do I work
around this? I've tried all these adjustments as an Administrator and also PC
A logon user.

THanks in advance!
ee
 
My reply is at the bottom of your sent message.

In
Hi Folks,
I have PC A and B in the same UserGroup with full w/r access. When I don't
shut down a specific app running on PC A, and then try to launch it from
PC
B it gives me an error. Basically the reources from PC A are tying it up.
I've played with the Sharing/Security paramaters on the specific file, but
all those "w/r privledges" doesn't allow the app to be shared. How do I
work
around this? I've tried all these adjustments as an Administrator and also
PC
A logon user.

THanks in advance!
ee
Click to expand...

Remote Desktop maybe?

RealVNC maybe?

--
Galen (Not Current MS-MVP)

My Geek Site: http://kgiii.info
Web Hosting: http://whathostingshould.be

"In solving a problem of this sort, the grand thing is to be able to reason
backwards. That is a very useful accomplishment, and a
very easy one, but people do not practise it much. In the every-day affairs
of life it is more useful to reason forwards, and so
the other comes to be neglected. There are fifty who can reason
synthetically for one who can reason analytically." - Sherlock
Holmes
 
Galen,

I've wrongly described the situation. It's User A and User B on the same
desktop.
When User A walks away w/o logging off, he/she ties up the resources so user
B can't launch the same app when they log in. I wasn't clear on that. When I
open up Task manager on User B's login, I get the MS error. I also don't see
the application running under Task Manager so that I can kill it. I have to
log back in as User A, then kill the app before any other user can login to
use the app.
 
My reply is at the bottom of your sent message.

In
Galen,

I've wrongly described the situation. It's User A and User B on the same
desktop.
When User A walks away w/o logging off, he/she ties up the resources so
user
B can't launch the same app when they log in. I wasn't clear on that. When
I
open up Task manager on User B's login, I get the MS error. I also don't
see
the application running under Task Manager so that I can kill it. I have
to
log back in as User A, then kill the app before any other user can login
to
use the app.
Click to expand...

I don't honestly know if this will work. But... You can try disabling fast
user switching and then changing the settings to go to a screen saver after
x-minutes and select the option to make the login screen appear.

--
Galen (Not Current MS-MVP)

My Geek Site: http://kgiii.info
Web Hosting: http://whathostingshould.be

"In solving a problem of this sort, the grand thing is to be able to reason
backwards. That is a very useful accomplishment, and a
very easy one, but people do not practise it much. In the every-day affairs
of life it is more useful to reason forwards, and so
the other comes to be neglected. There are fifty who can reason
synthetically for one who can reason analytically." - Sherlock
Holmes
 
Back
Top