In this article

Network administrators use this article to pre-configure the macOS Roaming Client daemon.conf settings before deploying via MDM. This ensures all devices receive a consistent configuration at install time without requiring manual post-install edits.

Custom values can be added to the MDM deployment script so every device receives the configuration automatically.

Add custom settings to the deployment script

In the MDM deployment script, locate the cat block that writes the temporary config file and add custom settings before deploying:

cat > "$LOCATION/$TEMP_CONFIG_NAME" << EOF
SITE_SECRET_KEY="$SITE_SECRET_KEY"
LOCAL_DNS_AND_DOMAINS=""
OVERRIDE_CONFIG_FILE=yes
EOF

Common settings include:

• Local domains and resolvers
• DoT upstream order
• Travel Wi-Fi mode 

Important notes

• daemon.conf uses TOML format—use correct syntax for strings and arrays
• Changes take effect within approximately 5 seconds after the next DNS request. A full restart is not required
• Do not modify the PKG installer directly. All customization should be applied through the deployment script
• If devices are not receiving the expected configuration after deployment:
  • Confirm the correct file path is referenced for the installation type
  • Review the relevant section of the deployment script to verify syntax and formatting