Issue Description
When installing a Disk Image on Jamf School managed devices, the install may fail with a message such as: "The Package [Package Name Here] could not be mounted (no mountable file systems)" or when opening the file it returns "The following disk images could not be open. No mountable file systems."
This usually occurs if there is a restriction set to prevent mounting files or if the file used for deployment is corrupted.
Troubleshooting Steps
Check for a configuration profile restricting use of Disk Images
To find this setting, in Jamf School > Profiles > Overview > Click into the profile > Restrictions > Media. Disk Images should be allowed as shown below:
If issue occurs after the above, to eliminate any restrictions from Jamf School start by disabling installed profiles one by one:
Go to Devices > Inventory > Search for the device and click into it
Navigate to the Managed profiles tab
Disable the first installed profile on this page then attempt the install on the machine
Repeat step c until narrowed down to which profile is preventing this install
If all profiles are disabled and the issue still occurs, the file may be corrupted or had an error while downloading onto the system. Try re-downloading the disk image file and mounting again.
Additionally, make sure that the file system used to create the packages is compatible with macOS. MacOS High Sierra (10.12.x) and earlier is unable to mount disk images created with APFS.
If the package was created with Jamf Composer, check the filesystem used to create the package in Composer's Preferences.
In Composer, go to the upper menu bar > Composer > Settings:
If the disk image is not made in Composer, reach out to Jamf Support and include more clarification as to how that file was obtained or created