[German]Windows Server Update Services (WSUS) 3.0 SP2 seems to have lost its synchronization feature a few days ago, as blog reader Martin B. just told me via email (thanks for that). Addendum: It seems that the issue has been fixed since a couple of hours.
Windows Server Update Services (WSUS) 3.0 SP2
It's not a pleasant situation for affected admins. Windows Server Update Services (WSUS) 3.0 SP2 went out of support on January 14, 2020, according to this Microsoft document.
As you may have seen, there has been an update to the extended support lifecycle for WSUS 3.0 SP2 (WSUS 3.2). We received feedback that ending this product's life in July 2017 would cause a significant disruption for those Windows Server 2008/R2 deployments that planned to rely upon it until January 2020. As such, the end of life for this product is now January 2020.
For those that currently rely on WSUS 3.2, please use this extension as an opportunity to plan a smooth transition to WSUS 4.0 (Windows Server 2012 or 2012 R2) or even our newest offering (Windows Server 2016) that will be available later this year.
Microsoft suggests switching to WSUS 4.0, but this requires Windows Server 2012 or 2012 R2. As soon as Windows 10 clients are used, there should be no way around this change. People who are still running an infrastructure with Windows Server 2008/R2 and Windows 7 are (unless I made a mistake) stuck on WSUS 3.0 SP2 (also referred to as WSUS 3.2), though.
WSUS 3.0 SP2: Sync issues since Feb. 2021
German blog reader Martin B. seems to be currently still running a WSUS 3.0 SP2 in his environment and notes that there are sync problems since a few days. In his mail Martin writes
For SBS 2011 servers, the sync of WSUS 3.0 SP2 with the servers at MS has not worked for a few days. The product is out of support since 14.1.2020, but this has not yet meant that it will not continue to work.
This is where all the sufferers have gathered so far and there is no workaround yet, only workarounds like pivoting to WSUS 4.0: WSUS Sync failure – Microsoft Q&A
In the Microsoft Q&A thread in question there is the following entry:
WSUS Sync failure
SBS2011
WSUS 3.2.7600.226WSUS sync has started to fail over the last few weeks, initially intermittentl, now I cannot get it to complete at all.
Update source is MicrosoftConsole error: Unable to resolve the specified upstream server name.
"WebException: The request failed with HTTP status 404: Not Found.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
The last successful sync was on 2/5/2021, which means the last updates from the February 2021 patchday have not been synced to WSUS. As I see from the discussion, there is not only one sufferer. Thanks to Martin B. for the hint.
Addenum: I received feedback from German readers, that the issue has been fixed sind Feb. 11, 2021 (late evening). WSUS is syncronizing again.
According to last posts in https://docs.microsoft.com/en-us/answers/questions/262172/wsus-sync-failure.html the syncronisation is working again. And I can confirm that, too. This is the message from WSUS: "New Update Alert: The following 409 new updates have been synchronized to SERVER since Friday, February 12, 2021 3:32 AM (GMT)."