WSUS woes - some client machines not getting updates

[timbo343]

After pushing out a new image to a room of machines, we are finding that in a room a 30 machines, some are downloading the updates from thw WSUS server and others are checking in to the WSUS server but saying there are no updates to download, yet all machines are checking in / reporting to the WSUS server.

 

In the room, all the machines are exactly the same, Group Policy is applying as it should.

 

I've looked in the registry of the affected machines and noticed under HKLM \ Software \ Microsoft \ Windows \ Current Version \ Windows Update there is a missing registry entry called traceID. TraceID is showing on the machines that are successfully pulling down updates from the WSUS server but missing from the troublesome machines.

 

We have tried re-imagining the affected machines yet this does not work, it is like there is an issue with the WSUS server.

 

We have tried to remove the client machines from the WSUS server, tried the clean up options, all has no effect.

 

Anyone seen this issue before and what was the fix to resolve it?

[3s-gtech]

Thick or thin imaging? This used to be an issue in the old days of imaging with Ghost and failing to sysprep properly. Didn’t have issues with thin images, and have now ditched WSUS as it was a bloody nightmare in the end.

[DrCheese]

If you have dual scan allowed & your machines are hotpatch capable they'll be pulling the hotpatch from the web instead. This has a different KB number so your WSUS server will still think the devices are unprotected & show like that (But in reality are fine)

[timbo343]

Thanks for the replies guys. I think i've sorted it after revewing the GPO settings.