Jump to content

Question

Posted

Im having an issue with windows proxy configuration, Normally I used the registry keys in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings ProxyServer ProxyOverride Proxy Enable etc to enable the proxy for everything but WSUS and my local adobe update server and I had no issues with wsus however after reading that the windows store doesn't use these settings

[url="http://tmgblog.richardhicks.com/2012/11/15/windows-8-modern-ui-apps-and-forefront-tmg-2010/"]http://tmgblog.richardhicks.com/2012/11/15/windows-8-modern-ui-apps-and-forefront-tmg-2010/[/url] (explaining the failed downloads I was having due to malware inspection)

I deployed a logon script to also include these applications with winhttp

netsh winhttp set proxy proxy-server=

Share this post


Link to post
Share on other sites

3 answers to this question

  • 0

Posted

Why don't you just use a pac file for your proxy settings on your clients - then the only thing you have to hand out to clients via script or group policy is the location of the pac file. You can then do whatever you want with bypasses, using lots of different if's and else's -- you can get as fancy as you need to for bypass, use different proxy, etc.. etc..

And just need to update the pac file for all clients to get the changes - no need to rerun a login script or update group policy on any changes, etc.

[url="http://en.wikipedia.org/wiki/Proxy_auto-config"]http://en.wikipedia....oxy_auto-config[/url]

here is a good ref to get you started using a pac file

[url="http://www.proxypacfiles.com/proxypac/"]http://www.proxypacfiles.com/proxypac/[/url]

Another nice thing about use of this is most browsers are set by default for autodect, so will use WPAD to find the location of said pac file and then use it.

http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol

This way guests or non AD members would also get your proxy info as long as they are setup for default auto discovery. Even if using a different browser vs just IE, etc.
1 person likes this

Share this post


Link to post
Share on other sites
  • 0

Posted

Nice work Budman..

Share this post


Link to post
Share on other sites
  • 0

Posted

[quote name='BudMan' timestamp='1353689696' post='595344606']
Why don't you just use a pac file for your proxy settings on your clients - then the only thing you have to hand out to clients via script or group policy is the location of the pac file. You can then do whatever you want with bypasses, using lots of different if's and else's -- you can get as fancy as you need to for bypass, use different proxy, etc.. etc..

And just need to update the pac file for all clients to get the changes - no need to rerun a login script or update group policy on any changes, etc.

[url="http://en.wikipedia.org/wiki/Proxy_auto-config"]http://en.wikipedia....oxy_auto-config[/url]

here is a good ref to get you started using a pac file

[url="http://www.proxypacfiles.com/proxypac/"]http://www.proxypacfiles.com/proxypac/[/url]

Another nice thing about use of this is most browsers are set by default for autodect, so will use WPAD to find the location of said pac file and then use it.

[url="http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol"]http://en.wikipedia....covery_Protocol[/url]

This way guests or non AD members would also get your proxy info as long as they are setup for default auto discovery. Even if using a different browser vs just IE, etc.
[/quote]

Ill try that now, Got one server reporting the correct address by removing the :8531 in ie settings

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.