Skip to main content
Make sure that your network can support Zappl’s requirements, documented here. If Zappl cannot reach the necessary services then core product functionality will fail.
1

Zappl Preferences Profile

This is the most important one, and must contain your Activation Token and Public Key. You should have received these upon activation of your trial/purchased license. No other keys are necessary for Zappl to function.

Custom Schema

This option is perfect for Jamf Pro. If you need support with using the Custom Schema, check out our full Jamf Pro deployment guide.

iMazing

We have a full payload in iMazing. This will provide you with a .mobileconfig file to upload to your MDM.
2

Additional Profiles

These additional profiles ensure that Zappl functions as expected, with the necessary permissions and background processes.

Managed Login Items

Ensures Zappl can run in the background, and prevents users from disabling this feature.

Privilege Preference Policy Controls

Pre-approves the necessary access for Zappl (Full Disk Access).
3

Installer Package

Latest Zappl PKG

Download the latest current version of Zappl. Upload the PKG to your MDM or install it directly on a test Mac.

Latest Zappl via Script

Alternatively, you can deploy Zappl using this script. This ensures the latest version of Zappl will always be deployed
Zappl is a patch management tool that actively downloads and installs software updates in the background. When deploying to large numbers of devices on the same network, we strongly recommend phasing your rollout in batches rather than deploying to your entire fleet at once. Deploying to all devices on the same network in one go will result in all outdated apps downloading updates simultaneously on the first run, which may result in significant network load.
Ready to take your Zappl experience further? Check out our full deployment guides for Jamf Pro, our wide range of preference customisations or how to deploy applications using Zappl.