Content Engine with Windows Update site

[jim.r.waller]

We are using a couple of CE's load balanced by a CSS for a proxy. Recently we have noticed that some users have been unable to use the proxy to download Critical Updates from Microsoft. When we turn the proxy off everything works fine. Has anyone ever seen this or have any ideas of what the problem might be?(ce7320-5.0.17)

[seilsz]

Can you provide some additional detail:

1. Where in the update process does it fail?

2. Does this apply to all users?

3. Is it only connections through one of the CE's?

Thanks,

Zach

[jim.r.waller]

Thanks,

1) It fails during the download of the patches(just sits at 0%)

2) Users at 3 specific sites seem to quit working after V4 to V5 update of Microsoft Update. Other sites setup the same(with Proxy pac from CE's) working ok.

Really strange if you take a non-working machine to a working site. It works fine...Sites are setup exactly the same.

3) It doesn't seem to matter which CE.

[seilsz]

There seems to be a host of issues when using a proxy with v5 of Windows Update:

http://communities2.microsoft.com/communities/newsgroups/en-us/default.aspx?query=proxy&dg=microsoft.public.windowsupdate&cat=en_US_56d1dd45-de9e-4fc5-9bc1-2d1d0de6daee〈=en&cr=US&pt=a5b74b1a-427e-4684-a270-294000352edb&catlist=93e29c6e-09cd-400c-8ac1...

It looks like v5 tries to bypass the proxy configuration and connect directly to the Microsoft update site(s).

So ... without the proxy involved, you may want to start by checking for routing and/or access control issues. A sniffer trace in front of the client would definately be of some use.

~Zach

[jim.r.waller]

The issue was that v5 seems to ignore the proxy settings for Windows Update site. Microsoft provided a fix and now all is well. Thanks for the help.