Terminal Services Idle Timeout Problems
We have multiple Windows 2003 terminal servers. We have configured group policy to end active but idle sessions after 1 hour. What is happening though is that users are kicked off the terminal server after about 5-10 idle minutes. They get no pop-up warning that their session will end, it just logs them off. They have to log back on and restart any programs that were open. I have checked the individual terminal services configuration and the Sessions tab for each user. There are no settings that would impose a shorter idle timeout. We're also getting no messages in the event log that corresponds to this. Any ideas?
ASKER
The GPO with the idle session timeout settings has the 'no override' checked.
It will give the effect that it will not let GPO linked closer to object than the the GPO override when policy settings are in conflict. Depending on version of OS/GPMC, it will be labeled 'no override' as its own flag or merged into enforced.
Run RSOP.msc to find the effective policy setting and what GPO is configuring this. If that GPO-link has 'no override' enabled, the option flag nead to be cleared to let the new GPO take effect when linked closer to computer object.
Run RSOP.msc to find the effective policy setting and what GPO is configuring this. If that GPO-link has 'no override' enabled, the option flag nead to be cleared to let the new GPO take effect when linked closer to computer object.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Use RSOP.msc to check where the effective policy setting is applied from.
Normally GPOs linked closer to object will take precedence of GPO linked to higher level in the structure when policy settings conflicts, but this can be overruled when configuring a GPO to be Enforced to deny any other GPO to override when settings conflicts. Right-click the GPO-link in GPMC to see if it has the Enforced flag set.