Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

At our school we use thin clients that connect to a Windows 2008 R2 server using Remote Desktop Services. This works very well.

One problem we still have is the login timeout for the RDP connection. When the thin client starts up, it shows the server login screen. However, after a small amount of time (one minute or so) the RDP session disconnects and the thin client shuts down (as it is configured to do). This is a problem for teachers that are used to powering up the computer at the start of the day and logging in when they first need it.

How can we change or disable this login timeout? We have looked at the various session timeout values, but there is nothing there to help us.

share|improve this question
There is a setting in the registry named DelayConMgrTimeout. Could this have something to do with it? – jan.vdbergh Aug 30 '12 at 7:47
up vote 7 down vote accepted

After some more searching on Google, I managed to find a solution.

The login timeout is set in the registry, with the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

Simply add a new DWORD value for LogonTimeout, containing the timeout value in seconds. After that, restart the Terminal Services service. (If you are connected via Remote Desktop, your session will be terminated.)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.