Feature Overview: Scripts and Remote Execution

Lanview scripts and remote execution allow authorised administrators to run commands or saved scripts against managed devices.

This feature area includes the Script Repository, ad hoc remote commands, script execution and task result tracking.

What this feature area includes

Scripts and remote execution include:

  • A Server-managed Script Repository.
  • Script folders and saved script management.
  • Script creation, editing, moving, duplication and deletion.
  • Device and group remote command execution.
  • Device and group script execution.
  • Device Remote Console permissions for Command Prompt, Windows PowerShell and PowerShell 7.
  • Task and result tracking for remote execution actions.

Repository management and execution rights

Managing scripts is not the same as running scripts.

A user may have permission to view or edit saved scripts without having permission to execute them on devices. Execution permissions are separate because running commands or scripts on endpoints is a higher-risk administrative action.

Where to find it

Scripts and execution features appear in:

  • Studio > Scripts.
  • Remote Execute dialogs.
  • Device Window > Remote Console.
  • Studio > Tasks.
  • Studio Console for command metadata and command history.

Permissions and access

Common permission areas include:

  • Script repository view, create, edit, delete and folder management.
  • Device remote command execution.
  • Group remote command execution.
  • Device script execution.
  • Group script execution.
  • Remote shell permissions for Command Prompt, Windows PowerShell and PowerShell 7.

PowerShell 7 availability depends on the target device. The presence of a Lanview permission does not mean PowerShell 7 is installed everywhere.

Policy and settings

Remote execution is permission-controlled and Server-dispatched. Reason policy may apply to sensitive execution actions.

The Script Repository does not use a general inheritance setting.

Audit behaviour

Remote execution actions are audited where catalogued, including start, request and result events. Remote execution template events may also be recorded.

Script content, command lines and output can contain sensitive information. Do not include credentials, tokens, connection strings or recovery material.