Remote Commands

Remote Commands allow authorised Lanview users to run commands or scripts on managed Windows devices.

They are used for support, diagnostics, maintenance and controlled administration tasks where direct access to the device is not required.

Remote Commands are powerful and should be assigned only to roles that genuinely need them.

Command types

Lanview supports different remote execution surfaces depending on configuration and permissions.

These can include:

• Command Prompt commands
• Windows PowerShell commands
• PowerShell 7 commands
• saved script execution
• device targeted execution
• group targeted execution

PowerShell 7 must exist on the target device before it can be used successfully. The presence of a Lanview permission does not install PowerShell 7 on the endpoint.

Running commands

Remote Commands can be started from supported device or group actions in Lanview Studio.

The user selects the command type, target and command or script content. Lanview checks permissions and reason policy, then sends the work to the target device or devices.

Lanview Client performs the device-side execution and returns status and output.

Device and group targeting

A command can target a single device or a group.

Group targeting should be used carefully. A command that is safe on one device may cause disruption when run across many devices.

Use smaller groups or test targets before running high-impact commands more widely.

Permissions

Remote execution permissions include:

The effective permission check depends on the command type and target.

Reasons and audit prompts

Lanview can require a reason before allowing remote execution.

Reasons are stored with the audit record and are commonly used to link the action to a support ticket, change request, incident or approved maintenance activity.

The organisation using Lanview defines what is considered a valid reason.

Audit behaviour

Lanview audits remote execution requests and results.

Audit records can include who requested the command, which device or group was targeted, what type of execution was requested and the result returned by the device.

Command text and output may contain sensitive data. Avoid commands and examples that include real credentials, tokens, recovery keys or private configuration values.

Common problems

The command does not run

Check the target device is online, the user has the required permission and the selected command type is supported on the target device.

PowerShell 7 commands fail

PowerShell 7 must be installed on the target device. Use Windows PowerShell where PowerShell 7 is not available.

Output looks incomplete

The command may still be running, may have written output elsewhere, or may have failed before producing the expected text. Check the task result and exit status.

A group command affected unexpected devices

Review group membership before running group targeted commands. Group membership determines the target set.

Console commands

Remote execution commands are listed in the command reference.

Guidance

Prefer scripts for repeatable work and ad hoc commands for short, low risk checks.

Avoid command lines that contain credentials. Command history and task output should be treated as sensitive operational data.