Best practice - to disconnect terminal users after inactivity

[Guest ChicagoPete]

Currently running Terminal Server 2000 and have several users that will NOT

logoff at end of day (no matter what you tell them!).

What is the best practice/cleanest way to disconnect these sessions after 2

hrs of inactivity?

 

Also, looking to move to Terminal Server 2003 shortly - same question.

 

thanks

[Guest Jeff Pitsch]

Re: Best practice - to disconnect terminal users after inactivity

 

Set the idle and disconnect times properly in either TS config or user

accounts for question 1. I guess I"m not sure what you're looking for here.

 

as for the 2nd, completely rebuild the server is truthfully the best

practice. make sure to upgrade your licenses and license server to Win2k3.

 

 

 

Jeff Pitsch

Microsoft MVP - Terminal Services

 

 

"ChicagoPete" <ChicagoPete@discussions.microsoft.com> wrote in message

news:E9ED283F-0E39-4E04-A153-980E3F728161@microsoft.com...

> Currently running Terminal Server 2000 and have several users that will

> NOT

> logoff at end of day (no matter what you tell them!).

> What is the best practice/cleanest way to disconnect these sessions after

> 2

> hrs of inactivity?

>

> Also, looking to move to Terminal Server 2003 shortly - same question.

>

> thanks

[Guest ChicagoPete]

Re: Best practice - to disconnect terminal users after inactivity

 

Thanks Jeff,

That is what I was looking for in T Server 2k.

As far as Term Server 2003, that will be a different,new box. Just wanted to

know where the timeout settings are in 2003 too.

 

"Jeff Pitsch" wrote:

> Set the idle and disconnect times properly in either TS config or user

> accounts for question 1. I guess I"m not sure what you're looking for here.

>

> as for the 2nd, completely rebuild the server is truthfully the best

> practice. make sure to upgrade your licenses and license server to Win2k3.

>

>

>

> Jeff Pitsch

> Microsoft MVP - Terminal Services

>

>

> "ChicagoPete" <ChicagoPete@discussions.microsoft.com> wrote in message

> news:E9ED283F-0E39-4E04-A153-980E3F728161@microsoft.com...

> > Currently running Terminal Server 2000 and have several users that will

> > NOT

> > logoff at end of day (no matter what you tell them!).

> > What is the best practice/cleanest way to disconnect these sessions after

> > 2

> > hrs of inactivity?

> >

> > Also, looking to move to Terminal Server 2003 shortly - same question.

> >

> > thanks

>

>

>

[Guest Jeff Pitsch]

Re: Best practice - to disconnect terminal users after inactivity

 

Same place plus you could set them through Group Policy as well.

 

Jeff Pitsch

Microsoft MVP - Terminal Services

 

"ChicagoPete" <ChicagoPete@discussions.microsoft.com> wrote in message

news:4308B446-81F2-4663-9EBC-44C4387E3DEE@microsoft.com...

> Thanks Jeff,

> That is what I was looking for in T Server 2k.

> As far as Term Server 2003, that will be a different,new box. Just wanted

> to

> know where the timeout settings are in 2003 too.

>

> "Jeff Pitsch" wrote:

>

>> Set the idle and disconnect times properly in either TS config or user

>> accounts for question 1. I guess I"m not sure what you're looking for

>> here.

>>

>> as for the 2nd, completely rebuild the server is truthfully the best

>> practice. make sure to upgrade your licenses and license server to

>> Win2k3.

>>

>>

>>

>> Jeff Pitsch

>> Microsoft MVP - Terminal Services

>>

>>

>> "ChicagoPete" <ChicagoPete@discussions.microsoft.com> wrote in message

>> news:E9ED283F-0E39-4E04-A153-980E3F728161@microsoft.com...

>> > Currently running Terminal Server 2000 and have several users that will

>> > NOT

>> > logoff at end of day (no matter what you tell them!).

>> > What is the best practice/cleanest way to disconnect these sessions

>> > after

>> > 2

>> > hrs of inactivity?

>> >

>> > Also, looking to move to Terminal Server 2003 shortly - same question.

>> >

>> > thanks

>>

>>

>>

[Guest Hernan Batista]

Re: Best practice - to disconnect terminal users after inactivity

 

