![]() ![]() That’s it, your new version of Acrobat Reader DC will now perform a clean uninstall of any old version that you superseded. Also select “Uninstall” to make sure it uninstalls the superseded version. Make sure you chose your new deployment type, which is the deployment type of the new Acrobat Reader DC that you just created. Add the different Adobe Reader versions you want this to supersede. On your application (not deployment type), chose properties and supersedence. Making an application superseded does not mean that it will be uninstalled, it needs a deployment of the actual application superseding it before it is uninstalled. Uninstall of the old version of Adobe reader will only happen when the device or user is hit with the deployment of the application superseding the old one. ![]() When you supersede a previous version of Acrobat Reader, the superseded version will be uninstalled before the new version in installed. Step 3 – Supersed old version of Acrobat Reader If not you can’t separate the different versions and you will have problems superseding old versions of Acrobat Reader. It is important to set the MSI version as detection method and not just the product code. Use windows installer as detection method and read the product code and MSI version from AcroRead.msi. Install string: Setup.exe /sALL /rs /msi EULA_ACCEPT=YES.Use 7-zip to extract the downloaded file so you get the actual installation files. ![]() Donwload an offline installer of Acrobat Reader DC from Adobe:.It also supersedes old versions of Adobe Acrobat Reader to make sure they get uninstalled before we install the new version. The installation will be unattended and silent as every good SCCM deployment should be. How to deploy Acrobat Reader DC with SCCM using the application model. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |