Setup Windows Terminal Server to Disconnect Idle Sessions
Sometimes when I have logged onto our Windows 2003 Terminal Server there have been over a dozen idle sessions. Many of these sessions have only been idle for short periods of time, but often we have sessions that have been idle for many hours, and sometimes even days.
Today I decided to limit the amount of time that disconnected sessions can sit idle for. I figured that allowing a disconnected session to be idle for 1-day would be generous enough, but still save on the idle terminal server sessions.
There are two ways to set up Windows Terminal Server Session limits. One through the Terminal Server Group Policies, and the other way using Windows Terminal Services Configuration. Because I only run two Windows 2003 Terminal Servers I have decided to use the Windows Terminal Services Configuration to limit the idle session time.