Hi,
Does anyone know how I can set the Software Update Agent to bypass the proxy server when using ISA WPAD?
I have a problem where all of my clients' scan states are showing as "unknown", and all get the following errors in the logs:
<![LOG[Async searching of updates using WUAgent started.]LOG]!><time="15:44:05.341+000" date="10-06-2008" component="WUAHandler" context="" type="1" thread="1036" file="cwuahandler.cpp:587">
<![LOG[Async searching completed.]LOG]!><time="15:44:07.466+000" date="10-06-2008" component="WUAHandler" context="" type="1" thread="5696" file="cwuahandler.cpp:2099">
<![LOG[OnSearchComplete - Failed to end search job. Error = 0x80244021.]LOG]!><time="15:44:07.466+000" date="10-06-2008" component="WUAHandler" context="" type="3" thread="1036" file="cwuahandler.cpp:2966">
<![LOG[Scan failed with error = 0x80244021.]LOG]!><time="15:44:07.466+000" date="10-06-2008" component="WUAHandler" context="" type="3" thread="1036" file="cwuahandler.cpp:3223">
I have discovered this means that the agent is trying to use the proxy server to communicate with SCCM, ie to get to http://svsccm02.dbct.com.au/ClientWebService/client.asmx. We are using wpad with ISA 2006 so no doubt this is where it is pulling the proxy address from. By default, this address is blocked using the proxy; when I add it in the scan is successful.
The thing is, our wpad script is set to go directly to all internal servers (bypass the proxy), and if I browse to that address on the clients it does indeed bypass the ISA server. I have tried a bunch of windows update agent commands (proxycfg -b, wuauclt.exe /forcedetect etc.) but I'm starting to come to the conclusion that the agent pays no attention to the Windows Update Agent settings. Detailed documentation on how the SCCM agent integrates with WU seems very scarce in general.
I don't really want to have to enable access via the proxy server. Any help with this would be much appreciated.
Regards,
Shaw