Skip to main content

Remote Desktop Services session timeout Setup in RD Session Host in Windows Servers

 



If you face a session time-limit policy issue that gets disconnected in 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:

Set the time limitation for the disconnected sessions to "NEVER"


Set time duration for active but idle Remote Desktop Service sessions -> The policy allows idle RDP sessions to get terminated which have no user inputs (like typing something on the keyboard or moving a mouse). You may set it to "NEVER"



Set time duration for active Remote Desktop Service sessions -> it is the maximum time duration of any RDP sessions, after which it gets terminated or disconnected after the set time limit. You may set it to "NEVER"


End Session when time durations are reached -> sets the time after which an RDP session will be logged off (terminated) instead of disconnecting it. Just simply set it to "DISABLED"



Lastly, set a time limitation for the logoff of RemoteApp sessions. You may set it to "NOT CONFIGURED OR DISABLE"


By default, these options are not configured. For example, to automatically terminate disconnected RDP user sessions in 7 hours, You will have to enable the 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.

Thank you

Comments

Post a Comment

Popular posts from this blog

Reset 120 day RDS Grace period on 2016 and 2019

  Reset 120 day RDS Grace period on 2016 and 2019 Enter the following command to check Grace Period: wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TerminalServiceSetting WHERE (__CLASS !=””) CALL GetGracePeriodDays  Confirm-deletion-of-the-timebomb-key-in-the-registry If you have a home lab environment or another lab where you continually test various solutions, licensing, and trial expiration is a challenge that you constantly tend to run into. It is just part of the fun of lab environments. While most trials are fairly “hard and fast” and don’t allow you to reset the trial expiration, if you work with Microsoft Windows Server and Remote Desktop Services (RDS), there is a “hack” that allows you to effectively reset the expiration of  Remote Desktop  Services grace period where you can essentially rewind the clock on your RDS licensing if you are making use of this role inside your lab environment. I am using Windows Server 2019 for my Windows workloads in my lab environment
Post a Comment
Read more

GitLab Repository Command Line Instructions

Start project repository Command line instructions You can also upload existing files from your computer using the instructions below. Git global setup git config --global user.name "Jaime Moncada" git config --global user.email "jaimemoncadajr@gmail.com" Create a new repository git clone https://gitlab.com/jaimemoncadajr/library-system.git cd library-system touch README.md git add README.md git commit -m "add README" git push -u origin master Push an existing folder cd existing_folder git init git remote add origin https://gitlab.com/jaimemoncadajr/library-system.git git add . git commit -m "Initial commit" git push -u origin master Push an existing Git repository cd existing_repo git remote rename origin old-origin git remote add origin https://gitlab.com/jaimemoncadajr/library-system.git git push -u origin --all git push -u origin --tags Credit :  https://gitlab.com OR Simple Way to Push an existing
2 comments
Read more