Question regarding SCCM Application - Update Content

M Tran 486 Reputation points

I am still uncertain of what to do. I have read that whenever you make changes to a deployment type (including changes to install commands, detection methods, or any other properties of an application, you have to "update content"

This will change the ContentID.

Is this true - that I must update content every time I make a change to a deployment?

Thank you!

Microsoft Configuration Manager
0 comments No comments
{count} votes

Accepted answer
  1. Simon Ren-MSFT 31,911 Reputation points Microsoft Vendor

    Hi @M Tran ,

    Thanks for posting in Microsoft MECM Q&A forum.

    Agree with @Eswar Koneti here. Only when we change the source file for a deployment by adding new files or replace existing files with a newer version, update content action is needed. When we change the detection method, requirements, return codes etc. for the application, we do not need to update content.

    And when we update the content for an application deployment type, Configuration Manager creates a new content ID for the deployment type, and the package references the new content ID.

    For more information about update content, please refer to the official article:
    Deploy and manage content for Configuration Manager

    Hope it helps. Have a nice day!

    Best regards,

    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.

    1 person found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Eswar Koneti 2,201 Reputation points

    Is this true - that I must update content every time I make a change to a deployment?

    No, thats not true. Update content refers to the source files that you are using in the application and is not applicable to detection, requirement rules and other properties of the application etc.


    2 people found this answer helpful.
    0 comments No comments

  2. M Tran 486 Reputation points

    Thank you both for your answer! and Thank you @Simon Ren-MSFT for the explanation. This brings up the question that I am still somewhat confused, regarding new versions for application.

    For example, I have deployed peazip 8.5 to my environment. Then months down the road a new peazip v9 is released. Can I then just delete peazip 8.5 and replace with v9, modify the deployment type and do "update content", or must I go through the "supersedence" process? In an article somewhere it says when you do supersedence, you have to keep all file versions. Wouldn't this eventually make you run out of storage space?

    Thank you!