Content Caching Server (Public beta)

Due to recent changes in the macOS system storedownloadd process, the ZuluDesk Content Caching daemon cannot currently deliver packages. We are currently working on a solution and apologize for any inconvenience this may cause.

Jamf School version 6.1.7 (public beta) adds support for Content Caching. With this daemon running on a macOS machine, you can internally cache all enterprise apps (iOS, tvOS, macOS) and documents. Content Caching Server requires a Mac running macOS 10.13 or newer.


  1. Enroll the Mac you want to use as the Content Caching Server in Jamf School, make sure to assign it a device group so you can easily find it;
  2. Download the "ZuluDesk Content Caching Server (v1)" package and upload it as In-House macOS Package in Jamf School Management System;
  3. Scope the newly uploaded package so it will install on the Mac you want to use as the Content Caching Server


  1. Go to Organisation -> Settings -> Content Caching and tick the box to enable Content Caching; 
    1. macOS Device to use: select the macOS device you want to use as the Content Caching Server;(Currently only available in BETA)
    2. Volume: enter the path where you want to store the cached files. Please make sure enough space is available;
    3. Public IP Addresses: enter the public IP address or your school. If you have more than one, separate them with a comma. This IP address is used to determine if a installation request should be handled by the Content Caching Server or not.
  2. Click on "Save". 

Internal network:

The Content Caching Server will start a webserver on port 5050. Make sure this port is whitelisted in your internal firewall if you have one and that all clients in your network can reach the Content Caching Server. Currently, multiple servers in the same network are not supported.

Next Steps:

The Content Caching Server will automatically start downloading all in-house apps and documents to the local server. To check if an item has been cached you can go to the details page. 

Installation Requests:

The Content Caching Server will automatically serve the file from the server if its being cached locally and the installation requests is originated from one of the Public IP addresses configured at Organisation -> Settings -> Content Caching.

Items you don't want to cache:

There are cases where you want certain items not to be cached. To do so, open the details page of the app or document and untick the "Enable caching on the Caching Server for this item" box. If the item was already cached, it will be removed from the Content Caching Server.


Local items are stored in the path you've configured in Jamf School Management System. The Content Caching Server will apply permissions to the folder in such a way that only the "root" user can access the files directly. 

Downloading files are protected with a one-time-token generated when the installation request is created. The token is validated with Jamf School Management System and is only valid for one given item. 


Download the Uninstall tool



Have more questions? Submit a request


Article is closed for comments.