Re: Clients Being Locked out After Being Idle
- From: Jennifer Mar <ph1sh99@xxxxxxxxxxx>
- Date: Thu, 29 Sep 2005 12:37:27 -0400
check your screen saver settings. we set ours to lock after 10 minutes of being idle. by default the profiles takes the setting off the server's settings.
dbarasch wrote:
I have a windows 2003 terminal services environment. The clients connect to the server using WYSE thin clients. The connection has a preset username and password in the WYSE box for connecting the client to the server. There is no reason for the user to know the Windows username and password as the session is heavily locked down using Group Policies. They only have one application to use which askes them for thier username and password for that system.
My problem is after some time of being idle the client session gets locked out of thier account. They are still connected, but locked out. When users return to use thier computer its asking for a password to unlock the session. How can I make it so that it never locks them out. I do have a policy in effect that sets a 1 hour time limit for active but idle terminal sessions. But that would put them in a disconnected state when that time limit is reached. As I said the session is still connected but account locked. Any suggestions?
.
- Prev by Date: Client Sessions Slow To Log Off
- Next by Date: Re: Delete temp internet files at logoff
- Previous by thread: Client Sessions Slow To Log Off
- Next by thread: Re: Clients Being Locked out After Being Idle
- Index(es):
Relevant Pages
|
Loading