What I mean by this is that M$ has taken to releasing their patches on a set date to make it more predicatable for their customers. This mean M$ gets DoS'ed at a particular time every week. This is made worse by the fact that there is no option for a manual update of the WUS (silly acronym) server by downloading your own patches.

So M$ is making poo again (haha that metaphor gets better).

They will probally just buy a ton of servers and bandwidth to handle this, but it is a problem that will never really go away and something that most blackhats would probally remember.

The security implications of a centralised service like this are not nice and far reaching. Someone should do a Masters project on it or something.

http://seclists.org/lists/isn/2004/Apr/0048.html

UPDATE 10:46am

This article http://www.computerworld.com/securitytopics/security/story/0,10801,92037p5,00.html
Talks about why patch release should be slowed down to prevent reverse engineering of patches, which can be done faster than most people update. It also has an idea for implementation of an automated encrypted patch service. All good thoughts, my project is looking better and better.