Re: Timeout after 10 minutes

local Group policy settings should not affect existing sessions, i.e. if you change local gp while there are existing sessions, those sessions will not be affected by the new local gp.
Can you please try to logoff all sessions. and see if the issue still happen to new sessions?
Thanks
Soo Kuan



--
This posting is provided "AS IS" with no warranties, and confers no rights.

"James Trogdon" <noone@xxxxxxxxxxx> wrote in message news:uwtZaix9IHA.4492@xxxxxxxxxxxxxxxxxxxxxxx
Yes, each user gets a Disconnect message and not a black screen. I have also watched the TS Manager disconnect them after 10 minutes of idle time. All screen savers for every account have been turned off. Any ideas?

James Trogdon


Vera Noest [MVP] wrote:
Have you verified that their sessions really get the status "Disconnected" in TS Manager?
10 minutes is the default time for the screen saver to kick in, and it's totally black. Your users wouldn't be the first ones to confuse their black screens with a disconnected session.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

James Trogdon <noone@xxxxxxxxxxx> wrote on 05 aug 2008:

I have a Windows 2003 R2 Terminal server that is using the Local
User and Groups and NOT Active Directory. I have set the Group
Policy as follows:

Computer Configuration - Administrative templates - Windows
Components - Terminal Services - Sessions

"Set time limit for disconnected sessions" = 1 Day
"Sets a time limit for active Terminal Services sessions" = 1
Day "Sets a time limit for active but idle Terminal Services
sessions" = 1 Day "Terminate session when time limits are
reached" = Enabled
After 10 minutes of idle time the client will disconnect. Their
session is active which is what I want but they shouldn't be
disconnecting. Do I need to restart the Terminal Server service
since I changed the Group Policy? If so, I can I do this
without restarting the entire server? Each user setting in
Computer Management shows the 1 Day time limit but they still
disconnect after 10 minutes of idle time. Thanks for any help
you can give me.
James.

.

Relevant Pages

  • Re: loging off users
    ... You can configure a time limit for idle sessions and configure them ... This can be done in Terminal Services Configuration, ... Components - Terminal Services - Sessions ...
    (microsoft.public.windows.terminal_services)
  • Timeout after 10 minutes
    ... Components - Terminal Services - Sessions ... "Sets a time limit for active Terminal Services sessions" = 1 Day ... "Terminate session when time limits are reached" = Enabled ... Do I need to restart the Terminal Server service since I changed the Group Policy? ...
    (microsoft.public.windows.terminal_services)
  • Re: End a disconnected session via GPO?
    ... Computer Configuration - Administrative templates - Windows ... Components - Terminal Services - Sessions ... "Sets a time limit for active Terminal Services sessions" ...
    (microsoft.public.windows.terminal_services)
  • Re: Time Outs in Terminal server
    ... Components - Terminal Services - Sessions ... "Terminate sessions when time limit is reached" ... MCSE, CCEA, Microsoft MVP - Terminal Server ... > to terminate the whole session to free that space. ...
    (microsoft.public.windows.terminal_services)
  • Re: Timeout after 10 minutes
    ... Components - Terminal Services - Sessions ... "Set time limit for disconnected sessions" = 1 Day ... After 10 minutes of idle time the client will disconnect. ...
    (microsoft.public.windows.terminal_services)