0365 Servicing using SCCM

Anil Yadav 1 Reputation point
2021-01-24T13:27:11.027+00:00

Hi All,

I am trying to upgrade all of my 0365 clients with version 1808 ,1902 ,1908 to 2002 using 0365 servicing from MECM(SCCM).
but I have seen a strange behavior in my SCCM infra many of 0365 clients lower the 2002 version are already showing complaint as the 2002 patch is not required on those devices.

i don't know why these patches are showing as not required. went through many documents but did not find any answer.

Please let me know if someone has faced this issue and find any solution.

Microsoft 365 and Office | Office Online Server
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Amandayou-MSFT 11,156 Reputation points
    2021-01-25T03:26:58.883+00:00

    Hi @Anil Yadav ,

    It seems that there is something wrong between the client and management points. We could check CcmMessaging.log which located in C:\Windows\CCM\Logs.

    Besides, After deploying the 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:

    59840-125.png

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

    60014-1251.png

    Step 2: 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.

    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: 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.
    Using log files to track the 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.

    0 comments No comments

  2. Anil Yadav 1 Reputation point
    2021-01-25T07:02:08.727+00:00

    Hi @Amandayou-MSFT

    There is no issue with Client Communication as everything else is working fine i.e. Security update , Application , Package , Task sequence .

    My problem is 0365 servicing patch 2002 is not required on multiple devices , i have run scan on few devices the scan completed successfully but the patch is not showing as missing in update store.log.

    I am trying to understand what is the issue and how servicing patches evaluate the patch requirement on device.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.