Group policy - domain policies appearing last then first in precedence

We run 2003 terminal servers with 2003 AD and use computer GPOs but recently we needed to split users into two OUs - one OU will use a proxy via a user GPO and the other group won't use the proxy via a different GPO.  The relevant user GPO will be merged with the computer GPOs via loopback.

The particular user GPO to apply the proxy is not working.  When I run rsop.msc and check the precedence for the proxy settings, a couple of domain policies are at the top with the proxy "<disabled>".  But those domain policies don't even have any proxy settings configured (enabled or disabled).  Plus, they appear at the bottom of the precedence AND at the top.  I thought GPOs were applied in this order: local, site, domain, OU.  

So how can the proxy be disabled when the GPO settings aren't even configured in the domain GPOs and why are the domain GPOs at the very top of the precedence level?  It must be something I've missed!
lrkwalkersAsked:
Who is Participating?
 
lrkwalkersAuthor Commented:
This has been resolved by the IT company we outsource work to.

I will get more info.

0
 
schristeCommented:
I'd review this site: http://technet.microsoft.com/en-us/library/cc778890(WS.10).aspx

The exceptions to the precedence might be what is tripping you up.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.