(b) We have the Adobe PRTK utility as a munki package, called "AdobeProvisioningToolCS6" (a) We generated "trial" installers using the AAMEE tool. This is a long process to resolve, but it's getting there. To save disk space, we moved the serial number to postflights, which means we share the dmg but have different plists per business unit. We're in the process of migrating separate business units into one system management setup, so we have a hojillion different license codes for Adobe tools. Just wanted to mention that we do this as well. This would lead to behavior you implied: you install one package, and Munki thinks the other package is installed as well, since it's using the existence of the exact same item in both cases to determine installation status. If, however, you start with the CS6 Production Premium Suite and use AAMEE to build a pkg that installs only Photoshop CS6 and a second pkg that installs only After Effects CS6, munkiimport will essentially identify both packages as "CS6 Production Premium Suite" installs and will not distinguish between the two. Munkiimport's default behavior will work if you build an Adobe Photoshop CS6 installer using install media for Adobe Photoshop CS6, and an After Effects CS6 installer using media for After Effects CS6. I think I'm missing some detail here: are you using a CS6 Suite installer, and building packages that install different subsets of the applications in the suite? If so, yes, munkiimport's behavior here won't provide the needed installs array, and Munki then won't be able to distinguish between different packages built from a single CS6 Suite. I obviously fixed this using makepkginfo to find out the correct keys. By default, munki imports packages from AAMEE with a installs key pointing to the common Uninstaller. > As I continue to learn, I figured out the problem with trying to install different packages and why they would cause other to think they were installed. On Nov 8, 2012, at 9:23 AM, Harry Fike wrote:
0 Comments
Leave a Reply. |