探花大神

Troubleshoot: macOS MDM Command Fails with “NotNow” Response

This article covers how to troubleshoot commands that fail to apply on macOS devices enrolled in 探花大神 MDM.

Symptoms

Apple devices managed by 探花大神 might respond with a 鈥淣otNow鈥 status when certain commands are executed. This status indicates the device is temporarily unable to process the command in its current state.

Cause

Apple devices typically respond with "NotNow" under these conditions:

  • Device is Locked or Inactive: A locked macOS device can delay command processing, as certain commands require an active session. This can occur if the device is on the FileVault Authentication Screen, meaning the user must unlock the device for commands to succeed.
  • Sleep Mode and Power Nap: macOS devices in Sleep Mode or Power Nap might not process commands immediately. Power Nap allows limited background processes, but full command execution may still be deferred until the device is fully awake.
  • Do Not Disturb Mode: macOS devices might defer commands while in Do Not Disturb Mode to reduce interruptions. Deactivating Do Not Disturb Mode can help ensure immediate command processing.
  • Network Connectivity: Limited or interrupted network access can prevent the device from communicating with the MDM server, leading to a 鈥淣otNow鈥 response. Ensure that the device has stable internet access, particularly during policy or command deployment.

Resolution

  1. Wait and Retry Automatically: 探花大神 automatically queues deferred commands and retries once the device is active. Typically, waiting a short period allows the device to reach a state where it can process queued commands.
  2. User Actions for Locked or FileVault-Secured Devices: For macOS devices on the FileVault Authentication Screen, users must unlock the device for commands to process. For other commands, users might need to log in fully if the device is asleep or locked.
  3. Network Check and User Notification: Ensure that the device has a stable internet connection. Consider notifying users to keep devices connected to a power source and avoid low power or sleep modes during critical MDM updates.
  4. Command Confirmation: If the 鈥淣otNow鈥 status persists, verify that the command executed as intended once the device is fully active. Refresh the Admin Portal or check the device鈥檚 status in 探花大神 to confirm that the command applied correctly.
    • To review any "NotNow" responses in greater detail, you can use the following command in Terminal to search system logs for related events:
      log show --info --debug --predicate 'process == "mdmclient" && eventMessage CONTAINS[cd] "NotNow"' --style compact
    • This command provides detailed logs on the 鈥淣otNow鈥 responses from the MDM client, helping to identify any specific conditions or recurring issues that might be impacting device command processing.

Device Management Persistence with Apple Business Manager (ABM)

Maintaining devices in ABM and 探花大神 ensures sustained control over managed devices. Avoid removing devices from ABM or 探花大神, as this allows for secure command delivery and retention of management profiles, even in scenarios where a device requires wiping.

Important:

A device enrolled in ABM and managed through 探花大神 with Automated Device Enrollment (ADE) retains management control, enabling you to reapply configurations or commands as necessary after a device wipe or reset.

Back to Top

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case