Several months ago, I released a tool (the ) to generate a Proxy Automatic Configuration file that can be used to bypass local proxy servers for Office 365 services. I also wrote a blog () on using the tool. I've received a lot of personal feedback on it, and wanted to expand on how to use the configuration file in production to manage desktops. As I stated in my blog posting, bypassing the proxy requires two elements: - A list of URLs/domains that the browser knows to not send to the proxy environment - Firewall access rules configured to allow outbound access to the IP addresses corresponding to the domains found in the proxy bypass list That sounds well and good; so how do you configure your desktop environment to take advantage of this proxy automatic configuration file? There are two basic ways that this can be accomplished.

Most organizations will want to bypass their proxy server for local. Proxy Auto-Configuration Script to Bypass Proxy. Example PAC File. The basic for all. Download Aiwa Nsx S202 Manual Dexterity. Proxy bypass rules for private IP networks, internal hostnames, and hosts with.local domain extension. Apr 06, 2016. File that can be used to bypass local proxy. Deploying the Office 365 Proxy PAC. The PAC and WPAD.DAT files in the IP address. Example PAC File. The basic for all. Proxy bypass rules for private IP networks, internal hostnames, and hosts with.local domain extension.

- GPO that specifies the location of the.PAC file (which will typically only be useful for Internet Explorer or Edge browsers, unless separate administrative templates have been configured for Firefox or Chome - WPAD (Web Proxy Autodiscover Protocol Web Server First things first. In order for your clients to pick up a configuration file at all, there has to be a web server hosting the file. The configuration is relatively straightforward if you're setting up IIS.

• Install IIS. Yes, it's pretty easy.

If you've never done it before, here's the cliff notes on the various IIS versions. • IIS 7.x (Windows 2008 R2) - • IIS 8.x (Windows 2012/R2) - • Configure the appropriate MIME types (at this point, we're going to configure a MIME type for both WPAD.DAT and the proxyautoconfig.pac file--it's the same file, but delivered via different methods.

Scarbee Rickenbacker Bass Rapidshare Premium. • Launch an elevated PowerShell prompt.