Terminal Server Group Policy Question

  • Thread starter Thread starter theGerm
  • Start date Start date
T

theGerm

Guest
I have a windows 2003 domain controller and a Windows 2003 Terminal
Server.

In a OU I have a Management Group Policy in which I configureed the
computer configuration and the user coniguration areas dealing with
terminal services.

User Config > Admin Templates > Windows Components > Terminal Services
> Sessions
Computer Configuration > Admin Templates > Windows Components >
Terminal Services > Sessions

For testing I set the "Sets a time limit for active but idle Terminal
Services sessions" to 1 min. I force the group policy update then
log into the Terminal Server and idle for 5 min. It never
disconnects.

What am I doing wrong?

Thanks
 
Re: Terminal Server Group Policy Question

Can you check first if the policy is applied, by running GPResult at the
command prompt?
Anthony,
http://www.airdesk.co.uk


"theGerm" <jrmontg@gmail.com> wrote in message
news:2dd8fb80-a429-424c-b308-c85470f0f8d6@x41g2000hsb.googlegroups.com...
>I have a windows 2003 domain controller and a Windows 2003 Terminal
> Server.
>
> In a OU I have a Management Group Policy in which I configureed the
> computer configuration and the user coniguration areas dealing with
> terminal services.
>
> User Config > Admin Templates > Windows Components > Terminal Services
>> Sessions
> Computer Configuration > Admin Templates > Windows Components >
> Terminal Services > Sessions
>
> For testing I set the "Sets a time limit for active but idle Terminal
> Services sessions" to 1 min. I force the group policy update then
> log into the Terminal Server and idle for 5 min. It never
> disconnects.
>
> What am I doing wrong?
>
> Thanks
 
Re: Terminal Server Group Policy Question

theGerm <jrmontg@gmail.com> wrote:
> I have a windows 2003 domain controller and a Windows 2003 Terminal
> Server.
>
> In a OU I have a Management Group Policy in which I configureed the
> computer configuration and the user coniguration areas dealing with
> terminal services.
>
> User Config > Admin Templates > Windows Components > Terminal Services
>> Sessions
> Computer Configuration > Admin Templates > Windows Components >
> Terminal Services > Sessions
>
> For testing I set the "Sets a time limit for active but idle Terminal
> Services sessions" to 1 min. I force the group policy update then
> log into the Terminal Server and idle for 5 min. It never
> disconnects.
>
> What am I doing wrong?
>
> Thanks

You should run an rsop.msc and gpresult on the TS box while logged in as the
user - and this policy should have loopback processing enabled.

After you do that, I suggest you crosspost this question & the results
(don't multipost!) to microsoft.public.windows.terminal_services *and*
microsoft.public.windows.group.policy for the most expert help.
 
Re: Terminal Server Group Policy Question

Yes it is applied to my username:

Applied Group Policy Objects
-----------------------------
Management Group Policy *****
Default Domain Policy
Local Group Policy
 
Re: Terminal Server Group Policy Question

What value do you actually have in HKLM\SOFTWARE\Policies\Microsoft\Windows
NT\Terminal Services\MaxIdleTime?
Anthony,
http://www.airdesk.co.uk



"theGerm" <jrmontg@gmail.com> wrote in message
news:80795eb0-51d2-49b5-b416-043b7ae3ac7d@l64g2000hse.googlegroups.com...
> Yes it is applied to my username:
>
> Applied Group Policy Objects
> -----------------------------
> Management Group Policy *****
> Default Domain Policy
> Local Group Policy
 
Back
Top