jimbo45, i have been working in Support for more than 10 years, and i know what i'm talking about. My argument has nothing to do with self disconnection. It's got to do with when i am done on a RDP session i am to manually log it off.

My pc and the remote pc i am RDPing to has nothing to do with server or client connections. Any PC with RDP agent can RDP to another machine and by having such tool does make it a server.

"It definitely IS standard practice when connecting to remote servers such as ERP systems (SAP etc) or even your online Banking system to time users out after a certain period of inactivity ".

Why are you going off the tangent? this thread is about RDP logoff and disconnect option. NOT group policy or how you set the remote session to self disconnect.

No one would just leave an RDP session openned for it to self timed out to disconnect. This is not from the enduser but from the Support staff end.

aem, is it at all possible at this stage to log off before you disconnect? That would be a temporary fix to your problem.

Hi Av, it's isn't my problem really lol, was just an observation that if Windows 8 was to be made into RTM that this should need to be addressed. To answer your question you can go into a command prompt and use the logoff command i suppose.

Well I just found it interesting, because I know that on my 2 servers I am able to log off and/or lock the computer (from the Start Menu) before I disconnect... Even though it would be nice to have it automatically done, I am unable to tell, as I have no backend access to the servers.

Disconnecting a session leaves what you are doing still running, logoff by actually logging off your RDP connection would end what you're currently doing on that session wouldn't it?