Wsus clients not updating or checking in with server
The cause of the problem apparently was a Microsoft Intune service update.
At least that's how it was reported in the Microsoft Services Status Dashboard.
Some organizations have a test fix from Microsoft, called the "test package." KB3159706 will update it.
Microsoft's announcement recommended these steps for organizations with WSUS systems affected by the bad KB3148812 patch: In other WSUS news, Microsoft's WSUS service went down for about 12 hours on May 4. Yesterday, organizations couldn't get updates to WSUS.
If you don’t know what to do here, leave these two lines out (or REM them out).The process of checking DCOM configuration is slightly different on different operating systems.Sometimes the most challenging part of the Configuration Manager 2007/SMS 2003 deployment phase can be ensuring that the client successfully reports to the site server.It's needed for Windows Server 2012 and Windows Server 2012 R2 users that want to keep Windows 10 clients up to date.This WSUS update can't be skipped by those users, Microsoft's announcement explained: Skipping this KB [KB3159706] means not being able to distribute the Windows 10 Anniversary Update, or any subsequent feature update, via these platforms.
This last section above will restart services, and then force an update check, and then open the Windows Update dialog.