Main Page
 The gatekeeper of reality is
 quantified imagination.

Stay notified when site changes by adding your email address:

Your Email:

Bookmark and Share
Email Notification
Server 2008 RDP Timeout
Ever get the message that your RDP session has been terminated on Windows Server 2008 - that is the message "Your remote desktop session has ended because the remote computer didn't receive any input from you"? That type of thing can be anoying if you are running a diagnostic tool that requires an account be logged in to the server so that it can run...or other reasons you may have. The purpose of this tutorial is to show how I was able to burn some time to track down what was actually controlling RDP sessions to extend session timeouts. RDP relates to Windows Server 2008 R2 while Windows Server 2008 Standard uses Terminal Services; both of them, however, are strikingly similar.

  1. In many cases the RDP is controlled by a local policy so it would seem intuitive to open up gpedit.msc and take a look. As shown by the screenshot, however, it "appears" the RDP settings are not configured.
  2. You may ask if "Connections" section contains the RDP session settings...that is possible, but let's look at a different angle to solving the issue first.

  1. Well, in knowing the RDP Host is configured, let's go to Administrative Tools -> Remote Desktop Services -> Remote Desktop Session Host Configuration as shown.

  1. Once the window opens, right-click on the connection and select Properties.

  1. Shazzam! It looks like the RDP Host is configured after all, under the "Sessions" tab. What was changed here was "End a disconnected session" under the first "Override user settings" and "idle session limit" to extend the time to what was needed.

About Joe