RDP Slow Disconnect with Single Apllication

Posted on 2007-11-16
Last Modified: 2013-11-21
First post. I stumbled from being a "Power User" to being a Network Admin for about a year now. I work on my own, and have had to learn most everything on my own as well. I've searched and tweaked and tinkered, but I can't get the RDC to close immediately on remote computers.

The single application that opens on Windows Server 2003 is a log in to an EMR (Electrronic Medical Record) located on another database server. I disconnected and relogged in immediately through RDC. If the just the RDC screen is closed, I've been able to log back in and still be logged into the application! This is not good for security. If the application is closed, then the screen hangs there for a good bit, until finally "Saving your settings....." When logged on as just a user, without the single application, it closes immediately.

I know it's possible to close the application and close the RDC screen, and sessions will end, but I need to make it completely and totally idiot proof for the ....ummm ..........physicians ......the technological gap ......let's say .................very large!

RDP 5.2.
Separate Terminal Services profile folders from Roaming profile folders.
Open SINGLE APPLICATION at start is set in User Profiles, (not RDP although I've tried that too)
End Session 1 minute. (I've tested this at different settings)
Idle-1 minute

END DISCONNECTED SESSION is selected both in User Profile and TS Configuration.

I don't know if this is something on the end user computer, or on the Windows Server 2003? Cache issues? Do I even need to give a TS profile folder for a single application opening?
Question by:lkg173
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
LVL 31

Expert Comment

by:Cláudio Rodrigues
ID: 20302468
Use this article I wrote and patch the RDP client to prevent them from clicking the 'X' (Close) button on the RDP client.

Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services
LVL 45

Expert Comment

ID: 20307581
lherrou - Pleased you caught that one...

Author Comment

ID: 20308729

I'm a newbie, so I guess I got one of the wrong Philosophy degrees too. I'll have to go back and re-read the definition of Philosophy. Do universities give refunds?

"If I can tweak, change and even break something, I will do it. Just for fun." tsmvp, nice article and that is a really cool tweak, but not the solution in this case.

Resolve Critical IT Incidents Fast

If your data, services or processes become compromised, your organization can suffer damage in just minutes and how fast you communicate during a major IT incident is everything. Learn how to immediately identify incidents & best practices to resolve them quickly and effectively.

LVL 31

Expert Comment

by:Cláudio Rodrigues
ID: 20308950
Well so I guess I did not understand exactly what you are trying to achieve. From your post, what I understood is this:
1. Users connect to the TS. As they have an application set to start once they connect, they do not see the TS desktop, but your application.
2. As they are closing the application NOT by closing it but by closing the TS Session window (they click the  'X' button), the application stays running but in a disconnected session so if they connect back in less than a minute they get the session - and the application - back, what you do not want.

From what I got what you are looking for is some sort of instantaneous close of the session when they click on the 'X' button and not when the close your application properly.
Is that correct?
If that is the case, sorry, you are out of luck.
But if you read the article I sent you the link you will see your problem is all happening because you ALLOW them to click on the 'X' button, disconnecting the session. If you DISABLE such button they will have no other option than closing the application properly what means they will NEVER be able to reconnect again and get the application still running, what you are trying to avoid. Simple as that.

Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services

Author Comment

ID: 20309441
Yes that's correct. You understood correctly, but I think I misunderstood the solution.

Is the Reg Edit workaround to be done on the TS or the Client?


LVL 31

Accepted Solution

Cláudio Rodrigues earned 500 total points
ID: 20309778
On the client. You must basically patch the Microsoft RDP Client executable by following the steps I list on the article. After you do that you will have a new executable that disables such close button, forcing the users to properly close the application, completely eliminating the issue.
There is another article I wrote on the same website that explains how to repackage the 'new' client so you can create a new MSI and deploy it to PCs using group policies.

Claudio Rodrigues
CEO, TSFactory Inc.

Microsoft MVP
Windows Server - Terminal Services

Author Closing Comment

ID: 31409687
Thanks, that clears it up.

Though it would be nice to be able to just do it from a TS, but that might take the fun out finding work arounds. lol


Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Upgrading from SBS2003 to Windows Server 2012r2 Essentials 13 74
aes256 Ransomware on SBS 2011 13 75
Windows 2008 set profile 9 62
endpoint protection and patch status - SCCM 3 74
Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question