Sorry I should have mentioned that for most logs, there are no apparent errors present, except for the Windows Update log. The following does appear in that log: WARNING: ISusInternal::GetUpdateMetadata2 failed, hr=8007000E.
I have researched that error before and realized too that there is a patch for Windows 7 and Server 2008 R2 but no help for Server 2008 SP2. Checking the WUA on affected servers returns version 7.6.7600.256. I have cleaned up the WSUS database many times on the SCCM server so that * *shouldn't** be an issue. I haven't tried the workaround others online mention so don't know if this works or not, but in desperation I might on a non-production test server: sc config wuauserv type= own Thank you for the quick responses. John On Tue, Aug 1, 2017 at 11:23 AM, Jason Sandys <ja...@sandys.us> wrote: > I think the WUA version issue is rearing its head again. > > > > Basically, the only way to get updated WUA version used to be directly > from WSUS – it was the dark times of the WUA because originally you used to > be able to download it and install it, then someone made the brilliant > decision that you could only get it from WSUS using the self-update > mechanism. Then the Win 7 x86 out of memory issue hit because the WSUS > catalog has gotten ginormous (among other issues) and after about 8 months, > the released an updated WUA in the form of a hotfix (brilliant again since > how do you deploy a Windows Update to a system where Windows Update isn’t > working?) > > > > Anyway, they only released this update, and many others since, for Win 7, > Win 8, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 > R2. These updates started rolling out about 3 years year I believe. > > > > No Vista or Windows Server 2008 updates were ever released as hotfixes to > my knowledge though and so you are stuck with the self-update mechanism > from WSUS; however, this self-update mechanism only works if you have > “Automatic Updates” enabled on your clients. Of course, we (the community > and Microsoft collectively) recommend to disable “Automatic Updates” to > prevent the UA from doing anything autonomously like reboot or install > updates directly from WSUS. Oh, and of course Vista is no longer supported > anymore and so Microsoft doesn’t really care about the client components > anymore that were common to both like the … WUA (that last bit is my > opinion, please don’t take that as fact although it very well could be). > > > > Catch-22s a plenty in this twisted tale 😊 > > > > So, first thing to do is check the WUA version on all of your Windows > Server 2008 systems (ConfigMgr already collects this for you so very easy: > https://technet.microsoft.com/en-us/library/bb680319.aspx). > > > > Next, you can manually try to update the WUA on a Server 2008 system where > updates aren’t working by doing the following – I’m of course assuming that > you’ll have multiple versions on your Server 2008 systems based on the info > in ConfigMgr and the ones not working will have an older version): > > - Enable Automatic Updates > - Run wuauclt /detectnow > - Disable Automatic Updates > - Check the version (can be determined from the version of the > Wuaueng.dll file n System32 – reference https://msdn.microsoft.com/en- > us/library/windows/desktop/aa385815(v=vs.85).aspx) > > <https://msdn.microsoft.com/en-us/library/windows/desktop/aa385815(v=vs.85).aspx)> > > > > Hopefully it updated and everything will work. > > > > If so, I’ve got a script to do this automatically for you at > http://blog.configmgrftw.com/?ddownload=2961 and a couple of blog posts > to unarchive. > > > > If not, and you actually read this far and did what I’ve recommended, > please let us know but ultimately, this may be case with Microsoft. > > > > J > > > > > > *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *John Lumadue > *Sent:* Tuesday, August 1, 2017 9:40 AM > *To:* mssms@lists.myitforum.com > *Subject:* [mssms] Server 2008 Std SP2 systems no longer reporting patch > status > > > > Has anyone else experienced this behavior? All of our Windows Server 2008 > Standard SP2 systems no longer report in to SCCM their patch status and > reports for various compliance states on these systems are blank. Win2008 > R2 systems are fine. This started back in April/May time-frame and I have > to patch them manually though Windows Update now. They will eventually be > replaced but it is a pain to not have the ability to monitor and patch them > via SCCM. Other deployment methods are fine for them, just Software > Updates issue. > > > > I verified they have the latest Windows Update Agent and I tried various > methods of troubleshooting such as recreating the SoftwareDistribution > folder, re-registering DLL files, etc. Nothing is resolving problem so far. > > > > Our SCCM is at Current Branch 1702. > > > > > > Thanks, > > > > > > John > > > >
