Which Lanview Component Do I Need?
Lanview is made up of several components. Each one has a different job.
Use this page to decide which component applies to the task you are working on.
Lanview Server
Use Lanview Server when the task relates to central state, policy, security, audit, packages, settings, device records or command dispatch.
Lanview Server manages device state. Studio, Client and AdminConsole all work through Server-controlled behaviour.
Lanview Studio
Use Lanview Studio for normal graphical administration.
Studio is the main administrator application. Use it to view devices, approve devices, manage groups, review inventory, run permitted actions, manage security, configure settings and inspect audit information.
Studio does not directly own Server state. Server still enforces permissions and policy.
Lanview Client
Install Lanview Client on every Windows device you want to manage.
Client runs as the machine-level runtime on the endpoint. It maintains the connection to Lanview Server and executes Server-authorised device actions.
Lanview Agent
Use Lanview Agent for logged-in user-session features.
Agent supports actions that need to appear in, or interact with, the signed-in user's session. This includes user-visible messages and Lanview-native remote support behaviour. Agent does not replace Client and does not grant administrator authority by itself.
Lanview AdminConsole
Use Lanview AdminConsole for local Server administration from the Server machine.
AdminConsole is useful for first administrator bootstrap and local Server diagnostics. It is not required for day-to-day graphical administration when Studio is available.