Dashboard > Non-Metrix Tech Tips > ... > Windows Tips > "Logging Off" versus "Disconnecting" from remote desktop sessions > Information > Page Comparison
Non-Metrix Tech Tips Log In   View a printable version of the current page.
"Logging Off" versus "Disconnecting" from remote desktop sessions
Version 2 by A. Mitchell
on Apr 05, 2007 15:59.


compared with
Current by A. Mitchell
on Apr 05, 2007 16:01.

(show comment)
 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 1 changes. View first change.

  When you remote into one of our various servers (Long, Coney, Jamaica), there are two distinct ways to end your session: logging off and disconnecting. Under most circumstances, it is generally preferable to choose "Log off..." from the Start menu as opposed to just "disconnecting" by closing the remote desktop window (clicking the X that appears when you hover your mouse at the top of the screen). This is because logging off will close all your applications and free up all the memory that was keeping your session alive. By contrast, disconnecting keeps all the info about your session in memory and is waiting for you the next time you log back in. This sounds like a good thing, but on a slower machine like Jamaica, it has the effect of taking up resources (clock cycles, memory) that aren't being actively used. This can slow the machine down for others who are trying to log in.
  When you use the Remote Desktop client to remote into one a server, there are two distinct ways to end your session: logging off and disconnecting. Under most circumstances, it is generally preferable to choose "Log off..." from the Start menu as opposed to just "disconnecting" by closing the remote desktop window (clicking the X that appears when you hover your mouse at the top of the screen). This is because logging off will close all your applications and free up all the memory that was keeping your session alive. By contrast, disconnecting keeps all the info about your session in memory and is waiting for you the next time you log back in. This sounds like a good thing, but on a slower machine, it has the effect of taking up resources (clock cycles, memory) that aren't being actively used. This can slow the machine down for others who are trying to log in. It can also make it difficult for system administrators who need to perform maintenance on the machine, but don't know whether you have programs and documents open in your remote session.
  
 If you need the session to persist - e.g., you are running a really time-consuming query/process and don't want to have the window open while it runs - then "disconnecting" is fine and necessary. But if you're done working on the server for the time being, it's probably better to "log off", so your session ends properly.
  
 This distinction is described here:
  
 http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/42ac6680-50f4-42b1-b299-148c639bdc25.mspx
Site powered by a free Open Source Project / Non-profit License (more) of Confluence - the Enterprise wiki.
Learn more or evaluate Confluence for your organisation.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.1.1 Build:#406 Dec 23, 2005) - Bug/feature request - Contact Administrators