Wsus client not reporting but updating
In addition they now have about 30 Windows 10 devices.
I also have a WSUS Server i point client servers to which i decided to point some Windows 10 lab machines at.
The fix for that was easy, and required creating and populating that folder.
The folder in question can be found here, C:\Program Files\Update Services\Self Update\WSUS3 inside here are 3 folders one for each architecture.
On my Surface i had manually set to Defer Upgrades.
As part of writing this post i set my Surface to talk to WSUS through the Local Group Policy, I didn’t change the Defer Upgrades setting in the GPO, so my choice in the GUI was still applied.
This is nicely explained in a blog post from back in 2008!
If your WSUS is already in working order, your Windows 10 machines should be registering, but, will likely show no status for updates.
First thing we need to do is make sure your server is patched to support Windows 10. KB3159706 includes manual steps to complete, which are: You may find these changes are already present, if not enter those highlighted, and save the file. We need to make some adjustments to IIS which we can do with Power Shell.
The reason for that is, it is not a permanent failure, the error just means it reached the max number of updates it can process this time around. It may then error 3 or 4 more times or as many times as it takes until it has processed the whole list of updates.
You want this process to complete as fast as possible, so, lowering the frequency from say 22 hours, to 1, means it might complete in 4 hours, instead of 4 days.
Neither of which were working to support Windows 10.
When logging in to it to begin working on Windows 10, i noticed that not many clients had actually reported status. Clients not reporting is again another issue that plagues WSUS administrators the world over with various fixes and tweaks.If you are not if this step applies, you should make sure you have a full, tested backup of the server and then run through the procedure.