Greetings,

I have an issue where a large number of PCs and servers in my environment are not detecting available software updates that were deployed after patch Tuesday.  Details are as follows:

I am running SCCM 2012 R2 with CU3 on a virtual 2012 R2 server with SQL 2012 SP2 on the same VM.

I believe this started happening since last month's (April) patch cycle.  A vast majority of my clients detect available patches, install, and reboot as they should, but a large handful do not. I have checked the WUAHandler, UpdatesDeployment, UpdatesHandler, UpdatesStore, and WindowsUpdate logs on various problematic clients, and all do not show any errors when the SCCM client scans for updates.  Specifically the WUAHandler and UpdatesDeployment logs show the scans complete successfully with zero errors but do not detect any available updates.  Is this also true if I log into the PC/server and manually run the Software Updates Scan from the SCCM applet within control panel.  If I run Windows Update from a client and have it check online from windows update, it finds patches so I know the update agent works.

I know the issue is not due to patches not downloaded or deployed within SCCM as machines with the same operating system as those that are having issues received the same patches.  In one example I reinstalled the sccm client and within an hour it detected patches and I received the notification within the system tray.  In another example I reinstalled the agent but it did not detect patches.  And again, the logs on the client do not show any errors.  It simply does not detect any patches are available.  The machines that are having issues are running various operating systems (Windows 7 x86, Server 2003 SP2, Server 2008 R2, and Server 2012.)

In some occasions, rebooting the PC or server has resolved this for a random machine but for most of the affected machines, a reboot doesn't do anything to help.

If anyone has any suggestions on where to look or what to do to help troubleshoot or resolve, I would appreciate it.

Thanks,

Mike G

• Edited by mgorski10 Wednesday, May 27, 2015 5:24 AM

UPDATE:

I checked a Server 2012 R2 machine and found the following in the WindowsUpdate.log.  (Error is at the very bottom.)  

<...>
2015-05-29 14:47:20:228  896 c58 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-05-29 14:47:20:228  896 c58 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037

If you mean this WARNING, that's nothing to worry about, it is expected and normal. (that is why it is a WARNING and not an ERROR)

Are there any log lines like this?

WARNING: ISusInternal::GetUpdateMetadata2 failed, hr=8007000E

some background into why I asked about hr=8007000E

http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx