Question

Adobe CC (creative Suite) june 2015 Fails

Forum|Forum|10 years ago
June 16, 2015
68 replies
268 views

DeployAdam
Contributor

Hi Folks,

We try to deploy the Adobe Creative Cloud Package, created with Adobe CCP Creative Cloud Packager. When the package is created we upload it to the JSS with Casper Admin. Then we use a policy to install the package on the clïents.

We never managed to install the package. Neither through direct install nor cache package and then install package. Also we tried to add the package to a DeployStudio workflow with the same error:

Installation failed. The installer reported: installer: Package name is adobecc_nl_16062015
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.)

If we login as localadmin on a 10.10 machine and run the package locally everything works fine and the whole suite is installed correctly. We have tried every possible way we could think of to make this work. Hope the community has some experience and tips for helping us on this matter.

Forum|pagination.label 1 / 3

+14

Aziz
Contributor
Forum|Forum|10 years ago
June 16, 2015

I received the same error whenever a user is not logged on.

Basically, Adobe CC apps require someone to be logged in. Either using Casper Imaging (logs into 'Adobe Temp Account') or deploying during login.

+12

lunddal
Contributor
Forum|Forum|10 years ago
June 16, 2015

For Adobe installers, see here: https://jamfnation.jamfsoftware.com/article.html?id=161

That procedure works for CC 2015.

+12

sean
Contributor
Forum|Forum|10 years ago
June 16, 2015

I use the CCP to create a pkg and then just upload that to our deployment server. Install at login window with no user logged in works fine. Haven't tried 2015 yet.

Note: I'm using Absolute at the moment, but this should make no difference to deployment.

What happens if you run it as root from the command line with a verbose output. You could do this over ssh without a need to have anyone logged in.

installer -verboseR -pkg /path/to/installer.pkg -target /

In fact, here is a picture of our already deployed 2014 being updated by our internal Adobe Software Update Server using the RemoteUpdateManager as part of a script run when the loginwindow is started after a user logs out.

DeployAdam
Author
Contributor
Forum|Forum|10 years ago
June 17, 2015

Thanks for thinking along guys. Installing in a student environment at login would not be an option for our organization. Using RemoteUpdateManager worked for us and I guess will still work but we first have to get Adobe CC on the machines in order to update them remotely.

We have over 2000 Apple devices being deployed wit only a basic OS X installation and a binary. Than we need to get Adobe CC on there somehow. (we could try integrating the installation in our image but obviously prefer to deploy separate from it.

+10

etippett
Contributor
Forum|Forum|10 years ago
June 24, 2015

@DeployAdam Did you ever have any luck with this? I am having issues installing CC2015 at the login window, just like @Abdiaziz reported. It worked fine with CC2014, so I'm a bit disappointed (but sadly not surprised) that Adobe has taken a step backwards in deployment flexibility. @sean Did you ever confirm with 2015 that you can install at the login window?

My workflow uses DeployStudio to install Casper on the computer and set a first boot script to call a custom Casper trigger. The CC2015 policies are scoped to this trigger. The same policies work fine if someone is logged in.

Thanks,
Eric

DeployAdam
Author
Contributor
Forum|Forum|10 years ago
June 24, 2015

@etippett check my post on the DeployStudio forum. Let me know if it helps...

package build with ccp fails with deploystudio

+10

etippett
Contributor
Forum|Forum|10 years ago
June 24, 2015

@DeployAdam Hmmm...That's interesting. So the second time you run the install it reports successful? I have to admit, it makes me a bit nervous using that sort of a workaround. I may just pursue a way to run it once someone is logged in.

I'm also reaching out to my Adobe technical account rep, so I'll let you know if I hear anything from him.

DeployAdam
Author
Contributor
Forum|Forum|10 years ago
June 24, 2015

I most certainly agree with you that we shouldn't be needing a workaround and that Adobe should make deployment and managing packages created with ACCP more seamless. But until then we have to be creative in finding solutions to deploy this beast. For us it wasn't thinkable to install while a student is logged in so we had to come up with this workaround.

Please share your findings when you received information from your Adobe tech rep.

mdonovan
Contributor
Forum|Forum|10 years ago
June 24, 2015

note: I've not yet tried deploying the new CC 2015 packages as I only updated all our packages with CCP (CreativeCloudPackager) yesterday, however the below is what has worked for me up until now. Hopefully it may contain something that may help.

As per the above instructions from @lunddal, once CCP has completed pulling down the software, I open Disk Utility and create a .dmg of the .pkg file that CCP has created. I then add this .dmg to Casper Admin, create a policy to cache install the .dmg and then add the installPKGfromDMG.sh script to execute the .pkg inside the .dmg.

From memory, it is important to not change the names of any of the files once they are created, and to also feed the correct .dmg name into the Parameter 4 field when adding the installPKGfromDMG.sh script to the policy.

One 'trick' I think I had success with was to be consistent with not having any spaces or non-standard characters in any file names or directory paths, including as far back in the process as typing the package name in the Package Details window within CCP.

This will also ensure you can go back to the package in the future and edit/update it with CCP without generating the 'this package is corrupt error'

@Abdiaziz I don't believe the machines have to be logged in for this to work. I think that only applies when deploying/updating Adobe AIR.

+14

Aziz
Contributor
Forum|Forum|10 years ago
June 25, 2015

@mdonovan

I've never had success deploying five or more packages without someone logged in, it always fails with "Installer can't find /. Please contact the software manufacturer.". I also don't deploy Air or the extra components and have it set to ignore conflicts.

Imaging wise at least, I do the following:

1) Set up smart group for a specific classroom (ex: blue room: Computer make like blue00)

