Anyone deploying CS 5.5/6 at Imaging?

RobertHammen
Valued Contributor II

AAMEE-generated package being served from an SMB share, so we've put the package on a DMG and using the script referenced here:

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

Everything installs fine as a policy (cache DMG, run script after), so I'm confident that we've done this correctly.

Now, what about installing this at imaging time? I've created a new DMG which puts the installer into /Library/Application Support/JAMF/Waiting Room. That policy runs at initial imaging.

I've duplicated/renamed my installPKGfromDMG.sh script, and configured it to run At Reboot.

What happens at imaging time? The installer is cached HOWEVER the script never runs, and there's no errors in the Casper Imaging logs. Other scripts configured to run At Reboot are running.

Has anyone at JAMF ever tested this? I tried with 8.6x and currently 8.7x. Right now, doing a hack with dummy receipts, then running a policy that checks for the existence of the dummy receipt and runs the script, and that works, but it's extremely "hacky". This is something that Casper Imaging should be able to handle at boot time.

I realize CS5.5 is old, but the client will be updating to CC and AFAIK CCP has the same limitation with packages and SMB shares, so...

10 REPLIES 10

mscottblake
Valued Contributor

I've tried this as well as creating PKGs with the installation trigger in a postinstall script. Nothing I have tried will get it to install CS6 at imaging time.

CS6 takes my imaging from 10 minutes start to finish to 2 hours so I would love to find a solution.

donmontalvo
Esteemed Contributor III

Adobe has known for a couple/few years now that AAMEE installer PKGs have a problem with (read: don't survive on) SMB shares.

Adobe's CEO is too busy chasing Rupees to notice his development team are sleeping at the wheel.

Good thing we have Jody/Karl to *try* to steer Adobe's less-than-capable developers in the right direction.

"We market incompetence to save you money...er, to save us money...yea...that's it! Well, in any case, remember 'Creative Cloud' is the future! Bwahahahaha....cha-ching!!!" Adobe CEO

Don

--
https://donmontalvo.com

gregp
Contributor

We built the CS6 packages with AAMEE and they're installed during imaging.

Took the resultant pkg's from AAMEE and stuffed them right into Casper Admin (8.6). Set them to run after first reboot and haven't had a problem.

We NetBoot to do imaging and all of our dist points are AFP. However, I think this shouldn't be a problem if AFP or SMB is used at first reboot since it copies the packages from the dist point to the local HD, then installs it from there later on- it doesn't try to install direct from the SMB share.

mscottblake
Valued Contributor

@gregp: Simply putting the AAMEE created PKG on a SMB share corrupts it, so yes, it matters what file system your DP uses.

gregp
Contributor

@msblake- Egad. That's.... something.

andyinindy
Contributor II

We also use an AAMEE created CS6 pkg, being served via AFP. We had to ask JAMF for their "AdobeUser.pkg" in order to get CS6 to install at all. However, we are now noticing that the installation is very "hit or miss". In other words, sometimes it installs successfully, sometimes... nothing. Nothing discernible in the logs, it just isn't there, despite being present in the firstrun packages.

Anyone else seeing this inconsistent behavior?

--Andy

gregp
Contributor

Ours is very consistent in successfully installing it. Haven't heard any reports of it failing from our install guys or users that have it missing.

RobertHammen
Valued Contributor II

Yes, I have other clients who are installing it fine from AFP shares, or even via http (from an OS X server).

This is a specific issue with SMB sharepoints (even though we're using http almost exclusively). Glad to hear I am not alone with this issue... I've got someone at JAMF trying to reproduce this with 8.71...

RobertHammen
Valued Contributor II

Oh and I love the Creative Cloud Packager 1.2 release notes "Oops, when you clicked the checkbox to Ignore Conflicting Processes, it didn't actually do that. Fixed in 1.2". Sheesh. If only they'd have read my thread here from last April, I could have told them that. Quality is job... err... 21?

donmontalvo
Esteemed Contributor III

@RobertHammen I feel for Jody/Karl, it's a tough spot to be in when you're force fed incapable people. ;)

--
https://donmontalvo.com