You can see this using pkgutil -pkgs | grep -i. However, Acrobat DC does install a number of receipts which list all of the files it brings along for the ride (all 10696 of them!). Note: Creative Cloud Packager has now fixed Uninstalls for Acrobat DC since v17.0ĭespite Creative Cloud Packager helpfully providing an uninstaller package, it doesn't actually function properly - it won't actually remove Acrobat Acrobat Pro DC. Applications/Adobe Acrobat DC/Acrobat Distiller.appĪt least now there's a useful version number (in this case "15.007.20033"), which can replace the "1.0.0.0 - please edit me!" version that munkiimport tried to guess. Use makepkginfo -f /Applications/Adobe\ Acrobat\ DC/Adobe\ Acrobat.app -f /Applications/Adobe\ Acrobat\ DC/Acrobat\ Distiller.app to generate an installs array and useful version number: These examples below may vary as version numbers are updated, but the process will generally be the same.Īcrobat Pro DC installs two applications, "Adobe Acrobat.app" and "Acrobat Distiller.app" (and a shortcut to its uninstaller, contained inside the "Adobe Acrobat.app"). Thus, these products need installs arrays. They also don't provide useful version numbers - munkiimport will automatically pick "1.0.0.0 - Please edit me!" because it can't find a better option. Specifically, Adobe Acrobat Pro DC, Edge Code, Edge Reflow, GamingSDK, Lightroom 5, and Scout do not generate useful data about their install, which will cause Munki to loop these installs endlessly. However, some of the Creative Cloud packages don't contain useful information inside that can generate a sane version number, and some of them don't generate the typical Adobe installs key, due to the way Creative Cloud Packager packages them. Using munkiimport above with the correct -uninstallpkg switch will produce a working Munki install (and removal) for most of the products. Note: several of these issues were fixed with the release of Creative Cloud 2015. munkiimport_cc_installers.py /path/to/CCPackages You can import a specific package into Munki using munkiimport: If you plan to include updates in the main packages, you should first read the note on including updates in the main CCP install packages in the aamporter section towards the bottom. You can use Creative Cloud Packager to create an installer package for each separate product, or any groups of products. Make specific changes to some pkginfo files to accommodate problematic Adobe package behavior.Īs of March 2015, Adobe Creative Cloud Packager lists 23 separate products. Import the Creative Cloud Packager's Install package and the Uninstall package for each product. Use Adobe's Creative Cloud Packager to package your Adobe CC product. The workflow is similar to that for CS5 and CS6 applications packaged with AAMEE. Munki can install Adobe CC deployment packages generated with Adobe's Creative Cloud Packager tool. Info on installing and removing Adobe Creative Cloud products with Munki.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |