LSeven
asked on
Users going idle longer than timeout set
I have a Windows Server 2003 Enterprise Cluster of Terminal Servers. I have four servers. I have two group policies set that regulate how long a person can stay idle. While these policies seem to work most of the time, FROM TIME TO TIME, a user stays idle for much longer than they should. When I run a gpresults on that user for the server they are on, the results wizard shows that the correct policies are implemented and are being applied. This usually does not happen to the same users and it happens to users that fall under either policy.
asavener
I thought terminal server idle timeout is a setting per computer, not per user. Is the GPO applied to the server?
Session timeout settings are computer configuration policy settings and this behavior shall not matter what user is logging on.
A possibly reason is that the user profile isn't unloaded correctly. Install UPHClean to get a helping hand with unloading user profiles.
http://www.microsoft.com/downloads/details.aspx?FamilyId=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
A possibly reason is that the user profile isn't unloaded correctly. Install UPHClean to get a helping hand with unloading user profiles.
http://www.microsoft.com/downloads/details.aspx?FamilyId=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
ASKER
The session time out settings are set by Group Policy under the user configuration section. This Group Policy is applied to the user OU. As I said before, this works 99% of the time, but one guy from time to time will have an idle session for many hours.
Do you have any documentation that says it is per computer only? That would be particularly strange since there is a setting in the user configuration sections and the resultant application of those settings has worked ALMOST all the time.
Do you have any documentation that says it is per computer only? That would be particularly strange since there is a setting in the user configuration sections and the resultant application of those settings has worked ALMOST all the time.
ASKER
http://technet.microsoft.com/en-us/library/cc758177.aspx
Specifically:
"These policies affect every client that connects to the terminal server. To define Session settings on a per-user basis, use the Sessions policies under User Configuration"
The first part of the article says to use Computer Configuration. This is a note at the end of that.
Specifically:
"These policies affect every client that connects to the terminal server. To define Session settings on a per-user basis, use the Sessions policies under User Configuration"
The first part of the article says to use Computer Configuration. This is a note at the end of that.
ASKER
Anyone?
I always configure TS-session GPO through computer configuration and had forgot that this is a setting that also can be configured under computer configuration. If using computer configuration, it will affect all users independent of what OU they're located in and also makes it possibly to have different session settings depending on what server is used for.
It will however not affect users using console session.
Have you installed UPHClean to force unload registry/profile?
It will however not affect users using console session.
Have you installed UPHClean to force unload registry/profile?
"also can be configured under computer configuration."
should had been
"also can be configured under user configuration."
should had been
"also can be configured under user configuration."
ASKER
I have not tried that yet. It seems to be related to roaming profiles though, which I do not use.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.