Updating deployed SCCM Packages with supersedance

[Geoff]

The question is, should I bother? What's best practice here?

 

I have PSADT based SCCM Application Packages for Flash, Java, Adobe Reader DC, etc and due to the historic nature of some of the clients I had to write in some pretty complex uninstall routines in the pre-installation step of the PSADT script. So given that should I bother telling SCCM that the new version of Adobe is an upgrade of the old package or should I not bother and simply remove the deployments for the old one and push the new one out? Or should I supersede the old version with the new one?

[sparkeh]

According to MS, best practice is to use supercedence: https://technet.microsoft.com/en-us/library/gg682011.aspx

 

Generally I do unless its something awkward that doesn't like being upgraded or uninstalled by sccm.

 

With regards to Adobe Reader DC, as all updates are now cumulative, I just have an deployment for the base version and another for the latest .msp (with a dependency on the base version).

[Geoff]

Alright well I've just chucked out Flash 24.0.0.186 with supersedence so we'll see. Edited December 21, 2016 by Geoff