By default, when a user closes the RDP/RDS session window in a terminal client (
mstsc.exe, RDCMan or Remote Desktop HTML5 web client) by simply clicking the cross in the top right corner without logging off, his session goes into disconnected mode. In this mode, all apps, open files and windows are still running on a remote desktop server and consuming resources.
By default, a user’s RDP session in Windows may stay in the disconnected state until terminated by the user or administrator, or until the computer is restarted. It is quite convenient, since a user may any time connect to his old remote desktop session and go on working with running programs or open files.
In the following screenshot you can see that the disconnected user sessions on the RDS server running Windows Server 2016 are using about 40% of the server RAM. Also, these sessions may block open files on your file servers, cause problems of incorrect saving of data in the apps, roaming profile folders or on User Profile Disks.
quser command, you can view when a user RDP session was started, how long it was idle and the current session state.
To automatically terminate disconnected RDP/RDS sessions in a specified period of time, you need to set session limits (timeouts) correctly.
If you use an RDS server, you can configure session timeout parameters in the RDS collection settings on the Session tab.
Specify the time period, after which you want to kill a disconnected remote desktop session, in the End a disconnected session option (by default, a session period is unlimited – Never). You can also set the maximum time of an active session (Active session limit) and end an idle session (Idle session limit). These hard timeouts are applied to all sessions in the RDS collection.
You can also set the limits of an RDP session in the properties of a local (
lusrmgr.msc) or domain user (
dsa.msc — Active Directory Users and Computers console).
In Windows Server 2012 R2/2016/2019, you can set RDP session timeouts using Group Policies. You can do it either in the domain GPO editor (
gpmc.msc) or in the Local Group Policy Editor (
gpedit.msc) on an RDS server or client (if you are using a desktop Windows edition as a terminal server).
The settings of RDP session timeouts are located in the following GPO section Computer Configuration -> Policies -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Session Time Limits. The following Remote Desktop timeout settings are available:
- Set time limit for disconnected session;
- Set time limit for active but idle Remote Desktop Services sessions — the policy allows idle RDP sessions to be terminated that have no user input (like moving a mouse or typing something on a keyboard);
- Set time limit for active Remote Desktop Services sessions — it is the maximum time of any RDP session (even an active one), after which it gets disconnected;
- End Session when time limits are reached — sets the time, after which an RDP session will be terminated (logoff) instead of disconnecting it;
- Set time limit for logoff of RemoteApp sessions.
By default, these options are not configured. To automatically terminate disconnected RDP user sessions in 8 hours, enable the Set time limit for disconnected session policy and select 8 hours in the dropdown list.
Save the changes and update the Group Policy settings on your RD host (
gpupdate /force). New timeout settings will be applied to new RDP sessions only (you will have to end the current RDS sessions manually).
In Windows Server 2008 R2, you could also set RDP session timeouts using a special console: tsconfig.msc (RD Session Host Configuration). It was enough to open the console and right-click RDP-Tcp -> Properties. The settings of session limits are located on the Sessions tab. However, there is no such console in newer Windows Server versions (although you can manually copy tsadmin.msc and tsconfig.msc files and use these consoles on newer Windows Server versions as well).