![]() ![]() In Deploy/App – create a legacy package – with install.cmd as your install package and uninstall.cmd as the uninstall command. The GUID would be the name of the install – located in the registry HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\Folders and look for your version of Adobe. The Uninstall.cmd script should contain: MsiExec.exe /X /qn **The 1.mst is the name of your custom file. ![]() ![]() The Install.cmd script should contain: msiexec /i AdbeRdr11000_en_US.msi /qn TRANSFORMS="1.mst" Adobe Reader MSP file for patching for that version.In the install directory include the following: I will talk more about these two scripts below. You will need to also create two scripts – Install.cmd and Uninstall.cmd. Remove messages and notifications about upgrades.Download the Adobe Customization Wizard, and create a custom MST file. MSI file and data1.cab into your install directory. MSI for Adobe Reader if you have not done so already. This would keep everyone on the same version, and when a real major update is available, everything can be easily uninstalled. So here at Specops, we recommend treating each update as a major update. That would be cumbersome for desktop management. If each update is handled separately in Specops Deploy / App, installing the next major version (for example going from Adobe Reader 11 to Adobe Reader DC) would require you to un-deploy each and every update. How do you manage it? I turned to my colleague Johan and sought his advice on the best practices. A customer recently asked me: What is the best way to handle all of the numerous Adobe updates? After the initial install, updates may be required quite frequently. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |