Create and send custom commands to managed devices. Monitor execution status and view results in real time.
Prerequisites
Required permissions: Admin or Staff role with command execution access
Supported platforms: Windows and macOS
Time estimate: 3–5 minutes
Additional requirements: Active device connection with Trio Agent installed
Before You Start
Custom commands allow IT administrators to execute specific actions remotely on managed devices, such as running scripts, performing diagnostics, or automating maintenance.
Commands can be executed manually, scheduled, or triggered automatically based on predefined conditions.
Ensure your scripts are tested before deployment to prevent errors on production devices.
Step 1: Navigate to Command Center
Go to the Fleet module from the sidebar.
Click Command Center → Create New.
Select Create New Custom Command to open the configuration window.
Expected result: You will see the command creation form with configuration sections for system, environment, scheduling, and file upload.
Step 2: Configure Command Settings
Command name — Enter a descriptive name (e.g., Turn on Backup).
Description (Optional) — Add context for this command’s purpose.
Operating system — Choose between:
Windows
Mac
Environment — Select the command environment:
CMD or PowerShell (for Windows)
Shell (for macOS)
Command — Type or paste the script or command you wish to execute.
Expected result: The command editor accepts valid syntax for the selected OS and environment.
Step 3: Define Execution Settings
Launch method — Select how the command should run:
Manually – Execute directly from the dashboard.
Schedule/Repeat/Webhook – Available under automation options.
Use “Smart defaults” — Enable to automatically apply Trio’s recommended timeout and retry rules.
Command expires after — Define how long the command remains valid (e.g., 3 days).
Timeout — Specify the maximum wait time for command completion (in seconds).
Troubleshooting this step:
Issue: Command does not execute. → Solution: Ensure target devices are online and accessible.
Common mistake: Expiration time set too short. → Prevention: Use at least 1–3 days for scheduled commands.
Step 4: Upload and Assign Files (Optional)
If the command requires additional files:
Click Upload attached file (Max 20MB).
Drag & drop or browse to select your file.
In File destination, specify the directory path on the target device (e.g.,
C:\Windows\Temp\FileName.png).Click Add.
Expected result: The uploaded file appears under the file list, ready for deployment.
Step 5: Save and Deploy
Review all configurations.
Click Create to finalize.
Assign the command to the target device(s) or group(s) under the Assign Targets tab.
Expected result: The custom command is created and queued for execution based on your defined schedule or manual trigger.
Next Steps
Immediate actions:
View command status under Command Center → Activity Log.
Monitor execution output and errors in real time.
Related configurations:
Policy Management → Automated Commands
Fleet → Scheduled Tasks
Troubleshooting
Issue | Cause | Solution |
Command fails to execute | Incorrect environment selected | Choose CMD for |
Device not receiving command | Agent offline | Verify agent connectivity and network status |
File upload error | File exceeds 20MB limit | Compress or split file before upload |
Timeout exceeded | Script running longer than expected | Extend timeout duration in execution settings |