- #Id adobe fireworks cs6 serial number
- #Id adobe fireworks cs6 install
- #Id adobe fireworks cs6 serial
I would have expected it to say Not Installed, but not Update Available. However, after running Adobe updates on a machine, MSU (in optional updates) shows the package as Update Available.
On a clean install, this works correctly. Ideally munki would have seen that all the Apps in the Installs key were installed and show "Installed" in MSU.
#Id adobe fireworks cs6 install
To correct this, I generated the install keys using makepkginfo -file on a clean install and dumped this into a copy of the pkginfo for Adobe CS6 Master Collection and appended Test to the name so it shows up differently in MSU. "/Library/Application Support/Adobe/Licensing/adobe_prtk_cs6" -tool=Serialize -leid=Dreamweaver-CS6-Mac-GM -serial=12345678 -adobeid= CS5/5.5 packages are the same except for the arguments for the PRTK utility are different - see the PRTK documentation.Īny Adobe product that gets installed for CS6 is going to generate this, so like my previous problem, if I install just Acrobat Pro X, and then try to install Master Collection, munki thinks it is already installed.
#Id adobe fireworks cs6 serial
(d) Each CS6 package has a postflight to inject the serial number:
(c) Each of our CS6 packages requires the PRTK package in a requires array. (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.
#Id adobe fireworks cs6 serial number
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 kommentar(er)
