question

i8displaynames-1265 avatar image
0 Votes"
i8displaynames-1265 asked Amandayou-MSFT commented

How does configuration manager application supersedence work

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 docs don't really cover scenarios as far a I have been able to find.

mem-cm-application
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Amandayou-MSFT avatar image
0 Votes"
Amandayou-MSFT answered Amandayou-MSFT edited

Hi @i8displaynames-1265,

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://docs.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.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

i8displaynames-1265 avatar image
0 Votes"
i8displaynames-1265 answered Amandayou-MSFT commented

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




· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

To remove the existing deployment type before the new deployment type is installed, select Uninstall. So the old application will be uninstalled, and the new application is installed, which happen on your side of test sccm, right?

I am getting some reports that the 2020 version being removed even though no one has clicked to install the 2021 version.

We could check AppEnforce.log to see if the 2020 version is uninstalled by sccm or other, and the reason the 2021 version is not installed, which records details about enforcement actions (install and uninstall) taken for applications on the client.

Best regards,
Amanda
0 Votes 0 ·

Thanks but that's not really answering the question I am asking, how to get something to uninstall is clear, its when it will happen that I am unsure of.

The 2021 version is deployed as available, so I want to know if the 2020 version will only uninstall when a user clicks install on the 2021 version or if it will uninstall automatically and leave the user without the software until they click install? More importantly I was hoping I could find some documentation that describes the expected behaviour of superseded applications with with uninstall selected without having to test all the many differing variations of deployment.

0 Votes 0 ·

Hi,

Based on my environment and test, 2020 version will only uninstall when a user clicks install on the 2021 version.

According to your decription, we could check the 2020 version is uninstalled by sccm or other fundamentally. By checking Event on the side of issued client, if the application is uninstalled by sccm, the user is System, if the application is uninstalled by user, the user is logon user.

The forum is an open platform for hearing different voices and suggestions to solve the problem.

Best regards,
Amanda

0 Votes 0 ·