ADR Package growing !!!

Duchemin, Dominique 2,006 Reputation points
2022-03-03T23:46:52.723+00:00

Hello,

I have an ADR:
179891-2022-03-03-15-33-00-adr-iss-servers-2018-01.png

But why do I still have 2018 updates (4 years ago in the package)? the package is 80 GB!!
179901-2022-03-03-15-44-22-adr-iss-servers-2018-01-packag.png

Thanks,
Dom

Microsoft Configuration Manager
0 comments No comments
{count} votes

Accepted answer
  1. Jason Sandys 31,176 Reputation points Microsoft Employee
    2022-03-04T15:22:42.187+00:00

    But why do I still have 2018 updates (4 years ago in the package)?

    Because there's no mechanism to remove unexpired updates from a package. Do not confuse the package with a deployment group, they are two completely different things and are not specifically linked.

    If you want to remove these older updates from the package, you can easily go into the package and manually remove them ensuring you only remove those that are not deployed (there's a column for that in the package view so this is easily done). However, how do you know nothing will ever need these updates again? How do you know an admin won't remove one of these older security updates? Why is 80GB a big deal? Assuming you are using cheap storage (which you 100% should be for content storage in ConfigMgr) this is like $100 of disk space (if that even) so removing them has no benefit except to slow the process down if one of these updates is ever needed again.

    I do strongly recommend that you revise your ADR though. Here's an older blog of mine where I cover my recommended "starting point" for ADRs: https://home.memftw.com/software-updates-and-automatic-deployment-rules-in-configmgr/

    1 person found this answer helpful.
    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Amandayou-MSFT 11,051 Reputation points
    2022-03-04T03:18:45.053+00:00

    Hi @Duchemin, Dominique ,

    I check it in my environment, actually, the ADR is dynamic.

    Please check if the named 2018 01 software update deployment has the update which released or revised last 1 month, for example, 1/13/2022. If not, it is normal. We could create the appropriate updates in a new deployment package, please find it in other ADR.

    179935-34.png

    If the update of the most recent month is in ADR, it maybe something wrong with ADR, we could rerun the ADR, and click the tab of preview to check what the updates are available.

    179895-341.png

    If it is not normal, we could recreate the ADR, and check the ruleengine.log to see if any error in it.


    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.

    1 person found this answer helpful.
    0 comments No comments

  2. Duchemin, Dominique 2,006 Reputation points
    2022-03-04T03:52:35.687+00:00

    Hello,

    Yes the latest Software Updates are in the ADR and Package 03/02/2022 are already in...
    179904-2022-03-03-19-46-45-software-updates-adr-server-02.png

    When running the preview on the ADR it contains only the current month which is what is expected.
    179953-2022-03-03-19-42-36-software-update-preview.png

    What should be in the ADR? All Software Updates or only the current month seen in the preview?
    Should I create a new package each time? (1) or (2) ?
    179879-2022-03-03-19-50-44-software-updates-adr-server-03.png

    If I select (1) how do I cleanup the content of the package?
    If I select (2) what should I do with the previous month package?

    Thanks,
    Dom

    0 comments No comments

  3. Duchemin, Dominique 2,006 Reputation points
    2022-03-05T00:33:46.737+00:00

    Thanks Jason will review your blog.

    Thanks,
    Dom

    0 comments No comments