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

Add Printer: Windows cannot connect to the printer. FIXED!

  Fix Windows Cannot Connect to the Printer Issue. Easily! 1. Search "Registry Editor" 2. Locate Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print and right-click select  New > Key  >  "DWORD (32-bit) Value" 3. Rename the file to  RpcAuthnLevelPrivacyEnabled 4. Right Click select " Modify..." 5. Make sure the Value name is correct " RpcAuthnLevelPrivacyEnabled" Value Data is 0  and the Base is Hexadecimal and click  OK . And now follow the steps below to stop the Print Spooler service  and then start it again. 1. Press Win+R (Windows logo key and R key) at the same time. A Run dialog box will open. Type services.msc in the run box and click OK button. 2. In the Name list, locate and double-click on services  Print Spooler . 3. Click Restart. Congratulations! 
Post a Comment
Read more

Windows Local Drive System Migration or Clone Disk using DiskGenius

Preparations for Cloning C Drive Before proceeding to the steps of cloning the C drive to an SSD, you should pay attention to following aspects. 1. The new SSD has enough storage space. It is important to make sure the target SSD has sufficient storage space to receive all data on your C drive, for the cloning C drive process will create an exact copy of installed Windows 10 operating system, applications, and data. If the SSD is not large enough, you should consider cleaning up unnecessary files from the C drive in advance, or you are likely to face low disk space issue on the new SSD. If the target SSD contains files, please also make sure these files have been backed up to somewhere else. That's because everything on the target SSD will be removed during the C drive cloning process. 2. Properly connect the SSD to your computer. You can connect the new SSD to your computer using a USB-to-SATA cable or SSD-to-USB adapter, depending on whether your SSD is internal or external. Just...
Post a Comment
Read more