Thanks for all the replies guys, and for clearing up how the mechanism works. I found this on another site which may help.
-- @echo off rem Batch file to clear the BITS queued jobs: net stop bits net stop wuauserv Del /q "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr0.dat" Del /q "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr1.dat Rd /s /q "%Windir%\SoftwareDistribution\" net start bits net start wuauserv wuauclt /detectnow -- Gavin. On Fri, Dec 12, 2008 at 2:45 PM, Ben Scott <[email protected]> wrote: > On Fri, Dec 12, 2008 at 4:47 AM, Gavin Wilby <[email protected]> > wrote: > > ... some of those updates fail to install. > > ... do i have to go to each machine and sort ot out manually ... > > It really depends on why it failed. As others have said, AU (Auto > Update) works by having clients fetch updates from your WSUS server. > > If the update fails to install due to something "outside" of > AU/WSUS, AU will keep retrying that update every cycle. For example, > say the client lacked disk space to do the download, or was missing a > software dependency that the update didn't check for. Once that's > fixed, on the next cycle, AU will install the update. > > If the AU client itself is broken, then you generally need to fix > the AU client somehow. That might be by doing the standard AU reset > (delete SoftwareDistribution, re-register DLLs, etc.), or something > more complicated, depending on the failure mode. > > If WSUS was broken, and pushed out a bogus update to the client, the > AU client may not see the "fixed" update as new. If it just prevented > the update from downloading, the AU client will keep retrying, as > above. > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
