Group Policy won't apply unless member of Local Admin

We are setting up a new terminal server and have a GP that applies to all our
terminals server users. The policy works great on our old servers but isn’t
being applied to our new server unless I set them up as a local administrator
on that terminal server. Any help would be appreciated.

 

KO <KO@discussions.microsoft.com> wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> We are setting up a new terminal server and have a GP that applies to
> all our terminals server users. The policy works great on our old
> servers but isn't being applied to our new server unless I set them
> up as a local administrator on that terminal server. Any help would
> be appreciated.<!--colorc--><!--/colorc-->

More info needed. What's different about this TS box than the others? Have
you got the policy linked to the correct OU (and is the TS box in the
correct OU)? What do the GPOs do?

 

"Lanwench [MVP - Exchange]" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> KO <KO@discussions.microsoft.com> wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > We are setting up a new terminal server and have a GP that applies to
> > all our terminals server users. The policy works great on our old
> > servers but isn't being applied to our new server unless I set them
> > up as a local administrator on that terminal server. Any help would
> > be appreciated.<!--colorc--><!--/colorc-->
>
> More info needed. What's different about this TS box than the others? Have
> you got the policy linked to the correct OU (and is the TS box in the
> correct OU)? What do the GPOs do?
> <!--colorc--><!--/colorc-->
This is a brand new install. All Windows 2003 servers. All computers are
in the same OU. The GPO locks down the terminal server like in Q278295.

 

KO <KO@discussions.microsoft.com> wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> "Lanwench [MVP - Exchange]" wrote:
><!--coloro:green--><span style="color:green <!--/coloro-->
>> KO <KO@discussions.microsoft.com> wrote:<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> We are setting up a new terminal server and have a GP that applies
>>> to all our terminals server users. The policy works great on our
>>> old servers but isn't being applied to our new server unless I set
>>> them up as a local administrator on that terminal server. Any help
>>> would be appreciated.<!--colorc--><!--/colorc-->
>>
>> More info needed. What's different about this TS box than the
>> others? Have you got the policy linked to the correct OU (and is the
>> TS box in the correct OU)? What do the GPOs do?
>><!--colorc--><!--/colorc-->
> This is a brand new install. All Windows 2003 servers. All
> computers are in the same OU. The GPO locks down the terminal server
> like in Q278295.<!--colorc--><!--/colorc-->

Run an rsop.msc and check for errors as well as looking in the event logs.

 

It turned out to be a problem with a mandatory roaming profile on that server.

Thanks for your sugestions.


"Lanwench [MVP - Exchange]" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> KO <KO@discussions.microsoft.com> wrote:<!--coloro:green--><span style="color:green <!--/coloro-->
> > "Lanwench [MVP - Exchange]" wrote:
> ><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >> KO <KO@discussions.microsoft.com> wrote:
> >>> We are setting up a new terminal server and have a GP that applies
> >>> to all our terminals server users. The policy works great on our
> >>> old servers but isn't being applied to our new server unless I set
> >>> them up as a local administrator on that terminal server. Any help
> >>> would be appreciated.
> >>
> >> More info needed. What's different about this TS box than the
> >> others? Have you got the policy linked to the correct OU (and is the
> >> TS box in the correct OU)? What do the GPOs do?
> >><!--colorc--><!--/colorc-->
> > This is a brand new install. All Windows 2003 servers. All
> > computers are in the same OU. The GPO locks down the terminal server
> > like in Q278295.<!--colorc--><!--/colorc-->
>
> Run an rsop.msc and check for errors as well as looking in the event logs.
>
>
> <!--colorc--><!--/colorc-->

 

KO <KO@discussions.microsoft.com> wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> It turned out to be a problem with a mandatory roaming profile on
> that server.
>
> Thanks for your sugestions.<!--colorc--><!--/colorc-->

Glad you found it - thanks for posting back.<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
>
> "Lanwench [MVP - Exchange]" wrote:
><!--coloro:green--><span style="color:green <!--/coloro-->
>> KO <KO@discussions.microsoft.com> wrote:<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>> KO <KO@discussions.microsoft.com> wrote:
>>>>> We are setting up a new terminal server and have a GP that applies
>>>>> to all our terminals server users. The policy works great on our
>>>>> old servers but isn't being applied to our new server unless I set
>>>>> them up as a local administrator on that terminal server. Any
>>>>> help would be appreciated.
>>>>
>>>> More info needed. What's different about this TS box than the
>>>> others? Have you got the policy linked to the correct OU (and is
>>>> the TS box in the correct OU)? What do the GPOs do?
>>>>
>>> This is a brand new install. All Windows 2003 servers. All
>>> computers are in the same OU. The GPO locks down the terminal
>>> server like in Q278295.<!--colorc--><!--/colorc-->
>>
>> Run an rsop.msc and check for errors as well as looking in the event
>> logs.<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->