Setting up and managing Remote Actions
Configure the Remote Actions module and its content to ensure Remote Actions users can fully benefit from it without interruptions.
Review the Remote Actions technical prerequisites outlined in the Before you begin section on this page.
View and configure out-of-the-box remote actions.
See the auto-installed system remote actions available after the module is enabled.
See the library remote actions available within dedicated Library packs.
See guides on how to create and configure remote actions.
See how to manage remote actions configured in your Nexthink instance.
Before you begin
Nexthink Administrators must complete the following technical prerequisites to ensure all required system components and settings are correctly in place.
Validate Collector version and settings
Ensure all employee devices have Collector deployed and running:
Execution policy other than Default must be configured on the Collector, to ensure remote actions can run on the device.
For running remote actions as a service on Windows Server devices, Collector version 24.5 or later is required.
Fur running remote actions with Campaigns, Collector version 23.5 or later is required.
For more information on execution policy options, refer to:
Set permissions
Nexthink Administrators should enable permissions to ensure the correct configuration and monitoring of Remote Actions.
For detailed information about available permissions, View domain options and Data privacy granularity settings, see:
Key Remote actions configuration concepts
Configuring remote actions for each use case
How you use remote actions depends on your purpose and your chosen trigger method. Nexthink has identified four main scenarios or use cases:
Assisted service
Use remote actions to help support teams assist employees.
Set a manual triggering mechanism to allow support agents to execute remote actions from Investigations, Device View, or Amplify.
Optionally, associate your remote action with a specific property or metric within a checklist available from Device View or Amplify.
Self-help
Use remote actions to help employees solve issues without requiring external intervention from support.
Set a remote action triggering mechanism via Spark and enable Spark's permission to execute it on employee devices.
Run remote actions in conjunction with Nexthink Campaigns in self-help scenarios. Use campaigns to notify employees about issues and ask them to take action.
How you run self-help remote actions depends on whether the script payload requires administrative privileges. Run the remote action:
In the context of the current active user, if the action requires no special privileges.
In the context of the local system account, if the action requires administrative privileges.
Refer to the Creating and configuring remote actions > Advanced configuration documentation for more information.
Additionally, Remote Actions utilizes an API to programmatically launch remote actions, extending their availability to third-party products, such as self-service portals or ticketing systems. Refer to the Remote Actions API documentation for more information.
Self-healing
Use remote actions to fully automate the remediation of specific issues on employee devices, avoiding human intervention.
Schedule remote actions to run automatically on one or more devices using Nexthink Query Language (NQL). Consider the frequency of execution for this type of remote action. Monitor their success with remote action dashboards.
Set a remote action trigger to Workflow and include it as part of an automated process.
Refer to the Remote action thinklet documentation for information.
On-demand data
Use remote actions to get additional data from devices and incorporate it into Nexthink.
Schedule remote actions periodically on specific devices to gather additional information that Nexthink does not collect by default.
Make a diagnostic remote action available for Spark to accelerate troubleshooting.
Refer to the Manage remote actions documentation for more information on how to execute remote actions on demand using Nexthink Query Language (NQL).
System remote actions
Remote Actions module includes system remote actions available in your Nexthink instance by default. This helps you extend Nexthink diagnostics capabilities, enhance troubleshooting and populate dashboards with additional, specific data points.
Go to Manage Remote Actions page and find remote actions with System origin.
Go to Nexthink Library and select specific system remote action to find out more.
System Remote actions do not impact your maximum license count.
Remote actions from Nexthink Library
Install and customize remote actions from the Nexthink Library to enhance Nexthink diagnostics and remediation capabilities across various areas.
Refer to Library packs for more information.
Last updated
Was this helpful?