Docs / FAQ

Frequently Asked Questions

This page answers common questions about Lanview scope, setup, security, audit and day-to-day administration.

General questions

What is Lanview used for?

Lanview is used to manage Windows devices on a local area network. It provides device management, remote support, inventory, package deployment, remote administration, monitoring, audit and settings features through Lanview Server, Lanview Studio, Lanview Client and Lanview Agent.

Is Lanview cloud based?

No. Lanview is designed for local Windows device management on a LAN.

Does Lanview need a browser-based management portal?

No. Lanview Studio is the primary administrator Windows desktop application. Lanview is administered through Studio, supported commands and Server components rather than a browser-only management portal.

Does Lanview require a subscription?

No. Lanview is a perpetual licence. You only buy the licence once for each major version.

Which Windows devices can Lanview manage?

Lanview manages Windows devices running Lanview Client. Check the installer and release information for supported operating system details for your version.

Components

What is the difference between Server, Studio, Client and Agent?

Lanview Server stores management data, accepts Client connections, sends authorised actions and records audit activity.

Lanview Studio is the administrator application used to sign in, view devices, change settings and perform permitted actions.

Lanview Client runs on managed Windows devices and connects outbound to Lanview Server.

Lanview Agent is installed alongside Client and supports features that need access to the signed-in user session, such as user-visible messages and Lanview-native remote support.

Why do devices need approval?

A device is not managed just because Lanview Client has connected. New devices appear as pending until an authorised administrator approves, rejects, blocks or otherwise manages the device record.

What happens if a device is rebuilt or replaced?

Use the supported reassociation, reset or rebind options where available.

Remote access

What is the difference between Remote View and Remote Desktop?

Remote View and Remote Control are Lanview-native remote support features. Remote View starts as view-only, while Remote Control is a separate escalation that requires permission and policy allowance.

Microsoft Remote Desktop Protocol (RDP) is separate from Lanview-native remote support and depends on Windows RDP availability and configuration.

Does Lanview record remote sessions?

No. It does not record screen-frame, screenshot, typed-text or video recording when using Lanview Remote View and Remote Control.

Administration

Can Lanview deploy software?

Yes. Lanview includes package and deployment features for managing package content, assigning deployment actions and reviewing results.

Can roles restrict what administrators can do?

Yes. Lanview uses role-based access control (RBAC). Assigned roles determine which areas an administrator can view and which actions they can perform.

What gets audited?

Audit coverage includes catalogued administrative activity such as sign-in events, security changes, role changes, device approval, remote access actions, package actions, process and service actions, power and session actions, settings changes and denials.

Where to start

Start with the setup and overview articles, then move into the feature area that matches the task you need to perform.