WSUS 3.x doesn't actually push updates-the clients pull them based on the registry information they have that points them to that WSUS server. So, you generally have to go to the clients and sort out the underlying problem.
The only time I've found this not to be the case is if you have a bad update on the server. If that happens, all clients will fail to install that same update and you have to look at fixing the server side. Wuauclt /detectnow run at the client machine will force a retry, but that alone (just a retry) doesn't usually fix a failed update install. -Bonnie From: Gavin Wilby [mailto:[email protected]] Sent: Friday, December 12, 2008 1:48 AM 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/> ~
