Skip to main content
Solved

Deploying Adobe CC package via Jamf Cloud and Self-Service. Install on client Mac fails at the end.

  • August 10, 2023
  • 7 replies
  • 91 views
Scourch
Forum|alt.badge.img+4

Heya folks. I had a previous post about Adobe CC with a lot of helpful feedback. I've gotten to a point where I was able to succesfully deploy and download applications via Mac Apps (Hooray!) but for individual Adobe products such as Photoshop and Illustrator, this was not working in that once installed the credentials I used to sign in was not recognized as being an Education account and I was granted only a trial.

Whereas when I create a package via Adobe CC Admin portal, pick my apps and install, when I log into after an install this way, Adobe recognizes my credential. So, after setting up my distribution point with Jamf Cloud and creating a package with the .pkg from the latest package build in Adobe Admin, I pushed it down to Self-Service with a policy.

I see Adobe CC in self-service and i go to install it and it takes about 8 to 10 minutes before it ultimately fails. When I go to the details in Jamf, all I get is...

  • Installation failed. The installer reported: installer: Package name is Mac Lab Test
    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. An error occurred while running scripts from the package “Mac Lab Test_Install.pkg”.)

Anyone have any idea of what that means, or what I can try?  The failure log here is not very specific.

Best answer by sonance

Ran into something similar on my end. 

Did some research and came across this KB article from Adobe:

https://helpx.adobe.com/enterprise/kb/deploy-packages-using-jamf-pro.html

I uploaded my .pkg via Jamf Admin, applied it to a policy and it worked.

Hope that works for you!

    7 replies

    mvu
    Forum|alt.badge.img+20
    • mvu
    • Jamf Heroes
    • August 10, 2023

    What did you build in your Adobe package? On the Mac you're testing with, are there any Adobe products previously installed? Like Adobe Creative Cloud?

     

    Scourch
    Scourch
    Forum|alt.badge.img+4
    • Scourch
    • Author
    • Contributor
    • August 10, 2023

    What did you build in your Adobe package? On the Mac you're testing with, are there any Adobe products previously installed? Like Adobe Creative Cloud?

     


    This package has Photoshop and Illustrator and no, the Mac has no other Adobe products installed on it.

    sonance
    Forum|alt.badge.img+2
    • sonance
    • New Contributor
    • Answer
    • August 10, 2023

    Ran into something similar on my end. 

    Did some research and came across this KB article from Adobe:

    https://helpx.adobe.com/enterprise/kb/deploy-packages-using-jamf-pro.html

    I uploaded my .pkg via Jamf Admin, applied it to a policy and it worked.

    Hope that works for you!

    Scourch
    D
    Forum|alt.badge.img+3
    • DG_Edwards
    • New Contributor
    • August 11, 2023

    Are you trying to deploy specific Adobe apps or are you trying to deploy the Creative Cloud app launcher where users can make their own choices on which to deploy?  

    I have to say, when I started with Jamf about 9 months ago the app packages downloaded from the Adobe admin console worked just fine and they'd install no issue.  Somewhere around 2 months ago those packages that previously worked simply stopped and would get nothing but errors such as you're describing.  We originally used the MacOS (Universal) platform when downloading the installer however neither that, nor MacOS (Intel) or MacOS (Apple Silicon) would work on any of the devices.  

    Around that same time we discovered that Jamf managed apps were now allowed to be advertised in Self Service which was a big sticking point for us.  We rolled over to the Jamf managed versions of all the apps and those have been working for us quite well.  

    I know this is a redirection more than a solution, but if that's something you're considering at least it'll give you an alternative path to deploying the software.  

    Scourch
    Scourch
    Forum|alt.badge.img+4
    • Scourch
    • Author
    • Contributor
    • August 11, 2023

    Are you trying to deploy specific Adobe apps or are you trying to deploy the Creative Cloud app launcher where users can make their own choices on which to deploy?  

    I have to say, when I started with Jamf about 9 months ago the app packages downloaded from the Adobe admin console worked just fine and they'd install no issue.  Somewhere around 2 months ago those packages that previously worked simply stopped and would get nothing but errors such as you're describing.  We originally used the MacOS (Universal) platform when downloading the installer however neither that, nor MacOS (Intel) or MacOS (Apple Silicon) would work on any of the devices.  

    Around that same time we discovered that Jamf managed apps were now allowed to be advertised in Self Service which was a big sticking point for us.  We rolled over to the Jamf managed versions of all the apps and those have been working for us quite well.  

    I know this is a redirection more than a solution, but if that's something you're considering at least it'll give you an alternative path to deploying the software.  


    It is specific apps, Photoshop and Illustrator. I am happy to report that @sonance suggestion of making the package in Jamf Admin, worked. What's funny is my experience seems to be the opposite of yours. My experience has more or less been this...

    • Made and downloaded an Adobe package and set up a SMB distribution point. Worked with another tech here who does WDS deployments and we couldn't get it to work.
    • Tried making a script to make a local folder, mount the package on our SMB share, copy it to the local folder and then unmount. Kept getting issues on the mounting, even though the path was correct because I could use that same file path in Terminal and open it.
    • Went to Computers > Mac Apps> Jamf App Catalog and downloaded the Illustrator and Photoshop applications. They pushed out to my test mac just fine and installed. The issue here was the credential I was using to log in (via Google SSO) came back as not having full access and said I had a 7 day trial.

    Comapre all this to the fact that I could make the package in Adobe CC Admin, download it, install it directly onto my test Mac and it all works fine. Last year before we used Jamf to manage the Macs, they were essentially free agents out in the High School. We had an admin account on there and some of our firewall and remote access tools but that was it. And those tools, like the Adobe products we're installed one by one by one. As it was then, it is true now; directly installing adobe via its package right onto the Mac, eliminating Jamf in this process, works.

    It wasn't until Sonace suggested Jamf Admin that I had success. Creating the package through that and then assigning that package to a policy in Jamf Pro pushed down Adobe CC and when installed, it also installed Photopshop and Illustrator and logging in with my Adobe cred, it recognized it as an education account and I had full app access, no trial.

    W
    Forum|alt.badge.img+7
    • wifichallenges
    • Valued Contributor
    • October 18, 2023

    For me, this is the stupidest thing ever, i had to re zip the PKG file instead of letting jamf do it... i dont have access to jamfadmin as we are cloud hosted. But from this thread, mid way thru, you can see that someone said that just zipping the pkg file worked and lo and behold it did.

     

    https://community.jamf.com/t5/jamf-pro/proper-way-to-install-adobe-creative-cloud-package/m-p/234092

    simply take the install.pkg file out of the zip file that you get from adobe. Then rezip just that file, then upload to packages. works.

    hung_cheng
    Forum|alt.badge.img+2
    • hung_cheng
    • New Contributor
    • October 31, 2023

    I was also facing the same issue. Please take a look at the below error message from Jamf. 

    Installation failed. The installer reported installer: Package name is Adobe Cloud Universal_Oct_2023
    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. An error occurred while running scripts from the package “Adobe Cloud Universal_Oct_2023_Install.pkg”.)[STEP 3 of 4][STEP 4 of 4]

    I also tried uploading the package via Jamf Admin, but the result remains the same.

    Does anyone has any advice on Adobe Cloud app deployment? Thanks

    Terms & ConditionsCookie settingsAccessibility statement