Creative Cloud Packager - any experiences?

[RobertHammen]

About to go down this rabbit hole. I've used the Creative Cloud Packager (basically a new version of AAMEE) to build an install package.

Trying to run the package manually, even though I instructed it to ignore conflicting processes, the package failed, apparently when installing Acrobat XI, because Safari was open. D'oh! Quitting Safari and re-running the Installer worked (yeah I did check the /Library/Logs/Adobe/Installer on the failure).

I haven't yet tried to deploy this with Casper Suite, and wondering if anyone else has/if there are any other gotcha's...

--Robert

[RobertHammen]

BTW, here's the ReadMe - seems like a lot of "known issues":

http://helpx.adobe.com/creative-cloud/packager/ccp-readme.html

[donmontalvo]

You are a brave man.

...(snip)... ...(snip)... ...(snip)... Problem: Once AIR components are successfully installed, trying to reinstall them might result in failure. Workaround: Once AIR components are successfully installed, do not try to reinstall them. ...(snip)... ...(snip)... ...(snip)...

[RobertHammen]

Creative Cloud Packager is similar to AAMEE - more like the next version of the tool.

I'm well aware of the issues with AAMEE packages and SMB shares - was trying to deploy these over http (this particular client's server was Windows 2008R2). Also know it can be iffy to deploy these via first boot/after a reboot during imaging.

End result is both image and policy deployment did not install successfully. So did trying to cache the packages (over HTTP or overriding as SMB) and install.

Long story short, the old trick of putting the packages on a DMG, using the script linked from https://jamfnation.jamfsoftware.com/article.html?id=161 works, at least as a Self Service policy. Client is fine with doing it that way vs. imaging (ran out of time to get machines deployed).

One caveat, as mentioned above, even if you set the CCP options to ignore conflicting processes (i.e. web browsers), the Acrobat XI installer will actually fail or hang if a browser's open. So, I actually used Creative Cloud Packager to build 2 packages: one for Acrobat XI, the other for the rest of the Cloud products desired. Then, since this installation is being performed via Self Service, forced the user to read the description that explains that all browsers will be closed (and wrote a quick script that runs before installation to kill Safari/Firefox/Chrome).

The only way to currently obtain Creative Cloud Package or the nice new Adobe Update Server Setup Tool 3.0 is if you have a Team Admin login to the Creative Cloud site...