[Notification] We're upgrading the JumpCloud Support Center the week of September 30th.

Support Center

Using the Commands Tab

JumpCloud's Commands feature lets you run commands across any number of systems (Windows, Mac or Linux) or System Groups, get back command results (including stdout, stderr, and exit code), schedule commands without the pain of cron, and much more.

This lets you quickly and easily automate tasks across a number of servers, launch those tasks based on a number of different types of events, and get full auditing of all command results.

The Commands tab is very easy to use:
  1. Click the "Commands" tab on the left navigation menu
  2. Click "+" to create a new command
  3. Select your operating system, Linux, Windows or Mac.
  4. Enter a name for the command, this is the name shown in the sortable list view of commands.
  5. Linux only: select the RUN AS user account to use to run the command, Windows only: commands will be run as the LocalSystem account and optionally can be run as Powershell.
  6. Type or paste in a script. The script can be in any language that your servers can execute.
  7. Select the launch event (see below for details).
  8. Set a timeout value.
  9. Set Run On, select the individual systems or Groups on which you want to run the command.
  10. Choose a Command Runner who should be granted permission to run the command.
  11. Select a File to upload to the system (optional, see below for more detail)
  12. Click "save command"

Launch Event

You have a number of choices as to how a JumpCloud command is launched:
  • Run Manually - Commands will be launched manually with the 'run now' button in the Commands list view.
  • Run as Scheduled - this command is set to run one time in the future, at a specific date and time. This is useful for one-time operations that need to be run during a change window.
  • Run as Repeating - this command is set to run repeatedly, at a specific interval
  • Run on Trigger (webhook) - this command is set to run upon receipt of a webhook from an external source.

NOTE: Scheduled and Repeating event timing will correspond to the target system's time zone.  Within the JumpCloud interface, the event will be labeled with "(Server Time)".


Upload one or more files to be pushed to the server prior to executing the command. The file push occurs immediately before the command is executed, so you can update the files anytime, and know that the next time your command runs, it will have the latest update. There are no file type restrictions.

Note:  There is currently a 1MB size limitation per file attachment and in the command results logging. 

Command Results

After a command has executed, the bottom pane of the Commands page will provide the administrator the exit code as reported by the system.  Any errors from the command that are passed through the OS or stdout and will be displayed in the Log portion of the command result's details. Refer to the OS or script documentation to resolve those errors. The error code displayed will be the error associated with the last instruction in the command, unless there is logic within the command itself that causes the command to exit prematurely.

Note: Any Exit Codes that may be displayed for command events are reported directly from the target system(s) shell and is handled by the command, script or program from which it was executed.

However generally "0" indicates a successful run, "1" indicates a failure condition, -1 indicates a timeout occurred, and " " indicates that the error could not be interpreted.

Commands for Macs | JumpCloud Tutorial


Last Updated: Feb 19, 2019 04:08PM MST

Related Articles
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found