Tasks and Task Results

Lanview uses tasks to track work sent to managed devices.

Most actions create tasks, including remote commands, package deployments, file transfers and device power or session actions.

Where to view tasks

Tasks can be viewed in several places:

• the Tasks module in Lanview Studio
• the Task Pane
• the Task List page in the Device Window
• feature-specific status views, such as package deployment or remote execution pages

The Tasks module is the full task view. Use it to review work across devices, inspect status and results, and find historical tasks.

The Task Pane is a compact view intended for checking current or recent task activity while working elsewhere in Studio. Open the full Tasks module when you need more detail or need to review tasks across several devices.

The Task List in the Device Window is limited to the selected device.

Task lifecycle

A task normally begins when an administrator requests an action.

Lanview records the request, sends the work to the target device or devices where applicable, and records the status returned by the Client.

A task may move through states such as queued, running, completed, failed or cancelled, depending on the feature and action type.

Task results

A task result records the outcome returned by the device or by Lanview.

Results may include status information, exit codes, summaries or command output depending on the action.

Task results should be interpreted in context. A completed task means the Lanview action reached a completed state. It does not always mean the wider activity succeeded.

For example, a command may run successfully but return an application-level error. A software deployment may start correctly but fail because the installer rejected its arguments. A Windows Update scan may complete without installing anything.

Cancelling tasks

Some tasks may be cancelled from Lanview Studio or the console.

Cancellation does not guarantee that device-side work has stopped. If work has already started, Windows or the application being run may continue to process it.

After cancelling a task, review its result and check the related feature or device state.

Sensitive task output

Task results can contain operationally sensitive information.

Remote command output, script output, installer logs or error messages may include paths, usernames, application names or configuration details.

Avoid placing credentials, tokens or other secret material in commands or scripts.

Permissions

Task viewing and cancellation may be controlled by task-specific permissions and by the permissions for the feature that created the task.

For example:

• package deployment permissions apply to package-related tasks
• service permissions apply to service operations
• Windows Update permissions apply to update tasks
• remote execution permissions apply to command and script tasks

Console access may also require server.console and the relevant feature permission.

Audit behaviour

Tasks are linked to the feature that created them. Tasks themselves are not a substitute for the audit log.

State-changing actions are audited according to their feature, such as package deployment, service control, remote execution, Windows Update or remote support.

Use task results to see what happened on the target device. Use the audit log to see who requested the action, when it was requested and which policy conditions applied.

Console commands

Related console commands include:

action.list
command.list
tasks.view
tasks.cancel

Common problems

A task is still running

The target device may be busy, offline, slow to return output or still processing the requested action.

A task failed

Open the task result and review the returned status. Then check the documentation for the feature that created the task.

A cancelled task still appears to do something

Cancellation may not stop device-side work that has already started. Confirm the device state after cancellation.

Guidance

Use the Tasks module for detailed review and the Task Pane for a quick view of current activity.

For investigation and accountability, review task results alongside the audit log.