Hi
I'll try to explain this as clear as I can!
We push our proxy settings at the domain level via a GPO which is applied to a specific AD group, all is working well. The GPO appears right at the top of the list of priorities, i.e. it has a link order of 1.
We want to change this and push the Proxy settings at the site level, however when we create a new GPO here and remove the existing one, no proxy settings are set.
If I create another GPO to push proxy settings at the domain level, it too also does not work, no Proxy settings are defined on the client.
However, if I move this new GPO up to the top of the list of priorities, the proxy settings work.
I've moved it down one by one and found out that our Default Domain Policy is the policy that appears to be blanking out the Proxy Settings.
Upon opening the Default Domain Policy, under Proxy Settings, there is no tick to define a proxy, but there is a servername and port, although they are greyed out and inaccessible.
I enabled the proxy, deleted those greyed out text entries, unticked proxy and saved the GPO, but the problem persists.
It appears our Default Domain Policy has in it some errant entries regarding Proxy Settings that are overriding any proxy settings that are applied before it.
So therefore as I see it, we need to either;
- remove these errant proxy entries in the default domain policy, though I cannot see a way of doing that as the GPO does not effectively
have any proxy settings defined in the GPMC
- force the GPO that is at the site level to have priority over the Default Domain Policy
Can anyone advise?? I quickly tried setting the GPO to "Enforced" tonight but it didn't seem to make any difference when I ran the GPO modeller.
Thanks
Nick