SCCM Windows Updates Fault due to WPAD File
Posted on 2011-02-11
I have setup and ran for many months SCCM R2. We use this for Windows updates, future software rollouts and general hardware/software reporting.
Recently with the addition of a new Hardware Based Web Filtering system a WPAD setting has had to be put in place for our non domain clients to redirect them through the new filtering system.
This has somehow had a negative effect on my domain clients scanning for windows updates and reporting back to the SCCM Server. When I run the “Troubleshooting 3 - Computers failing with a specific scan error“ report all domain clients report back as Scan failed with an error code of -2145107941. Needless to say my compliance reports come back as unknown.
If we remove/disable the WPAD then all domain clients scan without fault. I can then update all clients. We tested this a few times to be sure.
The WPAD file has to stay to accommodate the non domain clients.
Does anyone have an idea how I can get round this issue? I don’t want to move away from SCCM windows updating as it’s worked flawlessly until now.