stebennettsjb
asked on
GP Problem with Proxy settings
Hi experts,
having some issues with GP at the moment we changed from a software firewall using Proxy server to a hardware one which didnt need any proxy settings.
So i gointo the default domain policy and change it from ticked Proxy settings and close and wait.. 4 days later and all the servers say the default domain policy is setting the proxy server to unticked. But if i use (Newly found) the RSoP and check a user out it says that that Proxy settings are set and that it getting it from the default domain policy. All computers have been restarted numberous times (As i say i changed the policy 4+ days ago) so i dont get why its still doing it..
Any suggestions..
Thanks
Stephen
having some issues with GP at the moment we changed from a software firewall using Proxy server to a hardware one which didnt need any proxy settings.
So i gointo the default domain policy and change it from ticked Proxy settings and close and wait.. 4 days later and all the servers say the default domain policy is setting the proxy server to unticked. But if i use (Newly found) the RSoP and check a user out it says that that Proxy settings are set and that it getting it from the default domain policy. All computers have been restarted numberous times (As i say i changed the policy 4+ days ago) so i dont get why its still doing it..
Any suggestions..
Thanks
Stephen
We had a similar situation:
I ended having to create a GPO that was imported.
1) Open Group Policy
2) Go to user configuration | Internet Explorer Maintenance | Connection Settings
3) Choose import ... from current machine. (make sure that you import the settings that you want)
4) (OPTIONAL ONLY), create a registry change push, we use Prism. Change the registry entries of:
HKCU\SW\MS\Windows\Current Version\In ternetSett ings\Proxy Enable = 0
HKLM\SW\MS\Windows\Current Version\In ternetSett ings\Proxy Enable = 0
I ended having to create a GPO that was imported.
1) Open Group Policy
2) Go to user configuration | Internet Explorer Maintenance | Connection Settings
3) Choose import ... from current machine. (make sure that you import the settings that you want)
4) (OPTIONAL ONLY), create a registry change push, we use Prism. Change the registry entries of:
HKCU\SW\MS\Windows\Current
HKLM\SW\MS\Windows\Current
ASKER
thanks for the info i will try them both out..
ASKER
OK heres the update
tried doing
gpupdate /flush
reboot
on all servers and then on all machines
no joy
ive done the dns /flushdns as well with no joy also..
not sure how this importing GPO works, am i importing on the client or the server?
Thanks for the info and any more ideas welcome..
tried doing
gpupdate /flush
reboot
on all servers and then on all machines
no joy
ive done the dns /flushdns as well with no joy also..
not sure how this importing GPO works, am i importing on the client or the server?
Thanks for the info and any more ideas welcome..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The situation I have seen is where previous technician's will set the proxy via a local GP rather than a domain GP. I can not explain why the domain does not override the local it there are no check marks set for static proxy, but they haven't in my worlds.
The only way I can explain that the process I outlined above is working, is because it is actually applying an imported setting rather than no setting. If that makes any sense at all.
The way to apply a registy setting it to either run it from a login script (not recommended)
or as a GP logon:
Part One (Create the reg file)
------ snip ------
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Softwar e\Microsof t\Windows\ CurrentVer sion\Inter net Settings]
"ProxyEnable"=dword:000000 00
"ProxyAddress"=""
"ProxyPort"=""
[HKEY_Local_Machine\Softwa re\Microso ft\Windows \CurrentVe rsion\Inte rnet Settings]
"ProxyEnable"=dword:000000 00
"ProxyAddress"=""
"ProxyPort"=""
------ snip ------
Part Two: (create new Domain Group Policy like before)
Instead of setting the IE settings do the following:
1) Edit the policy
2) Drill down to 'User Configuration'-'Windows Settings'-'Scripts (Logon/Logoff)
3) Double Click 'Logon'
4) Click Add | Click Browse | Copy files into the newly opened folder
5) Double Click or open new reg file
6) Click OK until you are all the way out
Again, test this on a small group prior to implementing across the network
The only way I can explain that the process I outlined above is working, is because it is actually applying an imported setting rather than no setting. If that makes any sense at all.
The way to apply a registy setting it to either run it from a login script (not recommended)
or as a GP logon:
Part One (Create the reg file)
------ snip ------
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Softwar
"ProxyEnable"=dword:000000
"ProxyAddress"=""
"ProxyPort"=""
[HKEY_Local_Machine\Softwa
"ProxyEnable"=dword:000000
"ProxyAddress"=""
"ProxyPort"=""
------ snip ------
Part Two: (create new Domain Group Policy like before)
Instead of setting the IE settings do the following:
1) Edit the policy
2) Drill down to 'User Configuration'-'Windows Settings'-'Scripts (Logon/Logoff)
3) Double Click 'Logon'
4) Click Add | Click Browse | Copy files into the newly opened folder
5) Double Click or open new reg file
6) Click OK until you are all the way out
Again, test this on a small group prior to implementing across the network
ASKER
well a solution has been found.. a wise man came over and toke a look.. and its working now.
He changed:
sysvol\gemdom.gem-a.local\ Policies\{ 31B2F340-0 16D-11D2-9 45F-00C04F B984F9}\US ER\Microso ft\IEAK\in stall.ins
from pointing to servers to this
[Branding]
NoLinks=1
GPVersion=6.0.6000.16414
NoFavorites=1
[DesktopObjects]
[Proxy]
Proxy_Enable=0
[URL]
AutoDetect=0
AutoConfig=0
Thankyou Miahmichno for the help :)
He changed:
sysvol\gemdom.gem-a.local\
from pointing to servers to this
[Branding]
NoLinks=1
GPVersion=6.0.6000.16414
NoFavorites=1
[DesktopObjects]
[Proxy]
Proxy_Enable=0
[URL]
AutoDetect=0
AutoConfig=0
Thankyou Miahmichno for the help :)
check to make sure that the client computers are getting the group policy settings, and not using cached credentials and settings.
could it be a dns issue ?
- ipconfig /flushdns
- ipconfig /registerdns
that's all i can think of right now.