Has anyone managed to successfully build a package with Creative Cloud Packager and then deploy it with Casper? I can build a package that will install locally, but when I try to deploy it with Casper the installation stalls at 38% complete and then fails.

Do you have any "conflicting processes" open?

I was seeing the same with CS6 updates when logged in & running CS6 & Safari.

Try whilst logged in but running no apps.

http://tv.adobe.com/watch/creative-suite-in-the-enterprise/creative-cloud-packager-faq/

Conflicting Processes:
http://helpx.adobe.com/creative-cloud/packager/resolving-process-conflicts.html

Well so far it has been a bag of fail. The package build complete but the installers don't work. Guess I'm doing something wrong.

So even with ignore conflicting process on you must quit most apps for the installs to work properly. I also notice that in the app it gives you the option to sign into your account which has our main LWS/ELA email pre-populated. I hope that can be suppressed.

That sucks.

Please keep us updated.

We're part way through a CS6 rollout!

Been keeping an eye on CC, but as we're over 10 countries with around 250 creatives working for 12 brands... The licensing is messy!

@bentoms I totally understand we have the same issues due to the number of different brands and physical locations. I think what we got yesterday was the enterprise version. It's very similar to AAAME where you make the install package and serialize it or not and use trial versions. You also get the un-installers that we host in SS for upgrades. The CC Teams version looked like a lot of problems for enterprise.

Yea, the Creative Cloud Teams solution was never meant for Enterprise. Jody and Karl posted about the confusion at the Adobe OOBE blog...

http://blogs.adobe.com/oobe/2013/05/top-5-myths-of-creative-cloud-it-edition.html

Don

Yep teams is utter pants. Need to wait for the Enterprise release

http://twitter.com/donmontalvo/status/349314002674917376

@jnack @Adobe_ITToolkit @creativecloud @JAMFSoftware #whatever

"Hey, I just make the sausages." - Don Montalvo, TX

http://blogs.adobe.com/jnack/2013/06/more-than-700000-people-now-subscribing-to-creative-cloud.html#comment-86475

38% = you're trying to install AIR, or install with some conflicting process.

Note that, even if you tell CCP to ignore conflicting processes, if you include Acrobat in your deployment - whoops, it will puke! So I had to do two packages.

Also note the same issue with SMB shares and having to have the installer on a DMG, then cache the DMG and use a script to run it.

Also note 8.71 fixed a few issues with deploying AAMEE-created apps... so be sure you're on 8.71.

--Robert

...I can't believe Adobe is still incapable of producting PKG/MPKG installers that can survive SMB. :(

Don

I see some compression in your future....

@jhbush1973 DMG compresses the file and checksums it. Do you mean we should compress/zip/gzip the arcive...or...is Adobe going to blow us away with an option to spit out a compressed installer? :B

external image link

@bentoms wrote:

Conflicting Processes:
http://helpx.adobe.com/creative-cloud/packager/resolving-process-conflicts.html

Really? Shell? Shell is a conflicting process? Wow.

All the more reason to deploy only to logged off Macs. :)

Don

What I found was that the following pieces were the source of the permissions issue -
Contents/Resources/Setup/Adobe Photoshop CC_8/payloads/AdobePDFSettings10-mul/AdobePDFSettings10-mul.pkg
Contents/Resources/Setup/Adobe Photoshop CC_8/payloads/AdobePDFSettings10-mul/AdobePDFSettings10-mul.sig
Contents/Resources/Setup/Adobe Photoshop CC_8/payloads/AdobePDFSettings10-mul/Media_db.db

This terminal command fixed the permissions: sudo chmod -R 755 /pathto/package

Version 1.3 released today:

http://blogs.adobe.com/oobe/2013/10/creative-cloud-packager-1-3-is-live.html