In many projects I design and implement SCCM 2012 Site infrastructures. Most organizations are looking to optimize Operating System Deployment and Patch Management. In some cases, an existing SCCM 2007 Site infrastructure is already deployed. Migration strategies are developed to migrate all clients from SCCM 2007 to SCCM 2012.
The new feature used for application management is somewhat challenging for most administrators, especially if they already have a lot of Packages created in SCCM 2007. They tend to keep using this method in SCCM 2012 as well, but they’re missing a lot of comprehensive features Application Management provides.
This blog provides a nice feature of Application Management: superseding applications…
Superseding applications allows administrators to do the following:
- Replacing an older application with a new version
- Replacing an application by a different application of a different vendor
This blog demonstrates superseding Adobe Reader X with Adobe Reader XI. In this example, I downloaded the standard MSI files of both versions (10.0.0. and 11.0.0.). No customizations are used since the demonstration focuses on the installation of both versions.
Two applications have been created, one for each version. Since the installations are MSI, SCCM 2012 will configure the applications automatically and no additional configuration is required.
Each application has a standard deployment to a client machine, both are set as Available deployments.
Adobe Reader X is installed first, nothing special so far.
In order to have Adobe Reader XI installed and Adobe Reader X uninstalled first, I created a Supersedence in Adobe Reader XI first.
The screenshot shows that version XI supersedes version X, it will automatically uninstall version X before installing version XI.
Sidenote: it often happens that numerous versions of Adobe Reader are used as well. You can add these versions for as well to allow uninstallation of all previous versions so you maintain only one version of an application.
In the References property of version X, you can see that version X is superseded by version XI.
Once the supersedence is in place, you may want to stop any deployments of the superseded application. This can be done by deleting all deployments. Additionally, you might want to retire version X.
On the client machine, once the installation of version XI is started, it will automatically uninstall version X and install XI.
If the application is part of a Task Sequence, then you need to modify the Task Sequence with the new version…