Lanview DocsSupport and administration
Docs / Installation

Deploying Lanview Client

Lanview Client is installed on Windows devices that will be managed by Lanview.

The Client runs as a Windows service, connects to Lanview Server and provides the device-side functionality required for management, inventory, tasks and support features.

Before deploying

Before deploying Lanview Client, confirm:

  • Lanview Server is installed and running.
  • You know the Lanview Server DNS name or IP address.
  • You know the Client connection port, normally 45750.
  • Firewall rules allow the Client device to reach Lanview Server.
  • The device approval process has been agreed.
  • The required roles and permissions have been configured in Lanview.

Deploy to a small number of test devices before wider rollout.

Install Lanview Client

Run the Lanview Client installer on the target Windows device.

Lanview Client installs the Client service and the components required for supported user session features.

The Client application files are installed under:

C:\Program Files\Infinityscape\Lanview\Client\

Client runtime data is stored under:

C:\ProgramData\Infinityscape\Lanview\Client\

Interactive installation

During an interactive installation, the installer can prompt for the Lanview Server host and port when configuration is required.

Enter the Server details that the Client device should use to reach Lanview Server.

Silent installation

Lanview Client can be deployed silently using installer properties.

Example:

msiexec /i Lanview.Client.msi SERVERHOST=server01 SERVERPORT=45750 /qn

Replace server01 with the correct Lanview Server host name or IP address for your configuration. We recommend testing this on one device first before deploying the MSI to multiple stations. It is always worth running NSLookup on the server name before deploying it to ensure DNS is configured correctly.

If a fresh Client installation does not receive the required Server configuration, the Client service will not be able to connect to Lanview Server.

After installation

After Lanview Client is installed and configured, it connects to Lanview Server.

New devices appear in Lanview Studio in the Pending approval group. They are not available for management until an authorised Lanview user approves them.

Device approval

Use Lanview Studio to review pending devices.

Only approve devices that are expected and recognised. Device approval is a trust decision, especially when devices are being rebuilt, replaced or reassociated with existing records.

Client and Agent

Lanview Client runs as a Windows service and performs managed device operations.

Lanview Agent supports features that need the logged-in user session, such as user visible prompts and Lanview-native Remote View. Agent will be set to launch at every user login.

Both components should be installed and running for the full set of Client side features to work.

Deployment methods

Lanview Client can be deployed using the organisation’s preferred Windows software deployment method.

Possible approaches include:

  • Manual installation for testing.
  • Silent installer deployment.
  • Software deployment tools.
  • Group-based or staged rollout.
  • Build or provisioning processes.

Choose a deployment method that fits your operational procedures and allows rollback or support if a deployment issue is found.

Verifying deployment

After deploying Lanview Client, confirm:

  • The Client service is installed and running.
  • The device appears in Lanview Studio.
  • The device can be approved.
  • Device details update after approval.
  • Inventory and status information are received.
  • User session features work where required.

Troubleshooting

The device does not appear in Lanview Studio

Check the Server host name, Client connection port, firewall access and Client service status. Check in the Pending Approval Group.

The Client service does not start after installation

Confirm that the Client received the required Server configuration during installation.

The device appears but cannot be managed

Check whether the device is still pending approval, rejected, blocked or otherwise unavailable for management.

User session features are unavailable

Check that Lanview Agent is installed and running in the user session.