Description
Installing Adobe applications on managed computers is a common workflow for many organizations using Jamf School. However, large packages from the Creative Cloud Console can be challenging to upload into Jamf School and only using app installers causes the apps not to be licensed.
The workflow in this article uses a smaller package from the Creative Cloud Console with the shared device license that can then be used with the other apps installed via App Installers.
This workflow requires Composer, which can be downloaded in Jamf Account from Solutions > Add-ons.
Creating the Adobe Package
Create the shared device package in the Creative Cloud Console. When creating your package:
Only include the Creative Cloud application.
Choose create flat package before downloading.
Download the package you created and extract the PKG.
Adobe has instructions on how to get macOS packages here under the "Download Packages" section.
Create a nested package in Composer following the steps below:
On a computer with Composer installed, create a folder for your package in the /private/tmp directory:
sudo mkdir /private/tmp/adobe
Move the package you want to nest to the folder created in step 3a.
Open Composer and give it the permissions it requires.
Using Finder drag the folder containing the Adobe package into the Composer sidebar to start building a new package.
Make sure to grab the Directory containing the PKG not the PKG itself.
Expand the file tree in the Composer file viewer and highlight the
/private/tmp
directoryClick the ... button in the lower-right corner of Composer. Select Apply permissions tmp and All Enclosed Items.
Repeat step f but now select Apply Owner and Group to tmp and All Enclosed Items.
In the sidebar of Composer click on the small arrow next the package name you are working on.
Right click (or 2 finger click if on trackpad) on Scripts, hover over Add Shell Script, and then select postinstall.
On line 1 of the postinstall script, change the #!/bin/sh to
#!/bin/bash
.After the 4 predefined variables we will write our line to handle the install of the application, in this case:
installer -pkg "/private/tmp/adobe/NAMEOFADOBEPACKAGE.pkg" -target /
Note:
No
sudo
needed here as PKG scripts are executed as root.The path to your PKG will differ from the example. Update NAMEOFADOBEPACKAGE
Click File > Save in the menu bar to save the changes to the script.
In the sidebar of Composer, click the main package for the project you are working on.
Click Build as PKG to build the finished PKG.
Deploying Adobe Apps via Jamf School
Upload the package to Jamf School.
For steps see Adding In-House Apps and Packages in the Jamf School Documentation.
Add device groups to the scope of the application.
For steps see Distributing Apps and Packages to Groups in the Jamf School Documentation.
Install the other applications via App Installers.