Jump to content

Recommended Posts

Posted

Hey up,

 

We have a 2003R2 server running WSUS 3.0, and all seems to be well, apart from one group of PC's in a suite, which seemed to have failed a lot of updates (around 57 updates according to the server). Is there anyway of finding out why this is from the server or client, as it wasn't clear from the server console. (I am new to WSUS 3.0, old SUS was a doddle!)

 

I haven't yet tried a gpupdate on the client machines, but I guess I could also have a look at gpresult as well.... to make sure the machines are updating correctly. I suppose that the GPO on the suite could also be suspect, so will compare that to a working suite with a different GPO (we have different GPO's for each area around school, "WSUS C1" for example.)

 

Would deleting the client machines log on the server, then doing a gpupdate on the client force a refresh on the server?

 

Any other ideas?

 

Regards

Mark

Posted

The magic command you are looking for is

 

wuauclt /detectnow

 

gpupdate will update the policy used to control wuauclt, but it's not the workhorse. The above will force detection and installation if there are any outstanding updates marked for the target machine, but if they are downloading and then consistently failing on install there is something else wrong with the machine. Applying service pack is often a good fix IME.

 

 

Edit: Note, wuauclt runs silently, so you'll only see it's there by the process list and, if there are any updates marked, the tray when it starts to pull them down.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...