1

Looking for a solution to give the user the power to kill their RDP session to a remote app.

The application gets stuck and needs to be killed except I have multiple users on the same server under the same user name. So if possible needs to be by session ID.

When the application freezes the user would click a batch file or powershell script to enable the kill of the session ID they are currently using.

Note I can not change user names and can not change the Active directory to auto disconnect after a certain time as this is a active POS.

Any suggestions?

6 Spice ups
2

Are you sure they are logging onto the same RDP server using the same username? I don’t think that is possible.

2 Spice ups
3

Ctrl+Alt+Delete kill the process.

1 Spice up
4

Do you specify a program to launch at logon for that specific user? We do not run POS, but we have an app that uses the same AD account, and it launches a program at logon, and we ran into a similar need. I ended up doing this because even on the disconnect policy it never worked quite right. This runs in the background and when the user clicks the “x” or logs off this ensure the session is immediately disconnected. This was set under the User Configuration for RDS Start a Program on connection.

cd C:
cd c:\Program Files\Application
start /wait app.exe
logoff

1 Spice up
5

I would have to agree with B.L. Generally you cannot have the same remote session going with the same username and multiple users. Does not generally work like that unless you are using a 3rd party remote software.

6

batch file → pskill

but how you will ever know which PID matches which session since they all use the same user name is beyond me.

I think that’s why you want to use separate users.

1 Spice up
7

Seriously, do yourself a favor and make up a few extra usernames.

8

You’re saying that app gets stuck, but you want to kill the RDP session, instead of app’s process? Why?

Maybe that’s because by saying “remote app” you’re having RemoteApp on your mind?

9

Definitely possible; just not by default (nor would I recommend it - I, too, suggest different usernames based upon the limited information available).

Computer Configuration → (Policies ->) Administrative Templates → Terminal/RD Services → Terminal Server/RD Session Host → Connections - “Restrict TS/RD Services Users to a single TS/RD Session”

1 Spice up
10

I think that just forces them to pick up their disconnected session at next logon instead of creating a new connection, to stop users building up a list of disconnected sessions. Maybe the OP can make this a bit clearer.

1 Spice up
11

Its a Windows RemoteApp and the users do not have access to kill the process. They can not kill it from task manager as the remote app is on the server login not the user login.

12

Maybe it would be better to stick to old good Remote Desktop session with the only option to start given app in it? This way in a case it crashes, they can force kill it and restart it. This way they will not leave disconnected, dead sessions on the server. If the app is not stable, perhaps you simply shouldn’t be using it via RemoteApp.

13

This is proably the closest we will get, as the program can not be closes out by clicking “X” the program was designed that way. I think with this and a secondary addition to the batch file we could get this to work! I will keep you updated.

Sean Donnelly May 20, 2013 at 1:20 PM
Do you specify a program to launch at logon for that specific user? We do not run POS, but we have an app that uses the same AD account, and it launches a program at logon, and we ran into a similar need. I ended up doing this because even on the disconnect policy it never worked quite right. This runs in the background and when the user clicks the “x” or logs off this ensure the session is immediately disconnected. This was set under the User Configuration for RDS Start a Program on connection.

cd C:\
cd c:\Program Files\Application
start /wait app.exe
logoff
14

Good luck it works great for me!

15

One thing I never mentioned was that in the program start for TS is I called out a batch file that contains the above syntax. This launches the application and is also what allows it to close out properly. All done via GPO.

16

Krizz May 23, 2013 at 3:29 PM
Maybe it would be better to stick to old good Remote Desktop session with the only option to start given app in it? This way in a case it crashes, they can force kill it and restart it. This way they will not leave disconnected, dead sessions on the server. If the app is not stable, perhaps you simply shouldn’t be using it via RemoteApp.

Unfortunately I have almost 100 locations and 5-10 users at each. I inherited this system. Most users can not even get to control panel without calling in. With it being a POS I have printers, signature pads and check software that all relay information through the remote app to the server. Kinda stuck with what I got unfortunately. The POS software program is a POS daily.

You are Correct on that B.L.S. the session I.D. needs to be completely terminated otherwise the Remote app will just start again with the"frozen" session.

17

Thanks! Yeah I figured that was the case. We should have thought of that. That gets us on the right path, Its us against the users :wink: haha

Sean Donnelly May 23, 2013 at 3:50 PM
One thing I never mentioned was that in the program start for TS is I called out a batch file that contains the above syntax. This launches the application and is also what allows it to close out properly. All done via GPO

18

Excellent any issues let me know and I’ll do my best to help, good luck Pat.