Adobe Creative Cloud Packages Fail to Download

tuinte
Contributor III

Hello JAMFnation!

JSS: 9.21
Master DP: OS X 10.8.5 with Server.app

I've created a few packages for Adobe app installs with Creative Cloud Packager. All have been uploaded via Casper Admin. Issue is, I get this error whenever I do anything with them:

Failed to download files from http://jss.server.com/CasperShare/Packages/AdobeAcrobatXIPro.pkg/index.bom.

That was me simply trying to cache the package via Remote. That's an Acrobat-only package, but I get the same for each of the various CC packages, using Remote, policy or Self Service policy. Permissions look OK. They replicated fine. Packages install OK manually.

Other possibly relevant info:

All DPs are sharing over HTTP.

Upgraded to 9.21 from 8.73 a couple of months ago. Things have been good, though.

We were also getting this error with a printer driver, but the printer ended up being decommissioned anyway, so we never really resolved it.

It doesn't fail right away at all. I would say it takes pretty close to how long the package would take to download before it throws an error. But alas, the file isn't in Waiting Room afterward when all is said and done.

Ideas? I was so excited to tell everyone we had Creative Cloud ready to go…

Michael

1 ACCEPTED SOLUTION

mapurcel
Contributor III

For Adobe CC apps in our environment we wrap the .pkg file in a .dmg and then install via script, all through a Self Service policy. https://jamfnation.jamfsoftware.com/article.html?id=161

View solution in original post

5 REPLIES 5

tuinte
Contributor III

UPDATE:

I decided to give our AAMEE-created CS6 packages a test by caching via Remote/Self Service, and they're getting the same error. We've never deployed these via policy or Remote since the 9.x upgrade, so haven't seen that behaviour, but it's possible (likely?) it started then.

Anybody have any problems with non-flat packages, JSS 9.x, and Remote/policy?

FYI: We haven't touched JDS migration.

Thanks for any help you can offer!

Michael

tuinte
Contributor III

UPDATE:

The packages install fine at Imaging, just getting the same error every time using Remote or a policy (Self Service included). Seems to be all non-flat packages.

Michael

donmontalvo
Esteemed Contributor III

Have you tried forcing AFP? HTTP is good for flat PKG and DMG, but tends to fail on AAMEE/CCP generated non flat PKGs and MPKGs.

--
https://donmontalvo.com

mapurcel
Contributor III

For Adobe CC apps in our environment we wrap the .pkg file in a .dmg and then install via script, all through a Self Service policy. https://jamfnation.jamfsoftware.com/article.html?id=161

tuinte
Contributor III

Don: For boring reasons that upset me, forcing over AFP isn't an option.

mapurcel: Found that article yesterday and have made such a dmg. It's testing fine, so looks like I've found my solution, thanks so much.