i.e: The user is away from their device, and stopped interacting with their Session but the RDP connection is still established. Idle session limit: With this setting you can ask Windows to Disconnect an Active session when the time elapsed since the "last input time" exceeds a certain value. This settings will have no effect on "Active" sessions.Īctive session limit: That's to prevent user from keeping their session Active indefinitely, be careful with this setting because it will disconnect the user even if they are actively working. Here we can see where we can manage the timeouts in the Session Collection settings, I'll explain these settings below:Įnd a disconnected session: Here you can tell Windows when you want to Log Off sessions shown as "Disconnected", that's based on what I call the "Session Idle Time" i.e. You can use the group policy if you have special needs that you can't address with Session Collection settings, but please be sure that you are not configuring different values between Session Collection settings and Group Policy, and that you can keep track of your settings. Now we can talk about managing the timeouts.įirst of all, I recommend you to set the policy you configured ("Set time limits for disconnected session") back as "Not Configured" because we should manage this from the Session Collection settings. Windows keeps track of this but will not show you this value. We have the "last input time" too, that's the last time the user did something within their Active session. Let's call this value the "Session Idle Time" for the sake of simplicity. Forget about this value if the session state is "Active". We have the "Idle Time" shown in Server Manager => That's the time elapsed between the value shown in "Disconnect Time" and "Now". I call that the "last input time", and Windows will not show you this value. That's the case when the user is technically connected to the Session Host ("Active") but away from their device, or when the user is not interacting with the RDP window. However, the second thing you should be aware of is that there is another "Idle" concept: The time elapsed between the last user input when the session is Active. And because the session is Active, this value is meaningless (the session is idle only when Disconnected, and now the session is Active). However, here comes the first catch: When a user Reconnects to their Disconnected session, Windows will update the Session State from Disconnected to Active again, but the Disconnect Time value will not be erased, the Disconnect Time still shows the last time the user disconnected, and the Idle Time value will still happily show you the time elasped between the value shown in Disconnect Time and Now. So far, so good, because a user disconnects, the session state is updated, the Disconnect Time is updated too, and when you open up the Server Manager, the Idle time column shows you the time elasped between the value shown in Disconnect Time and Now. The Idle Time value is simply the difference between "Now" and the Disconnect Time. When a user disconnects (for example, by closing the RDP window without logging off), Windows will update the Session State from Active to Disconnected and update the Disconnect Time too. The Idle Time reported by Remote Desktop Services is misleading because the value is only relevant when the Session State is: Disconnected. If I'm understanding this correctly, they've been idle for a day and
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |