How do I stop Remote Desktop from auto logout

User settings in sessions tab are set to never, never, never but Remote Desktop still auto logs out the users after 10 minutes.
My configuration is somewhat more complex in that my thin clients straddle two terminal servers.  The primary login to "server1", the DC, and then all application icons on Server1 transfer the users to "Server2", a member server, via RDP as well.  The login credentials are not the same for both servers.  The "second" login set are based upon the application that is being selected but these users again are setup on "server2" under the sessions tab as never, never, and never?  Do I have to add the second user set to the DC - and if so why?  Doesn't the second server 2003 control its on remote desktop?  This configuration is such to achieve speed, which it does!

Thanks in advance/
saahgAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

arnoldCommented:
Double check the GPO to make sure you do not have a terminal server force logout option versus disconnect.

Run gpmc with or Resultant set of policy on the Terminal server to determine which policies are applied.
0
mojopojoCommented:
Agreed: Check which GPOs are applied to your Terminal Server with Resultant Set of Policies (RSoP).

You'll find the settings here:

Computer Configuration - Administrative templates - Windows Components - Terminal Services - Sessions
"Set time limit for disconnected sessions"
"Sets a time limit for active Terminal Services sessions"
"Sets a time limit for active but idle Terminal Services sessions"
"Terminate session when time limits are reached"

Here is a rundown of all the Terminal Session GPO settings and what affect they will have on your users remote sessions:

http://technet.microsoft.com/en-us/library/cc753112(WS.10).aspx
0
saahgAuthor Commented:
Spent 6 hours on support with Microsoft yesterday - all of these switches was set including new keys added in the registry - no cigar.  What finally solved the problem was negating the screen saver loading to the Thin Clients upon initial login.  All your have to do is ALL you have to do!!

Thanks for the suggestions.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.