Enable Time Limit to Disconnect Remote Desktop After Inactivity

When using Remote Desktop Protocol (RDP) on Windows, users often face challenges when disconnecting sessions without logging off, leading to sessions transitioning to a disconnected state. In this guide, we explore effective strategies to automatically log off disconnected and idle remote desktop sessions, providing insights into managing system resources efficiently. See Disable credential Prompts for Remote Desktop Connections, and to know your RD version, see Determine the Remote Desktop Client Version.

By default, Windows maintains RDP sessions in a disconnected state until manually terminated or until the system undergoes a restart. While this feature allows users to reconnect to previous sessions seamlessly, it can pose challenges, such as consuming valuable system resources.

In a typical scenario, these disconnected sessions can occupy a significant portion of server RAM, impacting overall performance. See Protect Remote Desktop credentials with Windows Defender Remote Credential Guard or Restricted Admin Mode, and View RDP Configuration Settings: Connect automatically on an RDP session.

Monitoring RDP Sessions with quser Command and PowerShell

To gain insights into RDP sessions, the quser command proves invaluable. It allows users to view the initiation time, idle duration, and current state of RDP sessions. See this detailed guide on How to Find Out Which Users Are Logged on Windows Server.

Follow the steps below to monitor RDP sessions. Launch the PowerShell as administrator.

Enter the “quser“ or “query user” Command:

quser

query user

Configure RDP/RDS session time limits via GPO

In Windows Server environments such as 2022, 2019, 2016, and 2012R2, the management of Remote Desktop Protocol (RDP) session timeouts can be accomplished through Group Policies. Follow the steps below:

Press the Windows key + R to open the Run utility. Type gpedit.msc to open the Local Group Policy Editor. For domain Group Policy Object (GPO) editor type gpmc.msc.

Run utility for Group Policy — *Open the local Group Policy editor*

To access the settings for RDP session timeouts in the Local Group Policy Editor, navigate to:

Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Session Time Limits within the GPO

*Navigate to Session time limits policy*

For (GPO), navigate to:

Computer Configuration -> Policies -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Session Time Limits within the GPO

To remove disconnected session, double-click “Set time limit for disconnected sessions.”

*Open Set time limit for disconnected sessions*

To automatically end all disconnected RDP user sessions in 6 hours, enable the “Set time limit for disconnected sessions” policy and select 6 hours from the dropdown list.

*Set the session time limit for disconnected users*

Click Apply and OK to save the changes.

To set the time limit for active but idle Remote Desktop Services sessions, double-click to open the option, enable the policy, and then set the time limit.

To update the Group Policy settings on your RD host, run command prompt as administrator, and run the command “gpupdate /force.”

Note that new timeout settings will only apply to new RDP sessions, requiring manual termination of current user sessions on RDSH.

Conclusion

In conclusion, this guide empowers users to enhance their Remote Desktop sessions on Windows. From monitoring and managing disconnected sessions to configuring effective timeouts, it offers valuable insights.

FAQs

Can I apply RDP session time limit changes without disrupting current user sessions?

No, updating RDP session time limit settings through Group Policy will not immediately impact existing user sessions. The new timeout settings will only apply to new RDP sessions. To enforce the changes for existing sessions, administrators may need to manually terminate or wait for users to log off and reconnect. It’s advisable to communicate any policy changes to users and schedule updates during periods of lower activity to minimize disruptions.

Why should I monitor Remote Desktop Protocol (RDP) sessions using quser and PowerShell?

Monitoring RDP sessions provides valuable insights into user activity, session initiation times, and idle durations. This helps administrators identify active sessions, manage system resources efficiently, and troubleshoot issues promptly. The quser command, when used with PowerShell, offers a convenient way to stay informed about who is connected to the server through RDP and their current session status.

How does setting RDP session time limits via Group Policy benefit system performance?

Configuring RDP session time limits through Group Policy is crucial for optimizing system performance. By setting time limits for disconnected sessions, you ensure that resources are not unnecessarily occupied by idle connections. This proactive approach helps prevent the accumulation of disconnected sessions, freeing up server resources and enhancing overall performance. It’s a strategic way to manage and maintain a healthy computing environment.

I hope you found this article useful on how to Enable Time Limit to Disconnect Remote Desktop After Inactivity. Please feel free to leave a comment below.