2) Make a policy that has a recurring check in. The policy includes Adobe CC 2015 and any other applications requested by the professor

3) During the imaging stage when the machine is on the 'Casper is installing software", the machine checks in with the JSS and kicks that policy off.

90% success rate. Occasionally the installer failed with a generic message like "Installer can't find /. Please contact the software manufacturer." But I also get the same message when using the InstallPKGfromDMG script (I followed the instructions, no name changes).

Any better suggestion? I hate using this method.

+12

sean
Contributor
Forum|Forum|10 years ago
June 25, 2015

Did anyone try installing from the command line whilst at the login window to see what was output on a machine that was failing?

@etippett I have done a couple of tests with 2015 and each time I have had a completed install whilst at login window.

I too have: Disable Air, Ignore conflicts

Only tested with InDesign and Photoshop so far. Are the issues so far the same for all, fails to install?

+10

etippett
Contributor
Forum|Forum|10 years ago
June 25, 2015

I'm using the same method as @mdonovan since we're working off of an SMB share the extra DMG steps are necessary. @Abdiaziz are you working off a JDS instance and therefore not having to wrap the CCP-created PKG in a DMG?

As for the issues with naming the DMG, etc, that's because the installPKGfromDMG script has issues handling spaces. I started working on a fixed version of the script once but never finished it; I just name all my DMG's properly to start with. That's not the issue I'm having in this instance, but thanks for pointing it out nonetheless as it certainly may trip others up!

