win server 2003 sp1 - cannot change TS idle session timeout

[Guest kwadz]

In our development environment, I can go to Terminal Services

Configuration\Connections - RDP-Tcp properties - sessions and check the top

box for override user settings, then select a value for all three of the

timeout options (end a disconnected session, active session limit, idle

session limit).

 

However, in our operational system, when I check the override box, the end a

disconnected session and idle session limit drop downs are still grayed out,

preventing me from changing their settings. Specifically, I want to change

the idle timeout from 15 min to 2 days, since our users keep getting booted

whenever they grab a cup of coffee.

 

I had one of our Windows SAs look into it and he suggested running rsop.msc

and checking the Administrative Templates for Terminal Services limitations,

but there is nothing pertaining to the session limits in there. The

operational support team says there is no domain admin account, either, so I

can't figure out how to get this setting changed.

 

Does anyone have any ideas? Registry hack? Setting override location?

 

Thanks!

[Guest Jeff Pitsch]

Re: win server 2003 sp1 - cannot change TS idle session timeout

 

Timeout can be set in the user policy and computer policy did you check

both areas? Grey'd out settings are almost always GPO.

 

Jeff Pitsch

Microsoft MVP - Terminal Server

Citrix Technology Professional

Provision Networks VIP

 

Forums not enough?

Get support from the experts at your business

http://jeffpitschconsulting.com

 

kwadz wrote:

> In our development environment, I can go to Terminal Services

> Configuration\Connections - RDP-Tcp properties - sessions and check the top

> box for override user settings, then select a value for all three of the

> timeout options (end a disconnected session, active session limit, idle

> session limit).

>

> However, in our operational system, when I check the override box, the end a

> disconnected session and idle session limit drop downs are still grayed out,

> preventing me from changing their settings. Specifically, I want to change

> the idle timeout from 15 min to 2 days, since our users keep getting booted

> whenever they grab a cup of coffee.

>

> I had one of our Windows SAs look into it and he suggested running rsop.msc

> and checking the Administrative Templates for Terminal Services limitations,

> but there is nothing pertaining to the session limits in there. The

> operational support team says there is no domain admin account, either, so I

> can't figure out how to get this setting changed.

>

> Does anyone have any ideas? Registry hack? Setting override location?

>

> Thanks!

[Guest kwadz]

Re: win server 2003 sp1 - cannot change TS idle session timeout

 

Jeff,

Thanks for your input. I'm not an SA, though, so I don't know how to go

about changing the policy. Is GPO a group policy?

 

"Jeff Pitsch" wrote:

> Timeout can be set in the user policy and computer policy did you check

> both areas? Grey'd out settings are almost always GPO.

>

> Jeff Pitsch

> Microsoft MVP - Terminal Server

> Citrix Technology Professional

> Provision Networks VIP

>

> Forums not enough?

> Get support from the experts at your business

> http://jeffpitschconsulting.com

>

> kwadz wrote:

> > In our development environment, I can go to Terminal Services

> > Configuration\Connections - RDP-Tcp properties - sessions and check the top

> > box for override user settings, then select a value for all three of the

> > timeout options (end a disconnected session, active session limit, idle

> > session limit).

> >

> > However, in our operational system, when I check the override box, the end a

> > disconnected session and idle session limit drop downs are still grayed out,

> > preventing me from changing their settings. Specifically, I want to change

> > the idle timeout from 15 min to 2 days, since our users keep getting booted

> > whenever they grab a cup of coffee.

> >

> > I had one of our Windows SAs look into it and he suggested running rsop.msc

> > and checking the Administrative Templates for Terminal Services limitations,

> > but there is nothing pertaining to the session limits in there. The

> > operational support team says there is no domain admin account, either, so I

> > can't figure out how to get this setting changed.

> >

> > Does anyone have any ideas? Registry hack? Setting override location?

> >

> > Thanks!

>