windows update cache

Hi,

I'm having a really hard time with the Windos updates. Is
there any product 
or way around the cache those updates? I know there are for
enterprises, 
but are there for ISPs?


-- 
Miguel Mata
Gerente de Operaciones
Intercom El Salvador
mmataintercom.com.sv
voz: ++(503) 2278-5068
fax: ++(503) 2265-7024

"Intercom, sus Telecomunicaciones en buenas
manos"

> I'm having a really hard time with the Windos updates.
Is 
> there any product or way around the cache those
updates? I 
> know there are for enterprises, but are there for
ISPs?

Windows Updates are not really cacheable because MS changes
the contents
of their patches without changing the names of the files.
You can read
more here:

http://usefulthings.org.uk/www/caching-windowsupdat
e-in-squid

--Michael Dillon

Windows Software Update Services doesn't require the
end-user to be part
of a domain to get updates. You just need to define the WSUS
server as
the source for updates by changing a few registry entries
and make sure
the server is available via HTTP or HTTPS to your customers.
You can
read more at Microsoft's site.

Also, WSUS is free to run on any Windows server.



-joe

-------------------------------------------------
Joseph A. Johnson, MCSE, MCP, A+
Chief Technology Officer
Riverside Consulting Group, Ltd.

Email:   joeriversidecg.com
Web:     www.riversidecg.com
Phone:   312-231-8315


-----Original Message-----
From: owner-nanogmerit.edu [mailto:owner-nanogmerit.edu] On Behalf Of
Miguel Mata
Sent: Friday, September 28, 2007 9:53 AM
To: nanognanog.org
Subject: windows update cache


Hi,

I'm having a really hard time with the Windos updates. Is
there any
product 
or way around the cache those updates? I know there are for
enterprises,

but are there for ISPs?


-- 
Miguel Mata
Gerente de Operaciones
Intercom El Salvador
mmataintercom.com.sv
voz: ++(503) 2278-5068
fax: ++(503) 2265-7024

"Intercom, sus Telecomunicaciones en buenas
manos"

On Fri, Sep 28, 2007, Joe Johnson wrote:
> 
> Windows Software Update Services doesn't require the
end-user to be part
> of a domain to get updates. You just need to define the
WSUS server as
> the source for updates by changing a few registry
entries and make sure
> the server is available via HTTP or HTTPS to your
customers. You can
> read more at Microsoft's site.
> 
> Also, WSUS is free to run on any Windows server.

Great if you're running a windows IT type LAN; crap if
you're running an
ISP!

http://www.advproxy.net/
- its a Squid distribution for ipcop with an
optional Windows update cache redirector. I don't know how
well it'll scale
but it seems to work fine for small home/office
environments.

You can always get an Akamai cluster  That'll
serve windows updates
to you, amongst other things.

That said, I know how to make Squid properly cache stuff
like Windows Updates;
I just need some spare time over the new year to code it up.
Sponsorship to
make it happen sooner is definitely welcome.




Adrian
(One of the remaining public Squid developers.)

Adrian Chadd wrote:
> On Fri, Sep 28, 2007, Joe Johnson wrote:
>> Windows Software Update Services doesn't require
the end-user to be part
>> of a domain to get updates. You just need to define
the WSUS server as
>> the source for updates by changing a few registry
entries and make sure
>> the server is available via HTTP or HTTPS to your
customers. You can
>> read more at Microsoft's site.
>>
>> Also, WSUS is free to run on any Windows server.
> 
> Great if you're running a windows IT type LAN; crap if
you're running an
> ISP!
> 

Why? It talks TCP/IP.

~Seth

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?



Adrian

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_MACHINESOFTWAREMicrosoftWindowsWindowsUpdate

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

On Fri, 28 Sep 2007, Seth Mattinen wrote:

>
> Adrian Chadd wrote:
>> On Fri, Sep 28, 2007, Joe Johnson wrote:
>>> Windows Software Update Services doesn't
require the end-user to be part
>>> of a domain to get updates. You just need to
define the WSUS server as
>>> the source for updates by changing a few
registry entries and make sure
>>> the server is available via HTTP or HTTPS to
your customers. You can
>>> read more at Microsoft's site.
>>> 
>>> Also, WSUS is free to run on any Windows
server.
>> 
>> Great if you're running a windows IT type LAN; crap
if you're running an
>> ISP!
>
> Why? It talks TCP/IP.

