SCCM - Unknown Assests within Windows Servicing/Updates

Question

Hi,

I'm a bit new to SCCM and was dropped in as the "SCCM Guy" after everything was made. So if I ask something dumb, please bare with me.

I'm tackling the Update portion of our SCCM server as of late, and we just had to reinstall WSUS. After a successful re-installation of WSUS, I am now getting a lot of clients counting in as Unknown.

We always had a few unknowns before and I understood why, but now I'm at a loss. I don't quite understand how I can get some clients but not all to show here.
I tried looking around and I can only find posts that are a few years old with logs I just can't find.

Some info:
Version: 5.00.9058.1000
GPO Automatic Updates: Disabled
Checked WindowsUpdate.log on a few clients: Getting back Failed 80070032 (if this helps any)

If anyone can get me starting on the right track that would be great! Also any info of what logs to check and where I could find them, or any help would be greatly appreciated!

Answer 1

Unknown means exactly that: ConfigMgr has not heard anything back from the client for this deployment's compliance state and so it has no idea what state it is in and is thus "unknown".

For troubleshooting updates in ConfigMgr, always start with the wuahandler.log. Also, don't fixate on a single error code, message or line. All errors must be interpreted in context and out of context have little to no meaning for troubleshooting purposes.

Answer 2

Also, look at the update scan status of the devices.

Answer 3

Hi, @Brandon Stade
Thank you for posting in Microsoft Q&A forum.

Agree with Jason, we always start from checking WuaHander.log on client for the updates unknown issue.
Here is the steps we may follow to check:
https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/troubleshoot-software-update-scan-failures#compliance-results-unknown

If you have the reporting services point installed, we can also check the report to see if there are a large number of devices reporting scan errors:
The report: Software Updates – E Troubleshooting > Troubleshooting 1 – Scan errors

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

So I had to put this on the back burner for a little bit, I am now taking a look at it again today.

After checking back it looks like there are a few more that are now showing up properly. Someone told me that IIS needs to rebuild after a WSUS reinstall? Not sure if that is true or not, but it does look like to be getting better, slowly, over time.

I think I will give it over my 3 day weekend here to see if it corrects it self.

Thanks for all the inputs!!