Remote Desktop disconnects when idle
How can I force the server to log off idle RDP session automatically? An idle or inactive session will also consume precious CPU resources and memory. When the number of concurrent connections has reached the limit, your best bet is to kick out idle users. In this tutorial we’ll show you how to use group policy to configure Windows to automatically log off idle remote desktop sessions. Automatically Log off Idle Remote Desktop Sessions in Windows
That’s it!
Modified on: Wed, 23 Feb, 2022 at 12:05 PM Occasionally a user might experience disconnection of an idle session. One reason this can occur is the configuration of the power settings on the client computer. A way to minimize the chances of disconnection of idle sessions, set the PCs power settings to stop the computer from going into sleep or hibernate modes.Deactivating the power management of the network card on the server and client can also be useful :It is also possible to set the server to keep alive all remote session using local policies.To do so, click start, type in "gpedit.msc"Locate the following local group policy :Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limit Here you will find 4 strategies that you may find useful. 1- Set time for disconnected sessions - This strategy is used for logging off a disconnected session after a certain time. This can also be set in the Admin tool.
Did you find it helpful? Yes No Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.
Symptom:
Page 2
|