How does configuration manager application supersedence work

i8displaynames 6 Reputation points
2021-10-19T12:48:11.603+00:00

I am trying to understand how application supersedence works in configuration manager.

I am trying to deploy an updated version of Adobe CC but with it being so large I wanted to set the new version as available rather than required and let users know its there, I also want when the new version is installed for the old version to be removed. So this is my scenario

Adobe CC 2020 is/was deployed as a required install
Adobe CC 2021 is deployed as an available install and is configured as superseding Adobe CC 2020 and the uninstall option is ticked

So the behaviour I was expecting was that the 2020 version would be left in place until the user clicks to install for the 2021 version at which point 2020 would be uninstalled and 2021 installed. I am getting some reports that the 2020 version being removed even though no one has clicked to install the 2021 version . This behaviour did not happen when I was testing it so I am confused as to why its happening now.

If anyone knows of where I can find some documentation that describes the supersedence behaviour that would be great as the Microsoft Learn don't really cover scenarios as far a I have been able to find.

Microsoft Configuration Manager Application
Microsoft Configuration Manager Application
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Application: A computer program designed to carry out a specific task other than one relating to the operation of the computer itself, typically to be used by end users.
455 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amandayou-MSFT 11,046 Reputation points
    2021-10-20T07:25:03.42+00:00

    Hi @i8displaynames ,

    By default, the new deployment type doesn't uninstall the deployment type of the superseded application. This scenario is commonly used when you want to deploy an upgrade to an existing application. To remove the existing deployment type before the new deployment type is installed, select Uninstall. If you decide to upgrade an application, make sure that you test this in a lab environment first.

    And here is the similar scenario about using SCCM Application Supersedence:
    https://www.anoopcnair.com/sccm-application-supersedence/
    Note: Non-Microsoft link, just for the reference.

    And here is Microsoft explanation about this scenario:
    https://learn.microsoft.com/en-us/mem/configmgr/apps/deploy-use/revise-and-supersede-applications#specify-a-supersedence-relationship

    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.

    0 comments
  2. i8displaynames 6 Reputation points
    2021-10-20T08:04:00.013+00:00

    Thanks @Amandayou-MSFT

    I have seen those and have no problem with the configuration side. What they don't explain is when if ticked the uninstall takes place, is it

    1. When the new version is installed (what my tests showed)
    2. The next time the computer checks in
    3. Because the old version deployment is "Required" but superseded, when check in happens is it triggering the install of the new "Available" version
    4. Something else

    I am concerned that the old version will be uninstalled without the updated version being installed to replace it. It maybe that I have mis configured something but its hard to know exactly what without knowing expected behaviour