80072F78 MS/Windows Update-revisited

[pmueller]

This thread from October seemed to die out without a resolution documented on this forum. I am also experiencing this error for Windows XP update and would like to know if it was identified and if so, is there a workaround/fix available? I can add that the problem has affected us in October and November for the updates. We also updated to the latest build of Wingate during that time frame. TIA.

[Nev]

This thread from October seemed to die out without a resolution documented on this forum. I am also experiencing this error for Windows XP update and would like to know if it was identified and if so, is there a workaround/fix available? I can add that the problem has affected us in October and November for the updates. We also updated to the latest build of Wingate during that time frame. TIA.

Hi,

Now I don't use Windows Update but WSUS is similar albeit stored locally.

Have read about this fault, what seemed necessary was to point it at a proxy script / wpad style served to the pc either by a central shared directory or better still by webserver / IIS.

Here is part of a proxy auto detect script which could work. Am not sure of the url[s] needed as an exception [where it says http://windowsupdate.com*] and you may have to add more to make it work, plus adjust the ip / port to suit!

=================================

function FindProxyForURL(url, host)
{
// variable strings to return
var proxy_yes = "PROXY 192.168.0.1:80";
var proxy_no = "DIRECT";
if (shExpMatch(url, "http://windowsupdate.com*")) { return proxy_no; }
// Proxy anything else
return proxy_yes;
}

=================================

This could allow the feature to NAT<->MSUpdate perhaps.

Report back, I'd be interested if this fixes. ;-)

There is also some MS-KB articles on adjusting the Windows Update to suit clients behind a proxy, where I use Group Policy.