How can I automatically handle different proxy settings for travelling users

I have several sites with different proxy server solutions, and some sites is using proxy. Some sites have their own proxy servers, other have governmental proxy servers.

Example of proxy settings below.
HTTP: 8080
Auto-config URL (.INS file)

Proxy settings is today deployed with policies in a geographical divided OU tree.

We are running Active Directory on Windows 2003 (root and sub common domain), DHCP on Windows server 2003, Clients are Windows 2003. We are using Checkpoint Firewall and secure Client VPN client, possibly upgrading it to Enpoint Security.

My challenge is that there is a lot of travelling users. When visiting a site there is currently only two options to deploy proxy settings.
1. Change the proxy settings on the client manually.
2. System administrator moves their account to the corresponding OU.
None of the above options is optimal. An option is of course to use site policies instead, but we have not done this, because when a user is leaving a site he might connect at another site (eg. airport, home office). When not getting an updated AD policy applied, the proxy settings remain set from the last time receiving an AD policy.

I am aware of the DHCP option 252, but have understood it cannot deploy direct proxy settings, like "HTTP: 8080", only Config URL's.

My question is how I can automatically deploy proxy settings for users wherever they are or at least on sites under my control, and with a clean proxy setting on sites not under my control.

PS! A possible way could be to create a config URL for eg. " HTTP: 8080", but don't know how and how to deploy it.

I am not familiar with proxy servers at all, so please bare over with me.

Questions to improve my questions is highly appreciated. Thanks in advance.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Create a fle names proxy.pac and put it in \\
Then create a logon script that runs at login to copy this file to the local harddrive (ex. c:\windows\proxy.pac)
then use group policy to force the browser to use automatic configuration script witht he following value without quotes "file://c:/windows/proxy.pac"

the script can be used to use different proxies or none at all depending on several factors including the pc's local ip address. So if the pc is on your network it would use your proxy and in not it would use no proxy. below is a sample of a proxy.pac file.

//modified 07/31/08 11:32 ch 
function FindProxyForURL(url, host)
var myip=myIpAddress();
//exceptions to proxy, traffic to local hosts is direct,
//also sites that have trouble with squid is direct
if (shExpMatch(url, "**") ||
   shExpMatch(url, "**")  ||
   isInNet(host, "", "") ||
   isInNet(host, "", "") ||
   isInNet(host, "", ""))
		return "DIRECT";
else if (myip.substring(0,3)!=="10." && myip.substring(0,7)!=="172.19.")
		return "DIRECT";
//use proxy unless unreachable, go direct if proxy is unreachable
//return "DIRECT";
return "PROXY squid:3128; PROXY squidbak:3128; DIRECT";

Open in new window


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AlexWilhelmsenAuthor Commented:
Your solution is quite good, but it will require the logon script for distributing the proxy.pac file. For visitiors I still would have to do it manually. My main question was for a fully autmated solution. Your script is quite neat so I will split some points for you.

The solution was quite easy when I understood that a proxy.pac and a wpad.dat file is the same, The wpad.dat name is just to make the 252 option in DHCP work. I found the complete solution at this url.
Create a Group policy to change your Proxy settings to whatever is required. Apply this at site level in Gorup Policy Management. Use different GPOs for each site.
AlexWilhelmsenAuthor Commented:
Good solution but for travelling users this will be a problem, since the last policy/proxy settings will be fixed until next time you get a policy. So if you do a stop at eg. a hotel or an airport they settings will still be there, and stopping you form browsing the web.

I know preferences in Windows 2008 R2 can fix this. but the question is very old, and related to Windows 2003 and XP.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

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.