Adobe Creative Cloud Issues via Casper

Mitch260488
New Contributor II

Hi Guys,

Does anyone no of a fix for deploying a Creative Cloud Package via casper?

The package works fine, if you install locally, but once its uploaded to casper admin and deployed it will fail.

Thanks

Mitch

14 REPLIES 14

nessts
Valued Contributor II

I wrap the package that Adobe creates in my own package and install with a postinstall script.

Mitch260488
New Contributor II

Hi Nessts,

How did you do this?

Thanks

Mitch

stevewood
Honored Contributor II
Honored Contributor II

I've had no issues dropping CC packages into CA and deploying via policy. I'm running 9.21 and using a JDS for my distro point.

Do you have a log entry of the failure that you could share?

nessts
Valued Contributor II

you put the adobe created package into a folder drop that into packagemaker, then tell it to put that package somewhere like /tmp then the postinstall can do things like installer -target / -pkg /tmp/adobe.pkg and then i install the font management software after that. I tried using just the Adobe created package for CS6 and it worked something like 60% of the time, i started wrapping it and it worked 90% of the time. Most of my install issues were at imaging time as well. I tend to not let casper do the install on boot device and handle all of that myself now, of course i have some customers where i dont get to use casper so that is part of why i have to do it in the first place, but it failed often with Casper even so i just take care of it outside of Casper.

Mitch260488
New Contributor II

Executing Policy Adobe CC Dec 2013...
Mounting London (192.168.10.176) to /Volumes/CasperShare...
Copying Adobe CC Dec 2013_Install.pkg...
Installing Adobe CC Dec 2013_Install.pkg...
Installation failed. The installer reported: installer: Package name is Adobe CC Dec 2013 installer: Installing at base path / installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

Mitch260488
New Contributor II

These are the errors via Casper Remote

installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191

installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:
:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191

installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%10.553191
installer:PHASE:Running package scripts…
installer:%97.750000
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
Submitting log to http://192.168.10.176:9006/
Finished.

stevewood
Honored Contributor II
Honored Contributor II

Have you tried caching the installer to the machine first, and then triggering another policy to do the install?

Also, I've seen issues with Adobe installers when other Adobe apps are open. Perhaps trying this install at logout or login would solve the problem.

When we migrated from 5.5 to CS 6, I cached the installer onto user's machines, then had a policy set to trigger at Logout to install the cached installer. It worked like a charm for me, with maybe a 95% success rate. Most of the failures were people being impatient and unplugging their machines.

jwojda
Valued Contributor II

I've seen where the user has chrome and/or firefox open and it fails.

There;s a log file in /Library/Logs/Adobe/Installers/

http://helpx.adobe.com/creative-suite/kb/troubleshoot-install-logs-cs5-cs5.html

spalmer
Contributor III

As @jwojda][/url mentioned check the Adobe install logs. A couple of issues I have discovered by looking through the logs are:

Errors caused by System Requirements: Some Creative Cloud applications require 10.6.8 or later and some require 10.7 or later (see http://www.adobe.com/products/creativecloud/tech-specs.html). If you install one big package with all of the Creative Cloud applications some applications that require 10.7 will blindly install on a 10.6.8 system, but some will fail and cause all previously installed applications to be uninstalled. This appears to be related to Adobe's installers not properly preventing an application from being installed on an incorrect OS version.

Permissions Errors: I found an error similar to the following for several applications:

ERROR: DS011: Installer package might be corrupt. Re-download the installer and try again. (PDF Settings CS5 10.0.0.0 {84901376-1C55-4BD3-AD2C-F9BDB4449DAC}: payload not found in the payloads folder: /Library/Application Support/JAMF/Downloads/Adobe Creative Cloud_Install.pkg/Contents/Resources//Setup/Adobe InDesign CC_10/payloads/AdobePDFSettings10-mul/AdobePDFSettings10-mul.dmg)

I found there are four applications that have the AdobePDFSettings10-mul.dmg payload: Illustrator, InCopy, InDesign, and Photoshop. Creative Cloud Packager always creates the last three with incorrect permissions of rwxr--r-- on that dmg file. I matched the permissions on the AdobePDFSettings10-mul.dmg in the Illustrator installer package rwxr-xr-x and now it works. The strange thing is this only fails when installing from Casper. If I push the packages via Apple Remote Desktop it works fine.

The other downside with this is that you need to remember to correct these permissions every time you recreate these packages with the Creative Cloud Packager 1.x. I also believe that I saw this same permissions issue when creating Creative Suite 6 packages with AAMEE 3.x.

Cook
New Contributor II

From memory quit out of all applications open and the installer should work. May require a self service or casper remote message to inform the client to quite all apps before deployment.

RobertHammen
Valued Contributor II

Typically when you see the install hang or fail, it's because the option in Creative Cloud Packager to ignore conflicting processes hasn't been selected.

Early versions of CCP either didn't properly set this, or the Acrobat XI installer ignored them, because I had issues with deploying CC initially. No problems with this since CCP 1.3 and later.

Also note, if any of your distribution points are on Windows, you need to wrap the .PKG that CCP creates in a DMG, cache said DMG, and use the InstallPKGfromDMG script to actually get the work done...

SIXfoot5ins
New Contributor II

I agree the @RobertHammen.
Wrapping the pkg in a dmg to cache & install with the script, always done it this way due to the size of the pkg and to improve reliability

spalmer
Contributor III

Just an FYI, if you are on Casper 9 and have migrated your scripts and packages there is no longer a need to wrap CCP or AAMEE created packages in a DMG when using non-AFP shares. When migrated all existing non-flat packages will be zipped and any new ones will now be zipped automatically when uploaded via Casper Admin.

See https://jamfnation.jamfsoftware.com/article.html?id=327 for more info.

bgreeno
New Contributor III

Also, make sure that any updates are not included with the package. It would fail every time for me when updates were included, but when I packaged the applications by themselves the installs work perfectly every time. Hope this helps.