The Application Model in the real world: Supersedence.

January 6, 2015 at 3:27 pm in CM12, CM12 R2, ConfigMgr, SCCM by Kurt Depre

Hi all,

As you will see in my future posts, I’m a big fan of the application model in ConfigMgr 2012. The AppModel offers several interesting features to deploy your applications to your clients. In this blog post I want to cover 2 scenarios enabled by one specific feature of the application model: Supersedence

What is supersedence?

TechNet describes it as follows: Application management in Microsoft System Center 2012 Configuration Manager allows you to upgrade or replace existing applications by using a supersedence relationship. When you supersede an application, you can specify a new deployment type to replace the deployment type of the superseded application and also configure whether to upgrade or uninstall the superseded application before the superseding application is installed.

Supersedence can be very useful when you have an application that replaces an older version or another application that is already deployed. Below you will find 2 examples on how we used supersedence at a Customer

Note: supersedence does not work within task sequences.

Automated uninstall of the previous version of a software

Often when upgrading an application to a new version you first want to uninstall the previous version if it’s present. This can easily be done using supersedence.

Below you find a simplified flow of how supersedence will work to uninstall the previous version of an application or maybe an application that is being replaced by another.


How to set it up?

1. Find your Old & new App (in this Example Flash 13 (old) & Flash 14 (New))


2. Edit your new (superseding) application, go to the supersedence tab and click Add…


3. In the Specify relationship dialog click Browse…


4. Search for your old application. Select it and click OK


5. In the Specify Supersedence relationship choose which deployment type that replaces the ones from the old Application and check the Uninstall checkbox

Note: the uninstall command needs to be filled correctly on the application that is being replaced.


6. Verify that everything is set correctly and click OK to save your changes


7. Create a deployment of the new Application

8. Watch the old Application being uninstalled and the new installed

The Side-by-Side upgrade.

Sometimes you want to replace an application but not immediately upgrade all existing installations (maybe this will be done at later time). So you want all new installations to be of the new version. One option is to target a separate collection but this can bring overhead. Another option that I prefer is using supersedence. In the example below we want to replace Google Chrome by Firefox. So for now existing chrome installations will remain but all new requests will receive Firefox instead.

Below you find a simplified flow of how supersedence will work for the “Side-by-side” scenario


How to set it up?

Note: It’s assumed that the previous version/Application is already deployed to the Target collection.

1. Edit the New Application, go to the supersedence tab and click Add…


2. On the Specify supersedence relationship dialog click Browse…


3. Find the application that is being replaced, select it and click OK


4. Specify which Deployment type will replace which one from the superseded application and click OK


5. Verify all settings on the application page (uncheck the checkbox allowing users to see multiple deployments of superseded apps if you are working with Available deployment and the Application Catalog’’) and Click OK to save your changes.


6. Create a deployment to the same collection as the superseded Application for the new App and verify that both deployments are present


7. Sit back and let the magic happen.

8. Optionally when you are ready to upgrade the older apps just remove the Deployment and on the next Application Deployment evaluation cycle the application will be upgraded)

Till next time.