Unable to apply Office 2019 Updates through SCCM

Arthus Chan 1 Reputation point
2020-09-14T09:01:33.213+00:00

I have follow the guide to apply Office 2019 Updates with SCCM manage-office-365-proplus-updates

SCCM Version: 5.00.8968.1042, Enable management of the Office 365 Client Agent is set to Yes

My Office 2019 version: 16.0.10361.20002, OfficeMgmtCOM is true, UpdatesEnabled is true

I use SCCM manual deploy 16.0.10364.20059 in SCCM, but my Office 2019 version failed to update and still stuck at 16.0.10361.20002 and unable to update to 16.0.10364.20059

What am i miss?

24408-client-office-2019-registry.jpg

24367-sccm-setting.jpg24398-sccm-update-deploy.jpg

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).
1,005 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amandayou-MSFT 11,051 Reputation points
    2020-09-15T03:08:13.58+00:00

    Hello @Arthus Chan ,

    After deploying the software update, there might be seven steps to troubleshoot the common issues.

    Step 1: We could check Policyagent.log. When policy is received, the following entry is logged in PolicyAgent.log:
    24812-915.png

    We could check if Deployment Unique Id on the console is consistent with policy id displayed in PolicyAgent.log.
    24813-9152.png

    Step 2: Software update would be checked if it is required by client , kindly check UpdatesStore.log. UpdateStore.log would record updates as missing if they are required. If it is not required or has been installed by client, there is no record in this log.

    Step 3: If the update is required, the content could be detected before downloading. We could refer to UpdatesDeploymentAgent.log.

    Step 4: The content could be downloaded. we could refer to UpdatesHandler.log, CAS.log, and ContentTransferManager.log. Here is a screenshot about ContentTransferManager.log.

    Step 5: After the download is completed, detection could be followed before installation. We could refer to UpdatesHandler.log,ScanAgent.log, UpdateStore.log, WindowsUpdate.log and WUAHandler.log.

    Step 6: Software update could be installed. We could refer to Windowsupdate.log and UpdatesDeployment.log.

    Step 7: After the updates are installed, Updates Deployment Agent checks whether any updates require a reboot, and then it notifies the user if client settings are configured to allow such notification. We could refer to UpdatesDeployment.log and UpdateStore.log.

    Here is an article about some detailed log screenshots.
    https://video2.skills-academy.com/en-us/troubleshoot/mem/configmgr/track-software-update-deployment-process

    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.