Software Updates Deployment Package "Is Deployed" - "No"

VitalyK-4619 1 Reputation point

There is a Software Updates Deployment Package in Microsoft Endpoint Configuration Manager. Every month I add new updates to this package and create a deployment on the collection of computers. I have revealed that despite the fact that in the Deployment Package are many updates only last-month updates are deploying during the current deployment. Others never install even if they are missing on new computers. Their status in Microsoft Endpoint Configuration Manager "Is Deployed" - "No", "Downloaded" - "Yes" All these updates with status "Is Deployed" - "No" were actually downloaded and deployed earlier this year. Maybe my mistake is that I delete old deployments when I create a new one. I'm confused, because I think that if there are all the updates in the Deployment Package they will be deployed and installed with a new deployment. Am I wrong?


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).
922 questions
Microsoft Configuration Manager
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Jason Sandys 31,116 Reputation points Microsoft Employee

    Every month I add new updates to this package

    Adding updates to an update (aka deployment) package does not in any way deploy them and is completely unrelated to whether or not they are deployed as update packages are not deployable.

    You have two choices for deploying updates in ConfigMgr: You either deploy the update(s) individually and directly or you add them to an update group and deploy the update group.

    Update groups are not the same as update packages. Update groups group updates for deployment and reporting purposes. Update packages are containers for update content, i.e., the actual files for the updates so that the clients can download the files when needed from a DP.

    Is there a reason you aren't using ADRs? ADRs will do everything for you based on rules that you configure.

    0 comments No comments

  2. AllenLiu-MSFT 38,006 Reputation points Microsoft Vendor

    Hi, @VitalyK-4619
    Thank you for posting in Microsoft Q&A forum.
    When you say "add new updates to this package and create a deployment on the collection of computers", I think you create the new SUG and select the old package "Office2016x64", and you have deleted some old SUG deployment, so the updates in old SUG still show in the package but the deployment is deleted.
    Like Jason suggested, you may use a ADR to automatic this.

    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.