none
Offline Sync of Office 2019 Software Updates RRS feed

  • Question

  • We have an offline WSUS/SCCM server that reports a "Last Synchronization Error Code" of 0x80131509. Wsyncrmgr.log is very long, so I'm just going to post the sections that CMTrace.exe highlighted in red in below. The sync will work if I first use the WSUS console to decline all Office 2019 updates. That works in the short-term, but we will upgrade to Office 2019 at some point. Has anyone found a way to deploy Office 2019 updates via SCCM in an offline network?

    Process O365 update manifest with no proxy.

    ProcessFileManifest() failed to process O365 file manifest. Caught exception: System.Net.WebException: The remote name could not be resolved: 'config.office.com'~~   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)

    Failed to synchronize O365 update 5239b0f5-4241-4e33-ab61-7b1aa85ea93b - Office 2019 Perpetual Enterprise Client Update Version Perpetual for x64 based Edition (Build 10351.20054)

    STATMSG: ID=6709 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=<removed> SITE=<removed> PID=4672 TID=1844 GMTDATE=Wed Oct 16 13:17:42.885 2019 ISTR0="Office 2019 Perpetual Enterprise Client Update Version Perpetual for x64 based Edition (Build 10351.20054)" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

    Skipped update 5239b0f5-4241-4e33-ab61-7b1aa85ea93b - Office 2019 Perpetual Enterprise Client Update Version Perpetual for x64 based Edition (Build 10351.20054) because it failed to sync.

    That section is repeated for the x86 update.

    Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse

    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=<removed> SITE=<removed> PID=4672 TID=7940 GMTDATE=Wed Oct 16 13:31:36.393 2019 ISTR0="Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

    Sync failed. Will retry in 60 minutes


    • Edited by Loc750 Wednesday, October 16, 2019 3:46 PM
    Wednesday, October 16, 2019 2:21 PM

Answers

All replies

  • Wsyncrmgr.log is very long

    The post the log on a file sharing service and then post a link to that.

    so I'm just going to post the sections that CMTrace.exe highlighted in red

    This is mostly useless as what's in red in CMTrace isn't necessarily an error, errors aren't always fatal or actionable, and just focusing on errors is rarely enough for many reasons. Log files are about context and thus out of context log lines rarely mean much by themselves.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, October 16, 2019 6:13 PM
  • Hi,

    Please make sure that your hierarchy's top level WSUS server and the top level Configuration Manager site server must have access to the following URLs:

    *.microsoft.com, *.msocdn.com, *.office.com, *.office.net, *.onmicrosoft.com, officecdn.microsoft.com, officecdn.microsoft.com.edgesuite.net. 

    For more details, see Office 365 URLs and IP address ranges:

    https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges#microsoft-365-common-and-office-online 


    Best regards,
    Larry


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    Thursday, October 17, 2019 6:50 AM
  • The top level WSUS server has access to those urls, but the top level Configuration Manager site server is on an offline network. We use the process in https://docs.microsoft.com/en-us/sccm/sum/get-started/synchronize-software-updates-disconnected and a USB drive to transfer the export metadata and WsusContent folder to the offline network. If SCCM itself needs access to the internet then I guess we won't be able to deploy Office 365/2019 updates. Thanks for your help.
    Thursday, October 17, 2019 1:48 PM
  • Hi,

    Glad that the question has been solved!

    And thank you very much for your feedback.


    Best regards,
    Larry


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 21, 2019 7:12 AM