Process Management
Lanview can view, start and terminate running processes on managed Windows devices where the user has the required permissions.
Process management is useful for support and diagnostics, but starting or terminating processes can affect users, applications and system stability.
Supported process actions
| Action | Availability | Purpose |
|---|---|---|
| List processes | Studio and console | View running processes on a device. |
| Start process | Studio and console | Start a process on a device. |
| Kill process | Studio and console | Terminate a process immediately. |
| Close process | Console only | Request that a process closes normally where supported. |
Group equivalents may be available for some console actions.
Close and kill
The Studio interface provides Kill, which terminates the selected process. This can cause unsaved work, data loss or application errors.
A normal Close request is available through the Lanview console rather than the Studio process list. Where a normal close is suitable, prefer it before using Kill.
Execution context
Process start commands can run in different execution contexts, such as system or user context.
These modes are not interchangeable. A command that works in one context may fail or behave differently in another.
Avoid command lines containing passwords, tokens, licence keys or connection strings.
Where to manage processes
Open the relevant process or task view in the Device Window to view running processes and use the available Studio actions.
The Run New Task dialog can be used to start a supported process.
Required permissions
| Permission | Allows |
|---|---|
device.task_list.view | View running processes on devices. |
device.task_list.start_process | Start processes on devices. |
device.task_list.kill | Terminate running processes on devices. |
groups.target | Target supported process actions at groups. |
Audit behaviour
Lanview audits process actions.
Audit records may include:
- process list requested
- process start requested
- process close requested
- process kill requested
- command or task result data
Process actions can require an audit reason when reason prompts are enabled.
Console commands
Related commands include:
device.process.list <deviceId|machineName> [/filter "text"] [/paths]
device.process.start <deviceId|machineName> /system [options] -- <raw command line>
device.process.start <deviceId|machineName> /user [options] -- <raw command line>
device.process.close <deviceId|machineName> /pid <processId>
device.process.kill <deviceId|machineName> /pid <processId> [/tree]The options available for system and user execution are shown in the command reference for the installed version.
Good practice
- Prefer a normal close before killing a process where possible.
- Avoid broad group process actions unless the impact is understood.
- Do not use command lines that expose credentials.
- Review task results after process actions.
- Require reasons for disruptive process control where appropriate.