Skip to main content

Content caching servers and considerations for deployment

  • Updated

Introduction

This article covers content caching servers and considerations for deployment under the datajar.mobi service.

Content caching is a service in macOS that speeds up downloading of software distributed by Apple and data that users store in iCloud by saving content that local Apple devices have already downloaded. The saved content is stored in a content cache on a Mac, and is available for other devices to retrieve without going out over the internet. The following article provides a comprehensive list of the specific content types of content that can be cached: https://support.apple.com/en-gb/HT204675

We recommend using a content caching server in the following scenarios:

  • You have more than 10 Mac computers on your organisation’s local network (e.g classroom(s) or office(s))
  • Total WAN/internet bandwidth/speed is low (e.g. below 80 megabits/second)

Your datajar.mobi service includes a role called Content Caching that contains minimal configuration with no applications. This role will enable the content caching service automatically, and for simple networks no further configuration is needed. We strongly recommend using this role for any Mac computer intended for this purpose.

Requirements and further considerations

Hardware recommendations

  • Mac mini 2018 (Intel) or 2020 (M1) and later
  • 8GB RAM
  • 1TB SSD
  • 10 gigabit ethernet

Network requirements and considerations

Content caching servers can work in a variety of network environments, ranging from a simple single-subnet with one public/WAN IP address, to larger networks spread across multiple VLANs with client devices using a range of multiple public/WAN IP addresses.

  • Connect the content caching server to the network with a wired ethernet connection and switch off Wi-Fi. This will prevent Wi-Fi network saturation under heavy load (e.g. during a mass operating system update for a cart of iPads).
  • Ensure your network allows access from the content caching server to Apple/our endpoints as per our Apple Device Network Requirements.
  • Ensure your network allows unfiltered/unproxied access from your clients to the content caching server. This can be limited to a specific TCP port if needed with a configuration change to the content caching server; please submit a support request if you need further assistance.

Depending on the topology/complexity of your network, additional configuration steps may be required for your content caching server, as outlined below:

For networks with a single subnet with one public/WAN IP address

  • No further considerations are necessary.
  • If you wish to limit the local IP address range for clients that the content caching server will be available to, please submit a support request stating the IP range(s) required.

For networks with multiple subnets and one public/WAN IP address

  • A configuration change to the content caching server is needed for clients to discover your content caching server correctly; please submit a support request informing us of this.
  • If you wish to limit the local IP address range for clients that the content caching server will be available to, please also state the local IP range(s) required.

For networks with single/multiple subnets and multiple public/WAN IP addresses

  • A configuration change to the content caching server is needed for clients to discover your content caching server correctly; please submit a support request informing us of this and state the public/WAN IP ranges your clients will use.
  • A DNS configuration change is required on your network. For more details please see: https://support.apple.com/en-gb/guide/deployment/dep44750bbf7/web. dataJAR can advise further on the specific change required for your environment.
  • If you wish to limit the local IP address range for clients that the content caching server will be available to, please also state the local IP range(s) required.

Need further support?

If you still require assistance with us or have any further questions, please raise a ticket with our support team.

Alternatively, please see our frequently updated knowledge base articles for reference.



Related articles