Re: Windows Update v5 issues and workaround
From: Slava (Slava_at_discussions.microsoft.com)
Date: 02/02/05
- Next message: Phillip Windell: "Re: Windows Update v5 issues and workaround"
- Previous message: Phillip Windell: "Re: Windows Update v5 issues and workaround"
- Maybe in reply to: Phillip Windell: "Re: Windows Update v5 issues and workaround"
- Next in thread: Phillip Windell: "Re: Windows Update v5 issues and workaround"
- Reply: Phillip Windell: "Re: Windows Update v5 issues and workaround"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 2 Feb 2005 03:01:04 -0800
Temporary work around. I have looked ISA2004 logs and found out, that WU
client goes to strange addresses (64.4.21.92, 207.46.157.93 and so on). I
think, that it received them from WU Server. I have created ComputerSet with
these addresses and added to Destination in WU Rule. It's working.
Unfortunately, these IP addresses can exchange in future (I think).
"Phillip Windell" wrote:
> The proper way to do this is with SUS anyway. Downloading the same patches
> repeatedly for every Client is silly and destroys your bandwidth,...not to
> mention you are putting the task of keeping the machines up to date in the
> hands of the users.
>
> SUS (Software Update Service) downloads the patches only *once* and then
> ditributes the patches to the clients. It works perfectly fine from behind
> any version of ISA, other proxys, and other firewall devices.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>
- Next message: Phillip Windell: "Re: Windows Update v5 issues and workaround"
- Previous message: Phillip Windell: "Re: Windows Update v5 issues and workaround"
- Maybe in reply to: Phillip Windell: "Re: Windows Update v5 issues and workaround"
- Next in thread: Phillip Windell: "Re: Windows Update v5 issues and workaround"
- Reply: Phillip Windell: "Re: Windows Update v5 issues and workaround"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|