Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Windows 7 x64 machine that I remote desktop into. The problem I have is when I log into the machine it loads the desktop fine. Once I close the remote desktop (no official log out.) and then log back in it reloads the desktop. I want it to preserve the session I was working in last time rather than resetting the session.

This is a headless machine so I log in initial and always from a remote machine.

share|improve this question
what do you use for remote desktop? – Deniz Zoeteman Oct 26 '09 at 19:37
I use the Remote desktop that comes with Windows XP Service Pack 3. – Jeremy Edwards Oct 26 '09 at 19:46
How are you closing the session? Just the X? – Andrew Coleson Oct 26 '09 at 19:52
Yes, I just click the X in the upper right hand corner of the window. – Jeremy Edwards Oct 26 '09 at 20:14
I use Windows7 all the time. I login to it remotely from an XP SP3 machine and I have NEVER had the problem you describe. You dont need to worry about "console" session. – djangofan Nov 3 '09 at 15:50

I use XP's built-in RDP when I need to connect to my Win7 box at home from work. I've not run into the problem you are describing, but typically when I close an RDP session I use Start > Disconnect instead of clicking the X in the corner of the RDP bar (but either method should disconnect instead of logging you off.) I'd suggest checking to see if you have more than one open session by using the QWINSTA command and kill any errant sessions using RWINSTA, then try reconnecting and see if the issue persists.

share|improve this answer

Terminal services manager tool will expose the 2 (or more) sessions you have connected and you should be able to tell the difference between the multiple sessions and it will you a hint to your problem. Make sure your external IP address always remains the same from connection to connection, otherwise it might think it needs to make a new session for you.

share|improve this answer

Something nobody else mentioned: perhaps your Terminal Services configuration on the Windows7 machine is set so that sessions expire after they are inactive for a few minutes?

share|improve this answer

You must log in to answer this question.

protected by Ivo Flipse Feb 24 '11 at 20:34

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged .