- 1. Intro - Creating Superseded Applications in SCCM 2012 R2
- 2. Part1 - Creating the Application
- 3. Part2 - Creating the application supersedence
- 4. Part3 - Distributing Content
- 5. Part4 - Deploying the Content
Intro - Creating Superseded Applications in SCCM 2012 R2
Today I was investigating upgrading an application we use for email signature management called Symprex. I want to upgrade it using SCCM and realised that internally we didn’t have any “How-To” documentation on deploying an application from start to finish, so what better way to add a post to my blog and some internal documentation.
So, what is supersedence exactly?
Microsoft TechNet gives us a pretty good explanation:
“Application management in Microsoft System Centre 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.
When you supersede an application, this applies to all future deployments and Application Catalog requests. This will not affect the existing installations of the application.”
Taken directly from Technet
Supersedence can be very useful when and or if you need to upgrade applications, that have previously been deployed.
In this multipart post, I will show you exactly how to create an application, right through to viewing the final result.