However, the patch had some flaws, causing WSUS to not be able to connect with Windows clients, among other problems.Some organizations that applied the flawed KB3148812 update have had dysfunctional WSUS systems for almost two weeks. The fix is a new Knowledge Base item called "KB3159706," as described in this announcement today.Those steps are described in Microsoft's KB3159706 Knowledge Base article. It's also offering it through the Microsoft Catalog.KB3159706 also is arriving through the Windows Update service as an "optional update." The Windows Update distribution approach is being done for the organizations that have disabled WSUS systems.In part two, I looked at how to configure computers to use WSUS, create WSUS groups to target updates and how to approve updates for distribution.
At least that's how it was reported in the Microsoft Services Status Dashboard.
Note that Windows Server 2016 will have this functionality at RTM.
IT pros will have to carry out some manual configuration steps to get this update to work with WSUS.
Essentially, KB3159706 does the same thing as KB3148812 was supposed to do.
It prepares the way for WSUS to automatically decrypt Windows 10 feature updates.
It's needed for Windows Server 2012 and Windows Server 2012 R2 users that want to keep Windows 10 clients up to date.