locked
SCCM 2012 1606 not recieving Office 365 Client updates. RRS feed

  • Question

  • Hi Guys,

    We are running SCCM 2012 Release 1606 and we want to download and deploy Office 365 Client updates. We configured the settings described in this document: https://technet.microsoft.com/en-us/library/mt628083.aspx

    After we run the sync, the Office 365 Client updates are nog being showed, all other updates like Windows 10 updates are working correctly.

    Primary Site Server OS: Windows Server 2012 R2 Fully patched

    SUP OS: Windows Server 2012 R2 Fully patched

    SCCM Build: 1606

    WSUS Version on SUP: 4.0

    What could be wrong?

    Tuesday, October 4, 2016 6:52 AM

Answers

All replies


  • "SCCM 2012 Release 1606" I think you mean SCCM 1606 as "SCCM 2012 Release 1606" doesn't exist.

    After you have done a full sync, are there any errors in WSyncMgr.log?
    Tuesday, October 4, 2016 7:00 AM
  • Sorry, i mean SCCM 1606 indeed.

    The WSyncMgr.log isn't showing any errors, it even shows the Office 365 Client catagory!

    Everything looks ok, but i also can't see the Office 365 Client upates in the WSyncMgr.log

    Requested categories: Company=Local Publisher, Company=Adobe Systems, Inc., Product=Office 365 Client, Product=Windows 10, Product=Windows Server 2012 R2, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Upgrades, UpdateClassification=Service Packs, UpdateClassification=Updates, UpdateClassification=Critical Updates    SMS_WSUS_SYNC_MANAGER    4-10-2016 08:32:43    9308 (0x245C)

    sync: SMS synchronizing updates, processed 571 out of 571 items (100%)    SMS_WSUS_SYNC_MANAGER    4-10-2016 08:32:54    9308 (0x245C)

    Done synchronizing SMS with WSUS Server scwsus01.zorgnet.local    SMS_WSUS_SYNC_MANAGER    4-10-2016 08:32:54    9308 (0x245C)

    Sync succeeded. Setting sync alert to canceled state on site SDG    SMS_WSUS_SYNC_MANAGER    4-10-2016 08:32:55    4596 (0x11F4)


    Tuesday, October 4, 2016 7:13 AM
  • Problem solved!

    KB3159706 was installed on the SUP but not on the Primary Site Server.

    Tuesday, October 4, 2016 3:11 PM