Hi Mr Jeff, can you help me with the "key" on the GPO I should config to fix

idle and disconnected time for terminal users?

 

thanks

 

HB

 

"Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message

news:%23S7bK8I4IHA.4332@TK2MSFTNGP06.phx.gbl...

> Same place plus you could set them through Group Policy as well.

>

> Jeff Pitsch

> Microsoft MVP - Terminal Services

>

> "ChicagoPete" <ChicagoPete@discussions.microsoft.com> wrote in message

> news:4308B446-81F2-4663-9EBC-44C4387E3DEE@microsoft.com...

>> Thanks Jeff,

>> That is what I was looking for in T Server 2k.

>> As far as Term Server 2003, that will be a different,new box. Just wanted

>> to

>> know where the timeout settings are in 2003 too.

>>

>> "Jeff Pitsch" wrote:

>>

>>> Set the idle and disconnect times properly in either TS config or user

>>> accounts for question 1. I guess I"m not sure what you're looking for

>>> here.

>>>

>>> as for the 2nd, completely rebuild the server is truthfully the best

>>> practice. make sure to upgrade your licenses and license server to

>>> Win2k3.

>>>

>>>

>>>

>>> Jeff Pitsch

>>> Microsoft MVP - Terminal Services

>>>

>>>

>>> "ChicagoPete" <ChicagoPete@discussions.microsoft.com> wrote in message

>>> news:E9ED283F-0E39-4E04-A153-980E3F728161@microsoft.com...

>>> > Currently running Terminal Server 2000 and have several users that

>>> > will

>>> > NOT

>>> > logoff at end of day (no matter what you tell them!).

>>> > What is the best practice/cleanest way to disconnect these sessions

>>> > after

>>> > 2

>>> > hrs of inactivity?

>>> >

>>> > Also, looking to move to Terminal Server 2003 shortly - same question.

>>> >

>>> > thanks

>>>

>>>

>>>

>

>

[Guest Vera Noest [MVP]]

Re: Best practice - to disconnect terminal users after inactivity

 

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"

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Hernan Batista" <herbatz@cantv> wrote on 09 jul 2008 in

microsoft.public.windows.terminal_services:

> Hi Mr Jeff, can you help me with the "key" on the GPO I should

> config to fix idle and disconnected time for terminal users?

>

> thanks

>

> HB

>

> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message

> news:%23S7bK8I4IHA.4332@TK2MSFTNGP06.phx.gbl...

>> Same place plus you could set them through Group Policy as

>> well.

>>

>> Jeff Pitsch

>> Microsoft MVP - Terminal Services

>>

>> "ChicagoPete" <ChicagoPete@discussions.microsoft.com> wrote in

>> message

>> news:4308B446-81F2-4663-9EBC-44C4387E3DEE@microsoft.com...

>>> Thanks Jeff,

>>> That is what I was looking for in T Server 2k.

>>> As far as Term Server 2003, that will be a different,new box.

>>> Just wanted to

>>> know where the timeout settings are in 2003 too.

>>>

>>> "Jeff Pitsch" wrote:

>>>

>>>> Set the idle and disconnect times properly in either TS

>>>> config or user accounts for question 1. I guess I"m not sure

>>>> what you're looking for here.

>>>>

>>>> as for the 2nd, completely rebuild the server is truthfully

>>>> the best practice. make sure to upgrade your licenses and

>>>> license server to Win2k3.

>>>>

>>>>

>>>>

>>>> Jeff Pitsch

>>>> Microsoft MVP - Terminal Services

>>>>

>>>>

>>>> "ChicagoPete" <ChicagoPete@discussions.microsoft.com> wrote

>>>> in message

>>>> news:E9ED283F-0E39-4E04-A153-980E3F728161@microsoft.com...

>>>> > Currently running Terminal Server 2000 and have several

>>>> > users that will

>>>> > NOT

>>>> > logoff at end of day (no matter what you tell them!).

>>>> > What is the best practice/cleanest way to disconnect these

>>>> > sessions after

>>>> > 2

>>>> > hrs of inactivity?

>>>> >

>>>> > Also, looking to move to Terminal Server 2003 shortly -

>>>> > same question.

>>>> >

>>>> > thanks