Regarding Enabling or Disabling Automatic Windows Update:

Automatic Windows Update silently does not update if you have a non-transparent web proxy between you and the Windows Update site. This is because AWU does not take account of any proxy settings which may be required, so it fails to connect to the update server. It doesn't log the failed attempt.

Running 'Windows Update' manually works because it runs within IE, and hence uses IE's proxy settings.

The only workaround I am aware of is to install Software Update Services on a machine which can be accessed without going through a proxy (e.g a server on the local network). SUS allows configuration of proxy settings for its own use.

[Reply or follow-up to this message]

Just Curious, If you update one computer on a network, can you update another computer without downloading the updates again?


On Thursday, November 27, 2003 at 4:25 am, msec wrote:
>Regarding Enabling
>or Disabling Automatic Windows Update:
>
>

Automatic Windows Update silently does not update if you have a non-transparent
>web proxy between you and the Windows Update site. This is because AWU does not take
>account of any proxy settings which may be required, so it fails to connect to the
>update server. It doesn't log the failed attempt.

Running 'Windows Update' manually works because it runs within IE, and hence uses
>IE's proxy settings.

The only workaround I am aware of is to install Software Update Services on a
>machine which can be accessed without going through a proxy (e.g a server on the
>local network). SUS allows configuration of proxy settings for its own use.

[Reply or follow-up to this message]

That's exactly the problem on the network I manage, and SUS worked perfectly for 
us.






On Thursday, November 27, 2003 at 4:25 am, msec wrote:
>Regarding Enabling 
>or Disabling Automatic Windows Update:
>
>
Automatic Windows Update silently does not update if you have a non-transparent 
>web proxy between you and the Windows Update site. This is because AWU does not 
take 
>account of any proxy settings which may be required, so it fails to connect to the 
>update server. It doesn't log the failed attempt.
>
Running 'Windows Update' manually works because it runs within IE, and hence 
uses 
>IE's proxy settings.
>
The only workaround I am aware of is to install Software Update Services on a 
>machine which can be accessed without going through a proxy (e.g a server on the 
>local network). SUS allows configuration of proxy settings for its own use.
>

[Reply or follow-up to this message]

On Thursday, November 27, 2003 at 5:41 am, Rod wrote:
>Just Curious, If you update one computer on a network, can you update another computer
>without downloading the updates again? The short answer seems to be 'not easily'. I experimented with this before hitting on SUS, and there are a number of 'gotchas'. Using Windows Catalog seems to be the 'approved' manual method, but it's not easy to work out which patches you really need, and the patches you do download are generally bigger than you'd download for a specific Windows Update. I'm not a guru in this area, though - maybe someone else can put us both straight. /msec

[Reply or follow-up to this message]

On Thursday, November 27, 2003 at 4:25 am, I wrote:

>The only workaround I am aware of is to install Software Update Services on a
>machine which can be accessed without going through a proxy (e.g a server on the
>local network). SUS allows configuration of proxy settings for its own use.

I've just realised there's another potential workaround, which is to install a *transparent* web proxy between you and the upstream non-transparent proxy.

Of course, the new proxy needs to understand about non-transparent proxies.

[Reply or follow-up to this message]

There is an article in a german magazine. It claims, that a policy edit or registry hack is possible to allow a proxy to be used as system account (which is, what the service is running at). Go for ftp://ftp.heise.de/pub/ct/listings/0323-196.zip The reg file is for Windows XP Home (D). The article is in c't 2003, 23, p.196

[Reply or follow-up to this message]

Ok I found how to correct for my office (except we always bypass the corporate proxy server)

Add the following to the file c:\Windows\system32\drivers\ets\hosts.

127.0.0.1 wpad.[Hostname]
127.0.0.1 wpad.[hostname minus 1st dot]
127.0.0.1 wpad.[hostname minus 2nd dot]

For example
127.0.0.1 wpad.auto.cs.microsoft.com
127.0.0.1 wpad.cs.microsoft.com
127.0.0.1 wpad.microsoft.com

Then run the following from a command prompt
net stop wuauserv
net start wuauserv

hope it helps.
- Phillip


On Thursday, November 27, 2003 at 4:25 am, msec wrote:
>Regarding Enabling
>or Disabling Automatic Windows Update:
>
>

Automatic Windows Update silently does not update if you have a non-transparent
>web proxy between you and the Windows Update site. This is because AWU does not take
>account of any proxy settings which may be required, so it fails to connect to the
>update server. It doesn't log the failed attempt.

Running 'Windows Update' manually works because it runs within IE, and hence uses
>IE's proxy settings.

The only workaround I am aware of is to install Software Update Services on a
>machine which can be accessed without going through a proxy (e.g a server on the
>local network). SUS allows configuration of proxy settings for its own use.

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum