Prerequisites

Required permissions: Admin role with access to Fleet and Command Center
Supported platforms: Windows 10/11, macOS Ventura and above
Time estimate: 5–10 minutes
Additional requirements: Autopilot groups and enrolled devices already synced and available in Fleet

Before You Start

The Command Details page lets you configure a reusable command template and assign it to specific devices or Autopilot groups. This is ideal for IT administrators who want to standardize command-line executions, like registry edits or script-based fixes, across multiple endpoints from a central interface.

Improper command syntax or incompatible environment selections may lead to command failures or system errors on the target device. Ensure you understand the command structure and target environment before executing.

Make sure all target devices are online, enrolled, and categorized correctly into Autopilot groups or available by name/OS. Have your command script ready in CMD or PowerShell format, and confirm if 64-bit execution is required.

Step 1: Access Command Template Details

Navigate to Fleet > Command Center
Select any existing command template (e.g., Template Command)
Expected result: You’ll see a tabbed layout with Settings, Autopilot, and Devices sections for the selected command

If you see no template listed: Go back to Command Center and click Create new command

Step 2: Configure Command Settings

In the Settings tab, fill in Command name (e.g., Convert to 64-Bit #1)
Add an optional Description for documentation (e.g., “Execute in 64-bit PowerShell mode”)
Select the Operating system: Windows or Mac
Choose the Environment: CMD or PowerShell
Paste your shell command inside the Command field
Click Save changes

Expected result: The template is now configured and ready for assignment

Troubleshooting this step:

Issue: “Save changes” is disabled → Solution: Ensure all required fields are filled
Common mistake: Using invalid syntax → Prevention: Test the command on a local machine first

Advanced/Optional Configuration

Wrap PowerShell in a 64-bit context using:

powershellCopyEdit& (Join-Path ($PSHOME -replace 'syswow64', 'sysnative') powershell.exe) -Command "& {$YourCommand}"

Step 3: Assign to Autopilot Groups

Go to the Autopilot tab
Use the search bar or scroll to locate desired groups
Click the + Assign button
Confirm selected groups and click Apply

Expected result: The command template is now linked to specific user/device groups

Troubleshooting this step:

Issue: Groups not visible → Solution: Ensure Autopilot is enabled and synced for these users
Common mistake: Assigning command to inactive groups → Prevention: Verify Autopilot status before assignment

Step 4: Assign to Devices Directly

Navigate to the Devices tab
Use filters to sort by Name, OS, Autopilot, or Last situation
Select devices and click + Assign
Confirm the selected targets

Expected result: The command template is now associated with specific endpoints

Troubleshooting this step:

Issue: Device shows “Queued” but not deployed → Solution: Confirm device is online
Common mistake: Selecting duplicate targets via group and device → Prevention: Review assignments before running