I am using some of the Terminal Server settings in group policy BUT I am NOT
using the "Sessions" setting entitled "Sets a time limit for active but idle
terminal server sessions". it is currently set to 'Not configured". Instead,
I have this setting configured in the users active directory profile on an
individual basis as some users are different than others. It is set on the
'Sessions' tab of their AD profile - and is typically set to 30 minutes.
However, today I noticed that a user is logged onto our win2K3 server and
has been active and idle (not disconnected) for over 2 hours - when his
settings only allows for 30 minutes!!!
Why might it be that he has not been yet disconnected? (which is what I set
to happen once a session limit has been reached)
I should also mention that when I attempt to remote control this users
session, it appears to hang. Could this be why this particular session is
unable to be disconnected in the time frame stated?
Thanks, Brad