One of my customers reported that his sccm console shows only one Office 365 Client Update while there should have been five per Microsoft’s official site. The other four Office 365 Updates still refused to appear even after several successfully attempts of synchronization.
When I check the wsyncmgr.log, the following information caught my eyes:
Synchronizing update e99a4c28-2da4-47f8-9de8-94881c745a06 – Office 365 Client Update – Monthly Enterprise Channel Version 2003 for x64 based Edition (Build 12624.20588) $$<05-20-2020 08:38:21.444-480>
Failed to synchronize O365 update e99a4c28-2da4-47f8-9de8-94881c745a06 – Office 365 Client Update – Monthly Enterprise Channel Version 2003 for x64 based Edition (Build 12624.20588) $$<05-20-2020 08:45:18.053-480>
Skipped update e99a4c28-2da4-47f8-9de8-94881c745a06 – Office 365 Client Update – Monthly Enterprise Channel Version 2003 for x64 based Edition (Build 12624.20588) because it failed to sync. $$<05-20-2020 08:45:18.053-480>
What is weird is that those failed updates will not be synchronized again during the next synchronization. That is why even after several update synchronizations those failed updates are always invisible, and the wsyncmgr.log shows nothing unusual. See below.
sync: Starting SMS database synchronization 28236 (0x6E4C)
Requested categories: Product=Office 2007, Product=Office 2016, Product=Office 365 Client, Product=Office 2013, Product=Office 2010, Product=Windows 10, Product=Windows 10, version 1903 and later, Product=Windows 7, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Upgrades, UpdateClassification=Service Packs, UpdateClassification=Updates, UpdateClassification=Critical Updates 28236 (0x6E4C)
Set content version of update source {D3DE997C-5CE1-4C70-AB28-127587CFB7F8} for site NC2 to 65 37484 (0x926C)
STATMSG: ID=6702 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_WSUS_SYNC_MANAGER” SYS=CONESVILLE800.STARHUBSG.SH.INC SITE=NC2 PID=37224 TID=37484 GMTDATE=Thu May 21 03:14:41.967 2020 ISTR0=”” ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0 37484 (0x926C)
I looked into the wsus database and site database only to find that all those desired updates are present.
Later I came to know that most synchronizations perform a delta synchronization, which actually does not repair any updates from previous synchronizations. That is why several attempts of synchronization could not fix the failed updates. Only a full synchronization will potentially repair updates from previous synchronizations that have gotten damaged or deleted. For details, refer to the link at the bottom.
So I asked the customer to create an empty file named full.syn in, eg. C:\Program Files\Microsoft Configuration Manager\inboxes\wsyncmgr.box on the primary site where the sync is to be done. That file will trigger a full synchronization. After that all the five Office 365 Updates came listed in sccm console.
SCCM Monde 