Configure your network for MDM
When you’re installing and configuring your MDM solution, consider how you’ll configure the network, Transport Layer Security (TLS), infrastructure services, Apple services and backup.
When you install a locally hosted MDM solution, you need to configure all the following items. Configure and test each one early in the process to ensure a smooth deployment. If your MDM solution is externally managed or hosted in the cloud, your MDM vendor may handle many of these items on your behalf.
Use a fully qualified domain name
An MDM solution must use a fully qualified domain name that can be resolved from both inside and outside the organisation’s network. This lets the server manage devices whether they’re connected locally or remotely. To maintain connectivity with clients, this domain name can’t change.
Have a static IP address
Most MDM solutions require a static IP address. The existing DNS name must persist if the server’s IP address is changed.
Configure MDM with Transport Layer Security
All communications between Apple devices and the MDM solution are encrypted with HTTPS. A TLS (formerly SSL) certificate is required to secure these communications. Don’t deploy devices without a certificate from a well-known certificate authority (CA). Note the expiry date and make sure you renew the certificate before it expires. For more information, see the following Apple Support articles:
Keep certain firewall ports open
To allow both internal and external access to the MDM solution, certain firewall ports must be open. Most MDM solutions accept inbound connections using HTTPS on port 443. Both the MDM solution and the devices must communicate with the Apple Push Notification service. Prior to November 2020, MDM solutions used ports 2195 and 2196 with APNs; clients use port 5223. After November 2020, MDM solutions use port 2197.
To allow a Mac to be migrated properly and re-enrolled in an MDM solution, Mac computers using macOS 13 or later and enrolled in an MDM solution no longer allow the transfer of the following settings using Migration Assistant:
For these settings to be skipped during migration, the target Mac must be enrolled in the MDM solution.
Tip: Your MDM solution may host Activation Lock escrow keys and bypass codes, macOS bootstrap tokens, and other unique pieces of data important to continuity of device access. For this reason, make sure you have a robust disaster recovery strategy for your on-premises MDM installation. It’s recommended that backups and restores be tested regularly.