JAMF releases CS6 deployment doc...SOUP's DONE! :D:D:D

donmontalvo
Esteemed Contributor III
1 ACCEPTED SOLUTION

acdesigntech
Contributor II

unfortunately my company :(

But since now that I am 100% in charge of the entire Mac space across the globe... :D

View solution in original post

20 REPLIES 20

tkimpton
Valued Contributor II

Thanks for that :)

donmontalvo
Esteemed Contributor III

FYI, page 9 includes an unfortunate limitation...

Important: Do not use the deployment instructions in this guide if the master distribution point in your JSS is an SMB share. Instead, use the deployment instructions in the following Knowledge Base article: http://jamfsoftware.com/kb/article.php?id=305

The meat & potatoes starts on page 11...Serializing Adobe CS6...

--
https://donmontalvo.com

timsutton
Contributor

Page 4 of Adobe's AAMEE deployment guide 3.0:

The Application Manager does not support NFS or SMB.

tkimpton
Valued Contributor II

Following http://www.jamfsoftware.com/libraries/pdf/white_papers/Administering-Adobe-Creative-Suite-6-with-the-Casper-Suite.pdf

Using an afp share

selecting "This package must be installed to the boot volume at imaging time checkbox and click OK." in Casper Admin

Adding to the config

imaging test machine with the config

Installation Fails!

tkimpton
Valued Contributor II

only thing ive found that works it this and scoping for machine receipts of CS6 and a dummy receipt. Deploying through ARD etc doesn't work and so i can just push out a dummy receipt and recon the machine :)

https://jamfnation.jamfsoftware.com/article.html?id=161

stibebu
New Contributor II

Granted, I only had 1 user who needed it so far... but I was able to use AAMEE 3 to package a serialized copy of Adobe Illustrator, without having to take the next step of "serializing Adobe CS6".... Worked great... am I missing something?

music5_5
New Contributor

Hi All,

Do you have to have Casper Suite for CS6 deployment or can I use this Casper Imaging as well?

In past, I have just uploaded the Adobe DMG file to JSS server and then Casper Admin to create new adobe installation which worked without any problem.

Would I be able use the same steps?

Thanks,
Raj

donmontalvo
Esteemed Contributor III

If you're deploying at imging time, AAMEE 3.0 produced packages should work fine. I'm holding off until AAMEE 3.1 is released, since we lost a few features (can't include updates, not backward compatible with 5/5.5, etc.), 3.1 will reintroduce the features.

If you're "baking in" CS6 on a monolythic image, you'll need to install in Trial mode, and serialize after imaging the Mac. But who uses monolythic images anymore anyway...

Don

--
https://donmontalvo.com

acdesigntech
Contributor II

unfortunately my company :(

But since now that I am 100% in charge of the entire Mac space across the globe... :D

donmontalvo
Esteemed Contributor III

@acdesigntech Congratulations, I'm sure you're gonna show them how it SHOULD be done! :D

--
https://donmontalvo.com

PeterClarke
Contributor II

I thought I had resolved my CS6 issues…

Seems to install OK if I reinstall Casper Client
– But when I try to install via a POLICY it errors out saying that it's trying to install at the root level "/"

Interesting that I DO get that with a Policy, but NOT with an Casper-Client install pull
- This seems to point to some bug in Casper ?

The LOG output specifically refers to "/" where as the AAMEE 3 setting was "Default Location"

I had the same result yesterday when I chose Custom an "/Applications" as the destination -- Policy Log said "/" as the destination & it failed…

Is Casper somehow mis-interperting the destination ?

So CS6 install via POLICY - does NOT seem to work…

Any Suggestions as how to resolve ?

tkimpton
Valued Contributor II

I think its a Casper bug. I noticed a while back when on some of my machines weird folders and files related to extracted Pkgs were on the top level of the disk! You are not alone in this weirdness!

TSOAFTVPPC
Contributor

Is anything different with the instructions now that aamee 3.1 beta is out?

ryanhollitz
New Contributor

I am still having issues. I have repackaged with AAMEE 3.1 and still can't deploy during imaging.

greatkemo
Contributor II

Hey Guys,

In this document http://www.jamfsoftware.com/libraries/pdf/white_papers/Administering-Adobe-Creative-Suite-6-with-the... on page 13 step 9 it says to add this command

/Library/Application Support/JAMF/Adobe/AdobeSerialization adobe_prtk --tool=VolumeSerialize --provfile=/private/tmp/prov.xml

Has anyone tried adding this line to the serialization package as a postscript? and did it work?

Kamal

rmaldonado
New Contributor

Hey All--

I am having some minor trouble getting the package I've created with AAMEE to deploy correctly. I have followed the instructions, and read all of the tips and tweaks on this page, but to no avail. I am currently testing it as a Self-Service item, and when I attempt installation the logs show this:

/usr/sbin/jamf is version 8.62
Executing Policy CS6 Adobe Design and Web Premium...
[STEP 1 of 3]
Mounting afp://myshare/Casper to /Volumes/Casper 2...
[STEP 2 of 3]
Copying AdobeDesignWebPremium_CS6[AFP]...
Installing AdobeDesignWebPremium_CS6[AFP]...
Installation failed. The installer reported: dyld: DYLD_ environment variables being ignored because main executable (/System/Library/PrivateFrameworks/Install.framework/Resources/runner) is setuid or setgid
installer: Package name is AdobeDesignWebPremium
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.)
Unmounting file server...
[STEP 3 of 3]
Running Recon...
Locating mobile device records...

Does anyone know if I am missing something easy? I wasn't able to fully understand exactly what this error was telling me. If anyone could shed some light that would be awesome :)

bentoms
Release Candidate Programs Tester

rmaldonado
New Contributor

Thanks for answering so quickly @bentoms unfortunately I am still receiving the same error, after caching.

/usr/sbin/jamf is version 8.62
Executing Policy CS6 Adobe Design and Web Premium...
[STEP 1 of 4]
Mounting afp://10.109.0.100/Casper to /Volumes/Casper 2...
[STEP 2 of 4]
Caching package...
[STEP 3 of 4]
Installing AdobeDesignWebPremium_CS6.pkg...
Installation failed. The installer reported: dyld: DYLD_ environment variables being ignored because main executable (/System/Library/PrivateFrameworks/Install.framework/Resources/runner) is setuid or setgid
installer: Package name is AdobeDesignWebPremium
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.)
Unmounting file server...

Any other ideas?

Thanks again for the link to this page for more resources.

donmontalvo
Esteemed Contributor III

@rmaldonado I've seen this error when uploads via Casper Admin failed (corruption?). Have you tried re-uploading the AAMEE package again?

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.)

Since this is an AAMEE installer issue, might also want to post at the AAMEE forum where the Adobe engineers monitor and respond fairly quickly:

http://forums.adobe.com/community/download_install_setup/creative_suite_enterprise_deployment

--
https://donmontalvo.com

rmaldonado
New Contributor

Thanks @donmontalvo, sorry for the late reply.

So basically it all boiled down to a corrupt package. We have an SMB share set as our master distribution point(hopefully changing this soon), and have that replicating to our 2 other AFP shares. To determine this, I just mapped to the AFP share manually, copy and pasted the CS6 pkg in there first, then copied it from there over to the master distribution share so that I could create a policy, and finally flipped the option within the policy to force it to always look to the AFP share. Ultimately this solution is working in the mean time until we can get our master distribution point changed to AFP. Thanks for the help and resources you provided for me to get this resolved for the immediate need!