Umair Khan's blog

Sharing my experience with System Center Configuration Manager and Microsoft.

ConfigMgr 2012 – Application Supersedence behavior with Task Sequence deployments

ConfigMgr 2012 – Application Supersedence behavior with Task Sequence deployments

  • Comments 2
  • Likes


Hi Folks, Today’s post is brought to you by my colleague Senthil. This explains about how ConfigMgr Application Supersedence works in ConfigMgr 2012 Application Model.

To know the basics of Application supersedence you can follow –

http://technet.microsoft.com/en-us/library/gg682071.aspx


Recently we came across some scenarios where the Application supersedence causes the installation of the superseding applications without having any deployments targeted to the machine.

Just wanted to share this with you so that it helps in better understanding when you run into such scenarios.

The naming convention for the two applications is ‘Application A’ and ‘Application B’

Scenario 1:

- Application A - Deployed to a system and it installed A successfully.

- Application A is part of a Task Sequence which has been deployed to All systems Collection as Available. (Only to PXE and Media)

- Deleted the Application A deployment targeted to the client.

- Added Application B.

- Application B supersedes Application A. 

 Result:

 We triggered policy update on the client and the client didn't install the Application B.

Scenario 2:

- Application A - Deployed to a system and it installed A successfully.

- Application A is part of a Task Sequence which has been deployed to All systems Collection as Available. (ConfigMgr clients, PXE and Media)

- Deleted the Application A deployment targeted to the client.

- Added Application B.

- Application B supersedes Application A. 

Result:

We triggered policy update on the client and the client didn't install the Application B.

 Scenario 3:

- Application A - Deployed to a system and it installed A successfully.

- Application A and Application B is part of a Task Sequence which has been deployed to All systems Collection as Available. (ConfigMgr Clients, PXE and Media)

- Deleted the Application A deployment targeted to the client.

- Added Application B.

- Application B supersedes Application A. 

Result:

We triggered policy update on the client and the client installed the Application B.


Hope it helps!

Senthilkumar Pandurangan

Support Escalation Engineer Microsoft System Center Configuration Manager  

Disclaimer: This posting is provided "AS IS" with no warranties and confers no rights

  • Thanks

  • Thank you for this. But one question. What happend in "Scenario 3" when only Application B is part of a Task Sequence?

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment