From 3dd85c6a6da33b0738c45dc66110c1faa98293f9 Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Fri, 8 Sep 2023 09:44:03 -0400 Subject: [PATCH] MDM docs: MDM commands (#13745) - Add "NotNow" MDM status --- docs/Using Fleet/MDM-commands.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/Using Fleet/MDM-commands.md b/docs/Using Fleet/MDM-commands.md index b7659bf981..4758e2d696 100644 --- a/docs/Using Fleet/MDM-commands.md +++ b/docs/Using Fleet/MDM-commands.md @@ -112,6 +112,7 @@ $ fleetctl get mdm-commands The command ID can be used to view command results as documented in [step 4 of the previous section](#step-4-view-the-commands-results). The possible status values are: * Pending: the command has yet to run on the host. The host will run the command the next time it comes online. +* NotNow: the host responded with "NotNow" status via the MDM protocol: the host received the command, but couldn’t execute it. The host will try to run the command the next time it comes online. * Acknowledged: the host responded with "Acknowledged" status via the MDM protocol: the host processed the command successfully. * Error: the host responded with "Error" status via the MDM protocol: an error occurred. Run the `fleetctl get mdm-command-results --id=