This seems like a question of how much control ISPs have
over customers' 
PCs at this point.  In my day (when we had to push packets
up hill through 
28.8 kbps modems, both ways...), we used to send out CDs to
all our 
customers that would install web browsers and mail clients,
and change the 
computers' dial-up networking settings to match our network.
 Changing 
some registry strings for Windows Update would have been
trivial.

The ISPs I've dealt with recently as an end user tend to
just send out a 
cable or DSL to ethernet bridge and let DHCP do the rest. 
This is 
progress, as it means devices can move from place to place
and just work, 
but I don't think it provides a way to change registry
settings.

-Steve

Steve Gibbard wrote:
> On Fri, 28 Sep 2007, Seth Mattinen wrote:
> 
>>
>> Adrian Chadd wrote:
>>> On Fri, Sep 28, 2007, Joe Johnson wrote:
>>>> Windows Software Update Services doesn't
require the end-user to be 
>>>> part
>>>> of a domain to get updates. You just need
to define the WSUS server as
>>>> the source for updates by changing a few
registry entries and make sure
>>>> the server is available via HTTP or HTTPS
to your customers. You can
>>>> read more at Microsoft's site.
>>>>
>>>> Also, WSUS is free to run on any Windows
server.
>>>
>>> Great if you're running a windows IT type LAN;
crap if you're running an
>>> ISP!
>>
>> Why? It talks TCP/IP.
> 
> This seems like a question of how much control ISPs
have over customers' 
> PCs at this point.  In my day (when we had to push
packets up hill 
> through 28.8 kbps modems, both ways...), we used to
send out CDs to all 
> our customers that would install web browsers and mail
clients, and 
> change the computers' dial-up networking settings to
match our network.  
> Changing some registry strings for Windows Update would
have been trivial.
> 
> The ISPs I've dealt with recently as an end user tend
to just send out a 
> cable or DSL to ethernet bridge and let DHCP do the
rest.  This is 
> progress, as it means devices can move from place to
place and just 
> work, but I don't think it provides a way to change
registry settings.
> 

One could try to transparently proxy requests to windows
update over to 
the WSUS server. No idea if that'll work though. I'm no
windows expert, 
nor was I trying to provide some total solution, I was just
trying to 
point out it uses TCP on port 8530 and one could try to use
that to 
their advantage.

~Seth

On Sep 28, 2007, at 1:05 PM, Steve Gibbard wrote:

>
> On Fri, 28 Sep 2007, Seth Mattinen wrote:
>
>>
>> Adrian Chadd wrote:
>>> On Fri, Sep 28, 2007, Joe Johnson wrote:
>>>> Windows Software Update Services doesn't
require the end-user to  
>>>> be part
>>>> of a domain to get updates. You just need
to define the WSUS  
>>>> server as
>>>> the source for updates by changing a few
registry entries and  
>>>> make sure
>>>> the server is available via HTTP or HTTPS
to your customers. You  
>>>> can
>>>> read more at Microsoft's site.
>>>> Also, WSUS is free to run on any Windows
server.
>>> Great if you're running a windows IT type LAN;
crap if you're  
>>> running an
>>> ISP!
>>
>> Why? It talks TCP/IP.
>
> This seems like a question of how much control ISPs
have over  
> customers' PCs at this point.  In my day (when we had
to push  
> packets up hill through 28.8 kbps modems, both
ways...), we used to  
> send out CDs to all our customers that would install
web browsers  
> and mail clients, and change the computers' dial-up
networking  
> settings to match our network.  Changing some registry
strings for  
> Windows Update would have been trivial.
>
> The ISPs I've dealt with recently as an end user tend
to just send  
> out a cable or DSL to ethernet bridge and let DHCP do
the rest.   
> This is progress, as it means devices can move from
place to place  
> and just work, but I don't think it provides a way to
change  
> registry settings.

And, even if it did, once the customer leaves and goes to
another ISP  
they would likely still be pointing at your server -- this
means that:
a: their windows updates would break or
b: you would carry on servicing them and paying for BW, etc

W

(Yes, yes, unless the new ISP gives them a CD that changes
the  
registry settings too...)

>
> -Steve
>

--
Hope is not a strategy.
       --  Ben Treynor, Google