fleet/docs/Using Fleet/MDM-commands.md
Noah Talerman 9c7079f50c
Windows MDM docs: turn on Windows MDM (#13943)
- Add new "Windows setup" page to "Device Management" section of docs
- Rename "MDM setup"  page to "macOS setup." Update links and add redirect
- Rename existing "macOS setup" page to "macOS setup experience." Update links. Did not add redirect because of conflict with "macOS setup" page
- Remove "MDM" from all MDM doc page titles
2023-10-04 15:39:09 -04:00

7.8 KiB
Raw Blame History

Commands

In Fleet you can run MDM commands to take some action on your macOS hosts, like restart the host, remotely.

If a host is offline when you run a command, the host will run the command the next time it comes online.

Custom commands

You can run custom commands and view a specific command's results using the fleetctl command-line interface.

To run a custom command, we will do the following steps:

  1. Create a .xml with the request payload
  2. Choose a target host
  3. Run the command using fleetctl
  4. View our command's results using fleetctl

Step 1: create a .xml file

You can run any command supported by Apple's MDM protocol as a custom command in Fleet. To see the list of possible commands, head to Apple's Commands and Queries documentation.

The "Erase a device" and "Lock a device" commands are only available in Fleet Premium

Each command has example request payloads in XML format. For example, if we want to restart a host, we'll use the "Restart a Device" request payload documented by Apple here.

To run the "Restart a device" command, we'll need to create a restart-device.xml file locally and copy and paste the request payload into this .xml file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Command</key>
    <dict>
        <key>RequestType</key>
        <string>RestartDevice</string>
    </dict>
    <key>CommandUUID</key>
    <string>0001_RestartDevice</string>
</dict>
</plist>

Step 2: choose a target host

To run a command, we need to specify a target host by hostname. Commands can only be run on a single host in Fleet.

To find a host's hostname, choose the "Fleet UI" or "fleetctl" method and follow the steps below.

Fleet UI:

  1. Head to the Hosts page in Fleet and find your target host.
  2. Make sure the Hostname column is visible (select Edit columns if not) and find your host's hostname. You'll need this hostname to run the command.

A host must be enrolled to Fleet and have MDM turned on to run a command against it.

fleetctl CLI:

  1. Run the fleetctl get hosts --mdm command to get a list of hosts that are enrolled to Fleet and have MDM turned on.
  2. Find your host's hostname. You'll need this hostname to run the command.

Step 3: run the command

  1. Run the fleetctl mdm run-command --payload=restart-device.xml --host=hostname command.

Replace the --payload and --host flags with your .xml file and hostname respectively.

  1. Look at the on-screen information. In the output you'll see the command required to see results. Be sure to copy this command. If you don't, it will be difficult to view command results later.

Step 4: View the command's results

  1. Run the fleetctl get mdm-command-results --id=<insert-command-id>

  2. Look at the on-screen information.

Example output:

$ fleetctl get mdm-command-results -id 333af7f8-b9a4-4f62-bfb2-f7488fbade21
+--------------------------------------+----------------------+----------------+--------------+---------------------+---------------------------------------------------------+
|                  ID                  |         TIME         |      TYPE      |    STATUS    |      HOSTNAME       |                         RESULTS                         |
+--------------------------------------+----------------------+----------------+--------------+---------------------+---------------------------------------------------------+
| 333af7f8-b9a4-4f62-bfb2-f7488fbade21 | 2023-04-04T21:29:29Z | RestartDevice  | Acknowledged | xyz-macbook-air.lan | <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE        |
|                                      |                      |                |              |                     | plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"              |
|                                      |                      |                |              |                     | "http://www.apple.com/DTDs/PropertyList-1.0.dtd">       |
|                                      |                      |                |              |                     | <plist version="1.0"> <dict> <key>CommandUUID</key>     |
|                                      |                      |                |              |                     | 	<string>333af7f8-b9a4-4f62-bfb2-f7488fbade21</string> |
|                                      |                      |                |              |                     | 	<key>Status</key>                                     |
|                                      |                      |                |              |                     | 	<string>Acknowledged</string> <key>UDID</key>         |
|                                      |                      |                |              |                     | 	<string>3A529CD6-2154-55EA-9AB7-EB13A43D9F5E</string> |
|                                      |                      |                |              |                     | </dict> </plist>                                        |
+--------------------------------------+----------------------+----------------+--------------+---------------------+---------------------------------------------------------+

List recent commands

You can view the list of the 1,000 latest commands using "fleetctl":

  1. Run fleetctl get mdm-commands
  2. View the list of latest commands, most recent first, along with the timestamp, targeted hostname, command type, execution status and command ID.

Example output:

$ fleetctl get mdm-commands
+--------------------------------------+----------------------+--------------------------+--------------+------------------------+
|                  ID                  |         TIME         |           TYPE           |    STATUS    |        HOSTNAME        |
+--------------------------------------+----------------------+--------------------------+--------------+------------------------+
| 024fb3b9-cd8a-40a6-8dd7-6c155f488fd1 | 2023-04-12T18:19:10Z | RestartDevice            | Acknowledged | iMac-Pro.local         |
+--------------------------------------+----------------------+--------------------------+--------------+------------------------+
| 87dc6325-8bc0-4fc8-9a2f-3901c535456e | 2023-04-12T18:15:01Z | DeviceLock               | Acknowledged | iMac-Pro.local         |
+--------------------------------------+----------------------+--------------------------+--------------+------------------------+

The command ID can be used to view command results as documented in step 4 of the previous section. 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 couldnt 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=<insert-command-id to view the error.
  • CommandFormatError: the host responded with "CommandFormatError" status via the MDM protocol: a protocol error occurred, which can result from a malformed command. Run the fleetctl get mdm-command-results --id=<insert-command-id to view the error.