Logs and Diagnostics

Lanview provides logs, audit records and diagnostic commands to help administrators investigate operational issues.

Diagnostic information can contain sensitive operational data. Review and redact it before sharing outside the organisation.

Default log locations

The default log locations are:

ComponentDefault location
Lanview ServerC:\ProgramData\Infinityscape\Lanview\Server\Logs\
Lanview ClientC:\ProgramData\Infinityscape\Lanview\Client\Logs\
Lanview Studio%LOCALAPPDATA%\Infinityscape\Lanview\Studio\Logs\
Lanview Agent%LOCALAPPDATA%\Infinityscape\Lanview\Agent\Logs\

%LOCALAPPDATA% refers to the profile of the Windows user running Studio or Agent.

Use server.paths in AdminConsole when you need to confirm the Server paths for the installed version.

Diagnostic sources

Common diagnostic sources include:

  • Lanview Server logs
  • Lanview Client logs
  • Lanview Agent logs
  • Lanview Studio logs
  • audit records
  • command history
  • task results
  • Server connection and session diagnostics

Studio diagnostics

Studio can display Server diagnostics through the Console when the signed-in user has the required permissions.

Studio's local logs help diagnose startup, connection and display issues on the administrator workstation.

Server diagnostics

Useful Server diagnostic commands include:

server.status
server.paths
server.selftest
server.bindcheck
server.sessions
admin.listener.status
admin.pipeinfo
network.interfaces

Command and action history

Lanview can show recent command and operator action history using commands such as:

command.list
action.list
command.meta <command>

Command history is useful for operational troubleshooting. It is not a complete forensic record on its own.

Audit diagnostics

Audit records can be searched and viewed through audit commands and Studio audit views.

Useful commands include:

audit.show
audit.find
audit.event.show <eventId>
audit.selftest

Audit data can include administrator names, target devices, reasons and operational context. Handle exports carefully.

Redaction before sharing

Before sharing diagnostics, remove or mask:

  • usernames where not required
  • device names where not required
  • domains and internal hostnames
  • Internet Protocol (IP) addresses where not required
  • file paths that reveal sensitive structure
  • command output containing secrets
  • passwords, tokens, keys, recovery codes or licence material

Do not paste raw logs into public forums or third-party systems without review.