@sean My package is the entire suite (all 13.5 GB of it!) so perhaps it's an app other than Photoshop and InDesign that is causing the issue. Apparently all of the apps are developed by different teams and their installers work in different ways (hooray!). I have AIR disabled, conflicts ignored, Creative Cloud Desktop disabled, updates controlled by IT. I've not tried manually running the install while at the login window to see what the output is (I don't believe the jamf binary or installer binary give much useful, though, probably just a "there was a problem installing the software, contact the manufacturer"), but I do have a capture of the log the installer generates. In case anyone isn't aware, this log is called PDApp.log (no idea why) and can be found in the currently logged user's ~/Library/Logs. If at the login window, that would be var/root/Library/Logs. The log is 1500+ lines long, so I won't post the whole thing here. However, here are the lines I think are important, from the first error to the end when it stops:

06/24/15 14:35:20:124 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 42342 | STEP 3: Starting to launch Bootstrapper of Media (APRO15.0en_US).
06/24/15 14:35:20:134 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 42342 | The Bootstrapper seems to be missing(/Volumes/CreativeCloud2015_FULL_Install/CreativeCloud2015_FULL_Install.pkg/Contents/Resources//Setup/APRO15.0en_US/Install.dylib/Contents/MacOS/Install). Skipping the installation process.
06/24/15 14:35:20:134 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 42342 | Correcting Dependencies in local db.
06/24/15 14:35:20:134 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 42342 | STEP 4: Starting to launch Adobe Installer.
06/24/15 14:35:20:134 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 42342 | Obtained Adobe Common Folder Path.
06/24/15 14:35:20:134 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 42342 | Adobe Installer launch location is :: /Library/Application Support/Adobe/OOBE/PDApp/DECore/Setup.app/Contents/MacOS/Setup
06/24/15 14:35:20:134 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 42342 | deploymentFile = (/tmp/16479552-1A76-4E59-BCB6-32CDE4F4BE9E//1B88A37F-95F2-4C60-A43A-644DB4DE5B5D), installSourcePath = (/Volumes/CreativeCloud2015_FULL_Install/CreativeCloud2015_FULL_Install.pkg/Contents/Resources//Setup/APRO15.0en_US)
06/24/15 14:35:20:153 | [INFO] | | ASU | DeploymentManager | AAMEEUtilities | | | 42342 | Launch Process With Task 06/24/15 14:35:54:425 | [INFO] | | ASU | OPM | OPM | | | 46819 | Build Version - 9.0.0.0
06/24/15 14:35:54:425 | [INFO] | | ASU | OPM | OPM | | | 46819 | Logging Level verbosity Set to 4
06/24/15 14:35:54:447 | [INFO] | | ASU | OPM | OPM | | | 46819 | Schema version and schema compatibility version are same or greater than current

06/24/15 14:40:26:155 | [INFO] | | ASU | OPM | OPM | | | 42342 | _opm_handle_OPDReturnedStatus called with opdStatus as:0
06/24/15 14:40:26:155 | [INFO] | | ASU | OPM | OPM | | | 42342 | No Record found for the input fields in opm_getValueForKey
06/24/15 14:40:26:155 | [INFO] | | ASU | OPM | OPM | | | 42342 | Released OPM refrence successfully in opm_freeLibRef
06/24/15 14:40:26:169 | [INFO] | | ASU | DeploymentManager | | | | 42342 | Event Guid generated is: 'f3c2cdb8-5651-47d9-bfeb-e03bebef2ea5'
06/24/15 14:40:26:387 | [INFO] | | ASU | DeploymentManager | | | | 42342 | Waiting for the async thread to get the task completed
06/24/15 14:40:26:419 | [INFO] | | ASU | DeploymentManager | | | | 48697 | Async thread is completed. Now exiting from function.
06/24/15 14:40:26:520 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 42342 | The install workflow is terminating.

+14

Aziz
Contributor
Forum|Forum|10 years ago
June 25, 2015

@etippett

I'm using HTTP on an SMB/NTFS share hosted on Windows Server 2012R2. I have no problem whatsoever besides deploying when someone isn't logged in. Half of the packages using installfromPKGtoDMG script fails for me even when I hardcode the DMG name (no spaces or special characters).

The error in question:

Downloading http://xx.xx.x.x/CasperShare/Packages/AdobeFireworksInstall.pkg.zip...
Installing AdobeFireworks...
Installation failed. The installer reported: installer: Package name is AdobeFireworks
installer: Upgrading at base path /
installer: The upgrade failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

+10

etippett
Contributor
Forum|Forum|10 years ago
June 25, 2015

@Abdiaziz Hmmm that's a bummer. InstallPKGfromDMG has been pretty solid for me so long as I'm careful with the DMG names. Are there spaces in the name of the mounted volume? I've seen that cause problems too.

+14

Aziz
Contributor
Forum|Forum|10 years ago
June 25, 2015

@etippett

None of all, for example:

Adobe InDesign would be = .pkg > AdobeInDesigninstall.pkg > DMG > AdobeInDesigninstall.dmg

+10

etippett
Contributor
Forum|Forum|10 years ago
June 25, 2015

@Abdiaziz Right, but what I'm asking is the name of the volume that shows up when the DMG is mounted.

+10

etippett
Contributor
Forum|Forum|10 years ago
June 25, 2015

@DeployAdam FWIW I tested using the 'chmod -R 755' method also mentioned in the DeployStudio thread you linked and didn't have any luck. I think I'm just going to drop a dummy receipt on the systems during their first boot after imaging that will put them in a smart group to scope a policy to install CC2015. If anyone else comes up with any fixes for installing CC2015 at the login window, please let me know.

Thanks,
Eric

+12

sean
Contributor
Forum|Forum|10 years ago
June 26, 2015

As said, I'm using the pkg that CCP creates, I'm not in a position of having to wrap it as a dmg and this is working. I also notice that the script has an error:

I'd suggest that:

# Verify Variables
verifyVariable dmgName

should read

# Verify Variables
verifyVariable $dmgName

Otherwise, try copying the dmg directly to a machine instead of using Casper. ssh into the machine, run the '/usr/bin/hdiutil mount' command against this dmg and then try using the 'installer' command as posted above instead of using the jamf binary to install the pkg.

Does this work or not? If not, does the verbose output provide any extra information regarding the fail?

Try just running sections of the script, e.g.

mountResult=`/usr/bin/hdiutil mount -private -noautoopen -noverify [/path/to/dmg] -shadow`
echo "$mountResult"
mountVolume=`echo "$mountResult" | grep Volumes | awk '{print $3}'`
echo $mountVolume
mountDevice=`echo "$mountResult" | grep disk | head -1 | awk '{print $1}'`
echo $mountDevice

packageName=`ls $mountVolume | grep "pkg"`
echo $packageName

Do the echo commands give the results you expect?

If you are concerned about spaces, the script doesn't need much amendment. First, make sure you "quote $4 the dmg name" you are passing to the script and then try the following. Note, I do not have Casper so I can't fully test this. Personally I'd change it to a bash script and not sh.

####################################################################################################
#
# SCRIPT CONTENTS - DO NOT MODIFY BELOW THIS LINE
#
####################################################################################################

# Verify Variables
verifyVariable "$dmgName"

# Mount the DMG
log "Mounting the DMG $dmgName..."
mountResult=`/usr/bin/hdiutil mount -private -noautoopen -noverify /Library/Application Support/JAMF/Waiting Room/"$dmgName" -shadow`                 
mountVolume="/"`echo "$mountResult" | grep Volumes | cut -d "/" -f 4-`
mountDevice=`echo "$mountResult" | grep -m 1 disk | awk '{print $1}'`

if [ $? == 0 ]; then
        log " DMG mounted successfully as volume $mountVolume on device $mountDevice."
else
        log "There was an error mounting the DMG. Exit Code: $?"
fi

# Find the PKG in the DMG
packageName=`find "$mountVolume" -maxdepth 1 -name "*.pkg"`

# Install the PKG wrapped inside the DMG
log "Installing Package $packageName from mount path $mountVolume..."
/usr/sbin/jamf install -path "$mountVolume" -package "$packageName"

if [ $? == 0 ]; then
        log " Package successfully installed."
else
        log "There was an error installing the package. Exit Code: $?"
fi

# Unmount the DMG
echo "Unmounting disk $mountDevice..."
hdiutil detach "$mountDevice" -force

# Delete the DMG
/bin/rm /Library/Application Support/JAMF/Waiting Room/"$dmgName"

DeployAdam
Author
Contributor
Forum|Forum|10 years ago
June 26, 2015

We have managed to create a pretty straight forward Casper solution for this in our eyes a problem Adobe must look into. Apart from that...our solution:

Deployment by Casper:
In short, the ACCP created installer will be cached on the client and from there the script takes over and starts installing. When installing the first time the installer fails but the script takes over and starts the installer again and will finish as we like!

Create an Adobe CC Package with Adobe CCP packager
Copy the installer Package (found in the Build folder) into Casper Admin
Create a script in Casper first (see below post for script)
Create a policy which will first Cache this package on the local machine (default WaitingRoom folder)
Add the previously created script to this same policy and make sure it executes after the cache task

Presto!

#!/bin/bash

############################ bash_adobecc_installer_JAMF.sh ####################
# Created by Omar Lahmar : lahmar@glr.nl                                       # 
# 22/06/2015 Grafisch Lyceum Rotterdam                                         #    
# This script double executes the adobe cc package and negates the             #
# need for having a user that needs to be logged in for proper deployment.     # 
################################################################################

cd /Library/Application Support/JAMF/Waiting Room/
ls /Library/Application Support/JAMF/Waiting Room/ | egrep -i 'adobe' | egrep -i '.zip$' | xargs -I{} ditto -xk {} /Library/Application Support/JAMF/Waiting Room/
adobecc_installer=`ls /Library/Application Support/JAMF/Waiting Room/ | egrep -i 'adobe' | egrep -i '.pkg$'`
sudo installer -verboseR -pkg "$adobecc_installer" -tgt / | sudo installer -verboseR -pkg "$adobecc_installer" -tgt /
sleep 2
ls /Library/Application Support/JAMF/Waiting Room/ | egrep -i 'adobe' | egrep -i '.pkg|.zip|.xml$' | xargs -I{} rm -rf {}

+14

Aziz
Contributor
Forum|Forum|10 years ago
June 26, 2015

I've got it working by:

Create Packages using Adobe CCP
Wrap them in a DMG (file name=AdobePhotoshop2015.pkg = AdobePhotoshop.dmg)
Select "install on boot drive during imaging"
Create policy that caches and installs using installfromPKGtoDMG script.

+10

etippett
Contributor
Forum|Forum|10 years ago
June 26, 2015

@sean The issue is not with the function of installPKGfromDMG, at least not in my case. Casper is mounting the DMG and calling the package just fine; the error is being thrown by the package itself. Therefore I don't think running the installPKGfromDMG steps one at a time wouldn't prove very useful. There may be some advantage to trying to call the package directly with installer, but I believe that's what the jamf binary does anyway.

@DeployAdam Thanks for sharing.

@Abdiaziz Are you using this as part of a Casper Imaging workflow? That's the only time the option to "install on boot drive during imaging" should matter. I'm not using Casper Imaging, so unfortunately this won't help me. Also, are you only installing Photoshop? I'm installing the entire CC suite (all 15 or so apps), each of which has their own sub-installs that are called during the installation of the main CCP-created package. It's one of these sub-installs that is failing for me; based on the logs I included it's probably whatever "APRO15.0en_US" is.

If anyone is wondering, I've not heard anything from my Adobe rep. [sigh]

+22

mpermann
Valued Contributor
Forum|Forum|10 years ago
June 26, 2015

@etippett is the APRO15.0en_US the Adobe Acrobat Pro application installer? I wonder if you left that app out of a test install whether your installation would finish or not.

+10

etippett
Contributor
Forum|Forum|10 years ago
June 26, 2015

@mpermann Ha, that's so obvious! I must have been staring at this for too long in order to overlook that. Thanks for pointing it out. I'll try to test that at some point.

+10

etippett
Contributor
Forum|Forum|10 years ago
June 26, 2015

FYI just used scp to copy the package (not the DMG) to a computer that had no one logged in, then SSH'ed to it and installed the package via installer command (not the jamf binary). No difference; exact same error.

krusea
New Contributor
Forum|Forum|10 years ago
June 26, 2015

I've been trying to install the 2015 apps with Self Service. I made a package of all of the current apps and it always fails on Acrobat DC. I made a new package with everything but Acrobat DC and it works. I made a package of just Acrobat DC and it fails in Self Service and when I try running the installer from the desktop it also fails.

Forum|pagination.label 1 / 3

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded