For the complete documentation index, see llms.txt. This page is also available as Markdown.

Working with Remote Actions

To start using Remote Actions:

Key Remote Actions concepts

Nexthink Remote Actions allows you to execute small scripts on employee devices. Remote actions provide a number of opportunities for the prevention and remediation of issues encountered by employees, as well as for gathering additional information from endpoints running Nexthink Collector.

Remote action targets and purpose

Remote action administrators define the target and purpose of each remote action based on the intended use case.

  • Target: Remote actions can target devices, VDI sessions, or both. For example, device-targeted actions can collect hardware information or remediate memory issues, while VDI-targeted actions can gather server status information or log off sessions.

    • The selected target determines the context in which the remote action is used and how it interacts with other Nexthink features.

  • Purpose: Remote actions can be designed for data collection, remediation, or both. Data collection actions gather information from targeted devices or sessions, while remediation actions perform changes or corrective actions. This classification helps organize and identify remote actions in dashboards.

Remote actions execution methods

Remote actions can be triggered with one of the following methods:

  • Manual: triggered directly by a user through the Nexthink web interface.

  • Scheduled: launched automatically based on defined targeting and timing rules.

  • API: triggered by API calls

  • Workflow: triggered during the execution of a workflow.

  • Spark: triggered by Spark to automatically collect information or remediate the issue upon employee approval.

Refer to Executing remote actions for more information.

Remote Action dashboards

Effortlessly keep track of the success of remote actions across your entire organization through advanced Remote Action dashboards.

Last updated

Was this helpful?