Timeout after 10 minutes

[Guest James Trogdon]

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.

[Guest Vera Noest [MVP]]

Re: Timeout after 10 minutes

 

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@nowhere.net> 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.

[Guest James Trogdon]

Re: Timeout after 10 minutes

 

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@nowhere.net> 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.

[Guest Soo Kuan Teo [MSFT]]

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@nowhere.net> wrote in message

news:uwtZaix9IHA.4492@TK2MSFTNGP03.phx.gbl...

> 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@nowhere.net> 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.

[Guest James Trogdon]

Re: Timeout after 10 minutes

 

I changed the group policy after everybody had already left for the day

and there was no one on the terminal server. I then logged a user on to

test it which of course it still disconnected after 10 minutes of idle time.

 

James.

 

Soo Kuan Teo [MSFT] wrote:

> 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

>

>

>

[Guest Vera Noest [MVP]]

Re: Timeout after 10 minutes

 

You wrote that your users are logging in with local accounts, not

domain account, but is your TS a menber of a domain? Because if it

is, there could still be a domain-wide policy overriding your local

settings.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

James Trogdon <noone@nowhere.net> wrote on 05 aug 2008 in

microsoft.public.windows.terminal_services:

> I changed the group policy after everybody had already left for

> the day and there was no one on the terminal server. I then

> logged a user on to test it which of course it still

> disconnected after 10 minutes of idle time.

>

> James.

>

> Soo Kuan Teo [MSFT] wrote:

>> 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

[Guest James Trogdon]

Re: Timeout after 10 minutes

 

I found the solution. My users are using Windows Mobile 5 scan guns

while using the Windows Mobile 6 Remote Desktop program. In the

"default.rdp" in the Windows folder on the gun was this line:

 

MinutesToIdleTimeout:i:5

 

I changed it to this:

 

MinutesToIdleTimeout:i:0

 

and everything works as intended. No timeouts. WooHoo!

 

Thanks for all the suggestions!

 

James.

 

 

Vera Noest [MVP] wrote:

> You wrote that your users are logging in with local accounts, not

> domain account, but is your TS a menber of a domain? Because if it

> is, there could still be a domain-wide policy overriding your local

> settings.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> James Trogdon <noone@nowhere.net> wrote on 05 aug 2008 in

> microsoft.public.windows.terminal_services:

>

>> I changed the group policy after everybody had already left for

>> the day and there was no one on the terminal server. I then

>> logged a user on to test it which of course it still

>> disconnected after 10 minutes of idle time.

>>

>> James.

>>

>> Soo Kuan Teo [MSFT] wrote:

>>> 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