Recent issues with SUP syncing with Office 365 Updates

LA 1 Reputation point
2022-11-17T15:06:15.327+00:00

Good morning,
I just wanted to see if anyone is having issues syncing any updates for O365?

For the last couple of days, we're getting these failures on two updates: 

Synchronizing update 3aec3508-50dc-4fc4-933a-4e52e2bb0124 - Microsoft 365 Apps Update - Current Channel (Preview) Quality Update for x86 based Edition Version 2211 (Build 15831.20122)  
  
Base Url for Office update file list service not configured or not valid , keep the original Url  
  
ProcessFileManifest() failed to process O365 file manifest. Caught exception: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.~~   at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)~~   at   
[truncated]  
 AsyncProtocolRequest asyncRequest, Boolean renegotiation)~~   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)~~   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)~~   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)~~   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)~~   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)~~   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)~~   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)~~   at System.Net.ConnectStream.WriteHeaders(Boolean async)~~   --- End of inner exception stack trace ---~~   at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)~~   at System.Net.WebClient.DownloadString(Uri address)~~   at Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.ProcessFileManifest_O365Service(String sO365ServiceUrl, XmlWriter xml, String updateId)  
  
Failed to synchronize O365 update 3aec3508-50dc-4fc4-933a-4e52e2bb0124 - Microsoft 365 Apps Update - Current Channel (Preview) Quality Update for x86 based Edition Version 2211 (Build 15831.20122)

We get the same for it's x64 sibling. The error tells me that our proxy is potentially blocking it, but it's not telling me the URL for me to verify. Is there a way to force the URL to be logged in wsyncmgr.log so I at least have a starting point to investigate?

Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
955 questions

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. HENRI WELLING 6 Reputation points
    2022-11-21T15:08:56.187+00:00

    I'm experiencing the same issue. The issue is only with "Microsoft 365 Apps Update - Current Channel (Preview) Quality Update for x64 based Edition Version 2211" (and x86) updates. Note that looking on the WSUS console, the sync shows that it is successful, so the issue looks to be internal to ConfigMgr and this specific channel / version of M365 and builds 15831.20122 / 15831.20100. As we do not use these, there is no negative effect besides the reporting of the sync failure in ConfigMgr, which is of course not a good thing. I suspect there is something "off" with these builds and hopefully MS will fix this soon.

    1 person found this answer helpful.
  2. Rahul Jindal [MVP] 9,126 Reputation points MVP
    2022-11-17T22:10:36.44+00:00

    Are you using a wsus service account by any chance?

  3. Simon Ren-MSFT 29,716 Reputation points Microsoft Vendor
    2022-11-18T09:13:07.26+00:00

    Hi,

    1,Please make sure the requirements for using Configuration Manager to manage O365 are met. The hierarchy's top-level WSUS server and the top-level Configuration Manager site server have access to the following URLs: *.microsoft.com, *.msocdn.com, *.office.com, *.office.net, *.onmicrosoft.com, officecdn.microsoft.com, and officecdn.microsoft.com.edgesuite.net. Refer to:
    Requirements for using Configuration Manager to manage Office updates

    2,It may be a certificate issue. On the SUP IIS server check the bindings for port 443 and verify a valid server certificate is chosen. Also click on SSL icon in IIS and choose the accept option. Similar thread for your reference:
    Office 365 updates not anymore visible in SCCM console

    Thanks for your time. Have a nice day!

    Best regards,
    Simon

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  4. Matt 151 Reputation points
    2022-11-22T16:13:28.337+00:00

    @LA ,

    what channel you are using on the clients "Current" or "Semi-Annual"?

  5. Steve Cahill 6 Reputation points
    2022-12-12T21:20:46.23+00:00

    We use Semi-Annual but have had this same issue about 5 times in the last month. Each time I have had to manually decline the Current Channel (Preview) updates and resync, which resolves it. It seems that these come out quite regularly (more than once a month), which is a pain as we get SCOM alerts (incidents) for the WSUS sync failures each time this happens.