Skip to main content

Create a command from a Template

Learn how to create Scripts from Trio templates.

Prerequisites

  • Required permissions: Admin or Staff role with command creation access

  • Supported platforms: Windows and macOS

  • Time estimate: 5–10 minutes

  • Additional requirements: Predefined command templates available in the Command Center

Before You Start

The Create Command from Template option allows you to quickly generate and execute prebuilt commands on selected devices or device groups.
This feature helps IT admins save time by reusing preconfigured scripts rather than creating each command manually.

Note: Commands created from templates can still be customized before deployment.

Step 1: Navigate to the Command Center

  1. From the left sidebar, select Fleet > Command Center.

  2. Click the Commands tab to view available command templates.

Expected result: The Command Center displays a list of predefined templates for different OS environments.

Step 2: Select a Command Template

  1. Browse the available templates and select the one you want to use (e.g., Convert to 64-Bit).

  2. Click Create from Template.

Expected result: The Create Command from Template page opens, prefilled with command details.

Step 3: Review Command Settings

  1. Under Command settings, review or update the following fields:

    • Command name: Auto-filled from the template (can be renamed).

    • Description (optional): Add context for internal tracking.

    • Operating system: Displays the supported platform (Windows or macOS).

    • Environment: Shows the applicable shell, e.g., CMD or PowerShell.

    • Command: View or edit the preconfigured script.

Tip: Use the Copy button to duplicate the command content for review.

Step 4: Configure Execution Settings

In the Select how this event will run section, define when and how the command executes:

  • Launch method: Choose between manual, scheduled, or automated triggers.

  • User “Smart defaults”: Toggle on to apply system-recommended timing and timeout values.

  • Command expires after: Specify how long the command remains active (default: 3 Days).

  • Timeout: Define the duration (in seconds) before command execution stops automatically.

Troubleshooting this step:

  • Issue: Command doesn’t execute → Solution: Check timeout and expiration values.

  • Common mistake: Leaving launch method unset → Prevention: Always confirm the method before proceeding.

Step 5: Upload Supporting Files (Optional)

If the command requires attached files (e.g., installers or scripts):

  1. Click Upload attached file and select the file (max 20 MB).

  2. Enter a File destination (e.g., C:\Windows\Temp\File name.png).

  3. Click Add to confirm.

Expected result: Uploaded files appear under the Files list with their destination paths displayed.

Step 6: Save and Assign

  1. Click Create to finalize the command.

  2. A prompt appears asking if you want to assign the command.

  3. Choose:

    • Assign – to apply it to specific devices or device groups, or

    • Done – to save the command for later assignment.

Expected result: The command is created and visible in the Commands tab.

Next Steps

Immediate actions:

  • Review assigned devices under the Queued tab.

  • Monitor execution status in real-time.

Related configurations:

  • Queued Command Management

  • Command Results Tracking

Troubleshooting

Issue

Possible Cause

Solution

Command not appearing in list

Template not selected properly

Reopen the Command Center and select a valid template

Command fails to run

Incorrect OS or environment

Verify that device OS matches the template requirements

File upload fails

File exceeds size limit

Ensure attached files are under 20 MB

Did this answer your question?