NinjaOne - Run Scripts on Device
  • 21 Nov 2024
  • 2 Minutes to read
  • Dark
    Light
  • PDF

NinjaOne - Run Scripts on Device

  • Dark
    Light
  • PDF

Article summary

NinjaOne - Run Scripts on Device runs scripts on:

  • Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

Note:

Required Fields

These fields must be configured to run the Enforcement Set.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

  • Use stored credentials from Ninja One (RMM) adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.

    • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
    Note:
    To use this option, you must successfully configure a Ninja One (RMM) adapter connection.
  • NinjaOne (RMM) Script ID - Enter the Script ID.

  • NinjaOne (RMM) Run Script As - An identifier that specifies the permissions' context under which the script will run on the device.

  • Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

Additional Fields

  • Host Name or IP Address - The hostname or IP address of the Ninja One (RMM) server.
  • Client ID and Client Secret - Credentials to connect to the Ninja One (RMM) server. Refer to the adapter's Required Permissions to learn how to obtain them.
  • Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
  • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
  • HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the  HTTPS Proxy.
  • HTTPS Proxy Password (optional) - The password to use when connecting to the server using the  HTTPS Proxy.
  • Gateway Name - Select the Gateway through which to connect to perform the action.

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have permission to perform this Enforcement Action.


For more details about other Enforcement Actions available, see Action Library.



Was this article helpful?