Apple Platform Deployment
- Welcome
- Intro to Apple platform deployment
- What’s new
-
-
- Declarative status reports
- Declarative app configuration
- Authentication credentials and identity asset declaration
- Background task management declarative
- Calendar declarative configuration
- Certificates declarative configuration
- Contacts declarative configuration
- Exchange declarative configuration
- Google Accounts declarative configuration
- LDAP declarative configuration
- Legacy interactive profile declarative configuration
- Legacy profile declarative configuration
- Mail declarative configuration
- Math and Calculator app declarative configuration
- Passcode declarative configuration
- Passkey Attestation declarative configuration
- Safari extensions management declarative configuration
- Screen Sharing declarative configuration
- Service configuration files declarative configuration
- Software Update declarative configuration
- Software Update settings declarative configuration
- Storage management declarative configuration
- Subscribed Calendars declarative configuration
-
-
- Accessibility payload settings
- Active Directory Certificate payload settings
- AirPlay payload settings
- AirPlay Security payload settings
- AirPrint payload settings
- App Lock payload settings
- Associated Domains payload settings
- Automated Certificate Management Environment (ACME) payload settings
- Autonomous Single App Mode payload settings
- Calendar payload settings
- Cellular payload settings
- Cellular Private Network payload settings
- Certificate Preference payload settings
- Certificate Revocation payload settings
- Certificate Transparency payload settings
- Certificates payload settings
- Conference Room Display payload settings
- Contacts payload settings
- Content Caching payload settings
- Directory Service payload settings
- DNS Proxy payload settings
- DNS Settings payload settings
- Dock payload settings
- Domains payload settings
- Energy Saver payload settings
- Exchange ActiveSync (EAS) payload settings
- Exchange Web Services (EWS) payload settings
- Extensible Single Sign-on payload settings
- Extensible Single Sign-on Kerberos payload settings
- Extensions payload settings
- FileVault payload settings
- Finder payload settings
- Firewall payload settings
- Fonts payload settings
- Global HTTP Proxy payload settings
- Google Accounts payload settings
- Home Screen Layout payload settings
- Identification payload settings
- Identity Preference payload settings
- Kernel Extension Policy payload settings
- LDAP payload settings
- Lights Out Management payload settings
- Lock Screen Message payload settings
- Login Window payload settings
- Managed Login Items payload settings
- Mail payload settings
- Network Usage Rules payload settings
- Notifications payload settings
- Parental Controls payload settings
- Passcode payload settings
- Printing payload settings
- Privacy Preferences Policy Control payload settings
- Relay payload settings
- SCEP payload settings
- Security payload settings
- Setup Assistant payload settings
- Single Sign-on payload settings
- Smart Card payload settings
- Subscribed Calendars payload settings
- System Extensions payload settings
- System Migration payload settings
- Time Machine payload settings
- TV Remote payload settings
- Web Clips payload settings
- Web Content Filter payload settings
- Xsan payload settings
-
- Glossary
- Document revision history
- Copyright
-
- Privacy Preferences Policy Control custom payload examples
- Certificate Transparency custom payload example
- Swift Playgrounds app payload example
- Background task management example
- LOM payload example configuration and command issuance
- Cross-Site Tracking Prevention examples
- Manage Safari cookies
- Adding Active Directory payload options
- Variables settings for device management payloads
Configure your network for device management
When you’re installing and configuring your device management service, consider how you’ll configure the network, Transport Layer Security (TLS), infrastructure services, Apple services, and backup.
When you install a locally hosted device management service, you need to configure all of the following items. Configure and test each one early in the process to ensure a smooth deployment. If your service is externally managed or hosted in the cloud, the developer may handle many of these items on your behalf.
Use a fully qualified domain name
A device management service needs to use a fully qualified domain name (FQDN) that can be resolved from both inside and outside the organization’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 device management services require a static IP address. The existing DNS name needs to persist if the server’s IP address is changed.
Configure a device management service with Transport Layer Security
All communications between Apple devices and the device management service 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 expiration date and make sure to 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 device management service, certain firewall ports need to be open. Most services accept inbound connections using HTTPS on port 443. Both the device management service and the devices need to communicate with the Apple Push Notification service (APNs). Device management services use port 2197 with APNs; clients use port 5223.
Migration Assistant
To allow a Mac to be migrated properly and reenrolled in a device management service, Mac computers with macOS 13 or later and enrolled in a device management service no longer allow the transfer of the following settings using Migration Assistant:
System
Network
Printer
For these settings to be skipped during migration, the target Mac needs to be enrolled in the device management service.
Tip: Your device management service 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 device management service installation. It’s recommended that backups and restores be tested regularly.