May 23 2022 02:31 AM
May 23 2022 02:31 AM
I have configured GPO to Set time limit for active but idle Remote Desktop Services sessions. Policy has been set to disconnect sessions which are idle for more than 3 hours. But I am getting warning after 30 minutes itself. This GPO has been applied at OU level. Issue occurs only with Windows 2019 servers. Session time limits on Windows 2016 servers which are in the same OU works well. I ran gpresult /h on the affected servers. I could see session time limit policy is applied properly still sessions are getting disconnected after 30 minutes.
Anyone came across this issue? Please assist me
May 25 2022 05:44 AM
If you face a session time-limit policy issue that gets disconnected after the meantime. You can follow the steps below in order to fix the issue,
By default, the user’s RDP session in Windows may stay disconnected until the user or administrator terminates, or the computer is restarted. However, it is quite convenient since a user may connect to his old RDP session and go on working with running programs.
In order to terminate disconnected RDP/RDS sessions automatically in a specified time period, you need to set session limits (time-outs) correctly. If you are using an RDS server, you will have to configure session time-out parameters from the RDS collection settings in the Session tab menu.
You will have to Specify the time period after which you want to disconnect the RDP session. Lastly, a disconnected session option (by default, a session period is unlimited – Never). Thus, you can set the maximum duration of an active session (Active session limit) and end an idle session (Idle session limit). These hard time-outs are applied to all sessions in the RDS collection.
You can set RDP session time-outs using user Group Policies. You can do this either in the domain GPO editor (gpmc.msc) or the Local Group Policy Editor (gpedit.msc) on a Remote desktop session or the RDS client.
RDP session timeout settings are found under following GPO sections Computer Configuration -> Policies -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Session Time Limits.
Below are the Remote Desktop time-out settings which are available:
By default, these options are not configured. For example, to automatically terminate disconnected RDP user sessions in 7 hours, You will have to enable Set time limit for the disconnected session policy and select 7 hours from the dropdown list.
At last, save all the changes and update the Group Policy settings on your RD host (gpupdate /force). Now, the new time-out settings will be applied to the latest RDP sessions. Hence, as a result, sessions will only get disconnected after the specified time which is provided by you.
Hopefully, the information above will assist you in resolving the session time-out issue.
May 31 2022 07:38 AM
Aug 08 2022 05:42 AM - edited Aug 08 2022 05:43 AM
@effjaayNo, I have applied workaround by configuring these policies in local policy on the affected servers.
Aug 08 2022 06:06 AM