What I have found is that if the update doesn't download properly and fails to install, the automatic update client will not download the update again. It will continue to try and install the bad download. This happens with both WSUS and conventional automatic updates.
The only way I have found to fix it is to stop the automatic updates service, then delete the contents of C:\Windows\SoftwareDistribution, then restarting the automatic updates process again. I have a script to do that here: http://www.amset.info/windows/auto-updates.asp It has to be run on the client, but works well with the psexec tool from sysinternals. Just last week I used the tool to correct over 200 workstations from the server following a bad download. Must blog on how I did that. Simon. -- Simon Butler MVP: Exchange, MCSE Amset IT Solutions Ltd. e: si...@amset.co.uk w: www.amset.co.uk w: www.amset.info Need cheap certificates for Exchange, compatible with Windows Mobile 5.0? http://CertificatesForExchange.com/<http://certificatesforexchange.com/> for certificates from just $23.99. Need a domain for your certificate? http://DomainsForExchange.net/<http://domainsforexchange.net/> ________________________________ From: Gavin Wilby [mailto:gavin.wi...@gmail.com] Sent: 12 December 2008 09:48 To: NT System Admin Issues Subject: WSUS3 Question This might be blindingly obvious to some - but not to me unfortunatly ;) If I have a WSUS3 server, and its pushing out updates both ones I approve and automatically security and critical, and then some of those updates fail to install. Whats the approved methos of dealing with it - do i have to go to each machine and sort ot out manually, will re-approving the update force it out again? Does a wuauclt /detectnow force the client to retry. I cant get a definitive answer to this,.. so does anyone know? Gavin. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
