[99573] in North American Network Operators' Group
Re: windows update cache
daemon@ATHENA.MIT.EDU (Forrest)
Fri Sep 28 13:49:59 2007
Date: Fri, 28 Sep 2007 12:19:09 -0500 (CDT)
From: Forrest <forrest@almighty.c64.org>
To: Seth Mattinen <sethm@rollernet.us>
cc: nanog@nanog.org
In-Reply-To: <46FD31CF.3020804@rollernet.us>
Errors-To: owner-nanog@merit.edu
On Fri, 28 Sep 2007, Seth Mattinen wrote:
>
> Adrian Chadd wrote:
> > On Fri, Sep 28, 2007, Seth Mattinen wrote:
> >
> >>> Great if you're running a windows IT type LAN; crap if you're running an
> >>> ISP!
> >> Why? It talks TCP/IP.
> >
> > How's it find the WSUS server again?
> >
>
> Key Name:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\WindowsUpdate
>
> Value 0
> Name: WUServer
> Type: REG_SZ
> Data: http://secret.server:8530
>
> Value 1
> Name: WUStatusServer
> Type: REG_SZ
> Data: http://secret.server:8530
>
>
> Works for me at $dayjob without AD and I don't need to play with weird
> solutions. (Disclaimer: I am not a windows expert, it's my weak point
> actually, so I have no idea if this is portable, I'm just saying it uses
> standard TCP/IP to talk to WSUS.)
>
> ~Seth
>
To make it work you'd have to get people to change the registry settings
on their computer to use your WSUS server, which can be done. But what do
you do with them after they've cancelled service with you and moved to
some other ISP? Either they end up with a Windows Update that doesn't
function anymore, or they end up using your bandwidth for the rest of
their computer's life to get their updates.
Perhaps it could be done by setting up a windowsupdate.com zone on your
own DNS servers that your customers use and point all of the DNS entries
to your own WSUS server, but I'm sure that comes with it's own set of
problems as well.....
Forrest
