In Windows Server 2022/2019/2016/2012R2, you can set RDP session timeouts using Group Policies. These hard timeouts are applied to all user sessions in the RDS collection. You can also set the maximum time of an active user session ( Active session limit) and end an idle session ( Idle session limit). Specify the time period, after which you want to kill a disconnected remote desktop session, at the End a disconnected session option (by default, an RDP session duration is unlimited – Never). If you have a Remote Desktop Services farm deployed on Windows Server, you can configure user session timeout settings in the RDS collection settings on the Session tab. To automatically end disconnected RDP/RDS sessions in a specified period of time, you need to set session limits (timeouts) correctly. Automatically Log off Disconnected and Idle Remote Desktop User Sessions You can configure the maximum duration of active, disconnected, and idle (no user activity) sessions for Remote Desktop Services. Get-RDUserSession -ConnectionBroker $connectionBrocker |select-object -Property CollectionName, HostServer, DomainName, UserName, ServerIPAddress, CreateTime, DisconnectTime, SessionState, IdleTime, SessionID, (hours:minutes)' Expression= You can also display information about the duration of user sessions in the RDS farm using a PowerShell script (specify the FQDN of your RDS Connection Broker server): Using the qusercommand, you can view when a user RDP session was started, how long it was idle, and the current session state.
0 kommentar(er)
