Prepare Network Infrastructure 02
The MDM solution can be a powerful tool for both the technology team, students and teachers, but the platform doesn’t work alone. The MDM communicates with the Apple devices through push commands sent by Apple's servers as requested by the MDM, which is dependent on a valid Internet connection. That's why the Network Infrastructure needs to be built and configured properly to avoid any future headaches.
When migrating MDM solutions, remember to check out the configured proxy ports as well as the server wildcards that should be allowed for the new MDM solution to work properly.
If you are moving to Mosyle Manager, check all the required TCP Ports, APNs Server, and MDM Server wildcard to allow:
|Service name||External port (begin)||External port (end)||Description|
|Web service (http)||80||80||For accessing Hypertext Transfer Protocol (HTTP)|
|Web service (https)||443||443||For a fallback on Wi-Fi only, when devices can't reach APNs on port 5223|
|Push||2195||2196||For sending notifications and having feedback of APNs|
|APNs||5223||5223||For communicating with Apple Push Notification Services (APNs)|
|Internal Control||3180||3180||For controlling the access to Internet through Mosyle Manager Study Sites and Web Filter|
It’s also required to allow the MDM Server wildcard:
If you are not only switching from a mobile device management, but also scaling the iPad and/or Mac Program of your school or district, it's also important to pay attention to the coverage and capacity of your network.
We sorted some tips in a special guide about Network Configuration and Infrastructure to help you configure your network in order to make it works seamlessly with the MDM solution, as well as some important insights about coverage and capacity, and testing the network.