WPAD and Proxy Auth Cause Exchange HCW to Fail
A recent conversation with a colleague reminded me of an issue I’ve faced a number of times (and forgotten to blog about) when running the Exchange Hybrid Configuration Wizard (HCW) on Exchange 2010 or 2013 in an environment where Web Proxy Autodiscovery Protocol (WPAD) is used.
The Problem
The most common scenario where I’ve seen this come into play is along the lines of this:
- WPAD is used to distribute Proxy.PAC to client machines
- Customer permits direct connection from Exchange servers to Internet
- From an elevated command prompt, run “netsh winhttp reset proxy” to ensure a direct connection
- Change Internet Options settings from “Automatically detect settings” to “Disabled”
- Browse to a site restricted by the proxy to confirm proxy bypass is working
- Can connect to Exchange Online using Remote PowerShell
- Run the HCW but it fails with the following error in the logs:
ERROR : System.Management.Automation.RemoteException: