Share via

sccm2012-Automatic Deployment Rules

Ahmed Deban 36 Reputation points
2021-11-09T08:26:11.39+00:00

Dears ,

I have issue with Automatic Deployment Rules the windows updates downloaded by WSUS in SCCM, but my problem the updates didn't push to Device Collections:

As I Checked the distribution point status it's Distributed Successfully, But the Device Collections it's not getting the windows updates as I checked the logs AppEnforce.log not updating showing some errors 0x87d00213 and appdescovery.log as well.

147649-image.png

147569-image.png

Please anyone can support me in this problem and how to troubleshoot and check the errors for the collections side ..

I appreciate your support ..

Thanks

Microsoft Security | Intune | Configuration Manager | Other
Sysinternals
Sysinternals

Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Ahmed Deban 36 Reputation points
    2021-11-14T05:49:48.56+00:00

    Hi @Amandayou-MSFT

    Thanks for your support, But I think there unusual problem with Automatic Deployment Rules as I checked your mentioned Logs:

    The Distribution Point Success and Compliant but not updating in the clients : which Logs and traffic related Distribution Point → Pushing Client to rectify the issue I will try to uploading the logs for you if possible ;
    149080-image.png

    PolicyAgent.log -Client

    -149106-image.png

    Monitoring Distribution Status :Done

    149132-image.png

    Deplyments :Unknown ,As sent Evaluate Software Update Deployments it's success

    149065-image.png

    149006-image.png

    Was this answer helpful?


  2. Amandayou-MSFT 11,166 Reputation points
    2021-11-10T02:41:45.33+00:00

    Hi @Ahmed Deban ,

    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:

    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.

    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.

    Detailed information could be referred to this link:
    https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/track-software-update-deployment-process#deployment-evaluation-and-update-installation-on-clients


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    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.

    Was this answer helpful?

    0 comments No comments

Your answer

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