Jump to content
|Topic||Stats||Last action by|
|Civilization: Beyond Earth||
|Felicia Day writes post about #GamerGate, gets doxxed||
|Forza Horizon 2||
|11 yo Boy (Legally) Hunts and Kills Rare Deer, His Prize? A Facebook Flame War.||
Posted 23 November 2012 - 13:53
Posted 23 November 2012 - 16:54
Posted 23 November 2012 - 17:20
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.
here is a good ref to get you started using a pac file
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.
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.