|
Question : Explenation about the sessions tab of the RDP-TCP properties
|
|
Dear Experts,
Can someone PLEASE ( I award 500 p. for it) explain the options on the tab Sessions of the RDP-TCP Properties. I don't understand it!
To go to the RDP-TCP Properties, select: Start -> Administrative Tools -> Terminal Services Configuration Right click on the RDP-TCP connection and choose Properties.
These are the options:
Override User settings: End and disconnect session Active session limit Idle session limit (what means idle?) Override User settings: When session limit is reached or connection is broken: Disconnect from session End session
Peter
|
Answer : Explenation about the sessions tab of the RDP-TCP properties
|
|
These are options that allow you to control a user's connection status. In a perfect world a user logs on to a terminal server session , does there work an logs off. However, in the real world some users walk away for a couple of hours and leave their session open, or when complete they just disconnect rather than logging off. Rather than having dozens of open sessions with disconnected users you may want to control the status of these users and their Terminal Server sessions therefore:
Override user settings: The following options can be set user by user in the user's profile in active directory. Enabling this forces the options below to take priority, and applies to all users.
End and disconnect session: If a user chooses to disconnect or just hits the 'x' at the top of the screen rather than logging off, you can leave this at the default or set a time at which it will log off the user. They might have been called away briefly, or have a failed connection, so you wouldn't want to disconnect them right away, but you might want to do so after an hour.
Active session limit: this is not often used, but in some cases you may want to limit the length of time someone is able to work on the terminal server
Idle session limit: This allows you to force a logoff if the user remains connected, but there is no activity for an extended period of time. Idle would be not doing any work. I.e. they fell asleep at their desk or left without disconnecting or logging off.
Override User settings: Again, overrides similar profile settings
When session limit is reached or connection is broken: This allows you to choose what option will be taken when one of the above "action session" or "Idle session" limits is reached, or if a connection is broken. You can disconnect the session and the user can log back in at a later time. Unsaved changes are not lost and the user can continue working just as before. Or, "End session" which closes the session and logs the user off. They will loose any unsaved work.
|
|
|
|