Your school consists of network with Apple devices such as Mac, MacBook, iPad and iPhone. These devices use the Internet to periodically check with Apple for updates to the operating system (iOS) and any installed applications. If there are any updates then they are automatically downloaded and this can saturate the school's Internet connection.
To resolve this issue, you might allow all Apple devices shipped with free software to act as an Apple cache by enabling the feature on the device that will be left on all the time. When an update is released, all Apple devices on the network are automatically directed by Apple to download the update from the local Apple cache. Each update is downloaded from Apple only once, which minimises the impact on the Internet connection.
However there could be some issues affected by implementing the Apple cache.
The device that acts as the Apple cache registers itself with Apple. Apple associates the public IP address with that particular cache. When an update request arrives from the same public IP address, Apple sends a message back telling the device to fetch the update from the local cache.
For example, we have ten proxy servers in our proxy farm. If school A sets up an Apple cache and when it registers with Apple the request just happens to be sent through proxy seven, Apple will associate the public IP address of proxy seven with that Apple cache.
Then an Apple device from school B checks for an update. The request just happens to be sent through proxy seven. Apple recognises the public IP address and tells the device to go and fetch the update from the local cache. But the local cache is in school A and our firewall prevents the device from reaching the cache. So any device that happens to be directed through proxy seven will be unable to obtain any updates from Apple (unless it is in the school that actually has the Apple cache). |