<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Caching windowsupdate in squid</title> <atom:link href="http://usefulthings.org.uk/2004/01/caching-windowsupdate-in-squid/feed/" rel="self" type="application/rss+xml" /><link>http://usefulthings.org.uk/2004/01/caching-windowsupdate-in-squid/</link> <description></description> <lastBuildDate>Thu, 10 May 2012 07:49:28 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.2</generator> <item><title>By: Seun Osewa</title><link>http://usefulthings.org.uk/2004/01/caching-windowsupdate-in-squid/comment-page-1/#comment-44</link> <dc:creator>Seun Osewa</dc:creator> <pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate> <guid
isPermaLink="false">http://usefulthings.org.uk/?p=58#comment-44</guid> <description>Hi.  My testing with SquidNT shows Windows Updates apparently being cached without that setting.  I&#039;d like to know what one could do when some of the downloads are corrupted.</description> <content:encoded><![CDATA[<p>Hi.  My testing with SquidNT shows Windows Updates apparently being cached without that setting.  I&#8217;d like to know what one could do when some of the downloads are corrupted.</p> ]]></content:encoded> </item> <item><title>By: toby</title><link>http://usefulthings.org.uk/2004/01/caching-windowsupdate-in-squid/comment-page-1/#comment-45</link> <dc:creator>toby</dc:creator> <pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate> <guid
isPermaLink="false">http://usefulthings.org.uk/?p=58#comment-45</guid> <description>The main problem (that I have discovered) is that AFAICT Microsoft produce patched patches which have the same name which means that when the patches are updated the caching proxy server uses the old one in preference to the one that windowsupdate expects.
The best solution is the have an up-to-date slipstreamed distribution which sits on a network and that you install using either a bootable pen drive or FDD. This also means you can automate the install and control what goes on the machine. I think that you can also add drivers to the install as well so it makes life  a lot easier for a little bit of work up front.</description> <content:encoded><![CDATA[<p>The main problem (that I have discovered) is that AFAICT Microsoft produce patched patches which have the same name which means that when the patches are updated the caching proxy server uses the old one in preference to the one that windowsupdate expects.</p><p>The best solution is the have an up-to-date slipstreamed distribution which sits on a network and that you install using either a bootable pen drive or FDD. This also means you can automate the install and control what goes on the machine. I think that you can also add drivers to the install as well so it makes life  a lot easier for a little bit of work up front.</p> ]]></content:encoded> </item> <item><title>By: Ozan</title><link>http://usefulthings.org.uk/2004/01/caching-windowsupdate-in-squid/comment-page-1/#comment-46</link> <dc:creator>Ozan</dc:creator> <pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate> <guid
isPermaLink="false">http://usefulthings.org.uk/?p=58#comment-46</guid> <description>You could use http://www.microsoft.com/windows2000/windowsupdate/sus/ if you have a spare W&#304;ndows 2000 -&gt; 2003 server available for Microsoft&#039;s solution to the problem. Or http://www.glob.com.au/windowsupdate_cache/ has a redirector that can cache windowsupdate files. Either solution is not perfect, I&#039;ve tried them both.</description> <content:encoded><![CDATA[<p>You could use <a
href="http://www.microsoft.com/windows2000/windowsupdate/sus/" rel="nofollow">http://www.microsoft.com/windows2000/windowsupdate/sus/</a> if you have a spare W&#304;ndows 2000 -> 2003 server available for Microsoft&#8217;s solution to the problem. Or <a
href="http://www.glob.com.au/windowsupdate_cache/" rel="nofollow">http://www.glob.com.au/windowsupdate_cache/</a> has a redirector that can cache windowsupdate files. Either solution is not perfect, I&#8217;ve tried them both.</p> ]]></content:encoded> </item> </channel> </rss>
