Wsus server not self updating
The CAU self-updating feature performs like any other clustered workload, and it can work seamlessly with the planned and unplanned failovers of an update coordinator computer.Remote-updating Enables you to start an Updating Run at any time from a computer running Windows or Windows Server.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.Cluster-Aware Updating (CAU) is a feature that coordinates software updates on all servers in a failover cluster in a way that doesn't impact the service availability any more than a planned failover of a cluster node.For some applications with continuous availability features (such as Hyper-V with live migration, or an SMB 3.x file server with SMB Transparent Failover), CAU can coordinate automated cluster updating with no impact on service availability. CAU supports updating Storage Spaces Direct clusters regardless of the deployment type: hyper-converged or converged.One of the virtual domain controllers is not taking MS Updates, a few months ago it did then something happened and it changed, so WSUS is not updating it and when i try it manually i am getting Error code: 8000FFFF, the other DC is updating fine When i check C: Windows windowsupdate Setup Downloading setup package "WUClient-Self Update-Core-Top Level~31bf3856ad364e35~amd64~~7.6.7600.256" Setup Downloading setup package WUClient-Self Update-Core-Top Level~31bf3856ad364e35~amd64~~7.6.7600.256from Misc Validating signature for C:\Windows\Software Distribution\Self Update\Packages\WUClient-Self Update-Core-Top Level~31bf3856ad364e35~amd64~~7.6.7600.256\WUClient-Self Update-Core-Top Level~31bf3856ad364e35~amd64~~7.6.7600.256.cab: Misc Microsoft signed: Yes WARNING: Load Library failed for with hr:8007007E Setup Staging setup package "WUClient-Self Update-Active X~31bf3856ad364e35~amd64~~7.6.7600.256" Setup WARNING: CBS staging operation failed, error = 0x8000FFFF Setup FATAL: Failed to stage setup package "WUClient-Self Update-Active X~31bf3856ad364e35~amd64~~7.6.7600.256", error = 0x8000FFFF Setup WARNING: Failed to stage applicable setup packages, error = 0x8000FFFF Setup FATAL: Downloading binaries for Self Update failed, err = 0x8000FFFF Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF Agent * WARNING: Exit code = 0x8000FFFF I have checked the registry as suggested in KB946414 and the values were not in it on the server running WSUS and the values are not there.
All servers are 2008R2, 2 physical servers running Hyper-V and these run 8 Virtual machines, each physical has one domain controller on it.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.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.