Export (0) Print
Expand All

Using Automatic Proxy Configuration

Updated: April 8, 2009

Applies To: Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 Foundation, Windows Server 2008 R2, Windows Server 2012, Windows Vista

Conflicting or improperly configured proxy settings on user computers can restrict user access to external sites while the user is connected to a corporate network. By reconfiguring user proxy settings, you can ensure that the user has appropriate access to internal and external resources.

In order for you to use this feature, your network must include a proxy server.

In order to use automatic proxy configuration in a connection profile, you must create a plain text file that specifies the following values:

 

Key Value

[Automatic Proxy]

No value. Section header for automatic proxy settings.

[Manual Proxy]

No value. Section header for manual proxy settings.

AutoProxyEnable

0 = Automatic proxy detection is disabled.

1 = Automatic proxy detection is enabled.

AutoConfigScriptEnable

0 = Automatic proxy script will not be executed.

1 = Automatic proxy script will be executed.

AutoConfigScript

The URL that points to the automatic proxy script.

ProxyEnable

0 = Manual proxy detection is disabled.

1 = Manual proxy detection is enabled.

ProxyServer

The name and the port of the proxy server.

ProxyOverride

The Domain Name System (DNS) addresses, separated by semi-colons, that should not be passed on to the proxy server. You can use the value <local> to bypass the proxy server for local addresses. If you include this value, it should be the final value in the string.

The following is an example of a simple proxy text file for Awesome Computers, simpleproxy.txt:

[Automatic Proxy]
AutoProxyEnable=1
AutoConfigScriptEnable=1
AutoConfigScript=www.awesome.com/proxysettings.txt

[Manual Proxy]
ProxyEnable=0

You can configure far more complex proxy settings. In the following example, complexproxy.txt, automatic proxy detection is used where possible, and a manual proxy supports clients that cannot use automatic proxy detection. Different protocols use different proxy servers, and several addresses have been excluded from the proxy.

[Automatic Proxy]
AutoProxyEnable=1

[Manual Proxy]
ProxyEnable=1
ProxyServer=ftp=FTPProxyServer:2010;gopher=GopherProxyServer:1066;http=HTTPProxyServer:42;https=SecureProxyServer:1984;socks=SocksProxyServer:5150
ProxyOverride=DNSaddress1;DNSaddress2;<local>

For more information about proxy settings in Internet Explorer, refer to the Internet Explorer Administration Kit.

For more information about Connection Manager keys and values, see Advanced Customization.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft