Hello,
Last year, I initially created Adobe Reader 11.0.08 as an application which has successfully been deployed to the majority of our fleet of workstations. We have now decided to upgrade to 11.0.12 (instead of the Document Cloud version) for security compliance.
I have created an application for 11.0.12 which is setup to successfully upgrade over v11.0.08 (with supersedence). There is a mechanism to remove the odd v9.x & v10.x versions still installed which also works well.
The problem I am experiencing are the other 11.0.X versions installed across our fleet (I have identified using a combination of reporting and asset compliance settings). Supersedence I believe is only designed to remove and replace an application that you have packaged into CM12 - correct me if I am wrong.
Does anybody have any recommendations on how to tackle the upgrade of other 11.X versions installed in a simple manner? The 2 ideas I have come up with are to either script the application to run an uninstallation first OR create slipstreamed versions of each Adobe Reader 11.x version and include in the supersedence (I would prefer using native SCCM features which work really well in our environment).
Thanks, Amiel