When a schedule sync is attempted on Mac devices, a device may not execute commands, but instead respond with a NotNow status during these conditions:
The device is running on battery power in Power Nap and the server sends any command other than DeleteUserCommand, DeviceLockCommand, EraseDeviceCommand, RestartDeviceCommand, ShutDownDeviceCommand, UserListCommand, ActivationLockBypassCodeCommand, ClearActivationLockBypassCodeCommand, or UnlockUserAccountCommand.
The server sends an InstallProfile or RemoveProfile command on the user connection and the user’s keychain is locked.
The device is blocking the user’s login while it contacts the server and the server sends a request that can take a long time to process; for example, InstalledApplicationList.
Workaround: The commands will be executed when the device reaches the server once the device is unlocked (No manual step will be required by the administrator).