Lanview DocsSupport and administration
Docs / Getting Started

First Setup Checklist

This checklist gives a practical order for setting up a new Lanview installation.

Use it as a high level guide before moving into the detailed installation and configuration articles.

1. Plan the Server location

Choose where Lanview Server will run.

The Server should be installed on a Windows device or server that is suitable for hosting the Lanview management service and can be reached by Lanview Studio and managed Clients. This does not need to be a Windows Server edition. It can be Windows 11 but it needs to be on at all times.

Before installation, confirm:

  • The Server DNS name or IP address that Clients will use. We recommend DNS name so that if the IP address changes, the client devices will not need to be updated.
  • The network ports that will be used for Client and Studio communication.
  • Whether access should be limited by firewall rules.
  • Who has access to administer the Server and who has access to the backend Lanview configuration files. This should be restricted.

2. Install Lanview Server

Install Lanview Server first.

After installation, confirm that the Lanview Server service is running.

3. Create the first administrator account

A new Lanview installation requires an initial administrator account.

The first administrator is created through the supported Server bootstrap process. This account is then used to sign in and complete the initial configuration. This must be done using the supported bootstrap process from Lanview AdminConsole. More detail is in the Installing Lanview Server section.

Do not rely on default credentials in setup procedures. Lanview uses a first administrator setup process rather than a shared default login. Consider making the first user account the break-glass account. Avoid using this for any normal use and instead use it for recovery purposes.

4. Install Lanview Studio

Install Lanview Studio on the administrator device. It can be a device that also has Lanview Client installed.

Open Lanview Studio and connect to Lanview Server using the Server host and administration port.

Sign in using the administrator account created during bootstrap setup.

If two-factor authentication is required by your configuration, complete the setup or verification process when prompted.

5. Review core Server settings

Before deploying Clients widely, review the main Server settings.

Important areas include:

  • Authentication and two-factor authentication.
  • Audit settings and reason prompts.
  • Device approval behaviour.
  • Remote View and Remote Control policy.
  • Remote Desktop Protocol (RDP) default port.
  • Client identity rollout policy.
  • Package, transfer and repository settings where used.

Avoid enabling high-impact features before roles, permissions and audit expectations have been reviewed.

6. Review users, roles and permissions

Use Lanview Security to review the built in roles and create any organisation specific roles.

At minimum, decide who should be able to:

  • Sign in to Lanview Studio.
  • View devices and groups.
  • Approve or reject devices.
  • Run remote support actions.
  • Run remote commands or tasks.
  • Manage packages and deployments.
  • View and export audit information.
  • Manage users, roles and Server settings.
  • Use AdminConsole where local administration is required.

Use the smallest practical set of permissions for each role.

7. Deploy Lanview Client to test devices

Install Lanview Client on a small number of test devices before deploying it widely.

A Client deployment normally needs the Lanview Server host and Client connection port. This can be set in the MSI GUI, or using command line properties. More information on how to do this will be in the 'Deploying Lanview Client' section.

After installation, the Client connects to Lanview Server and appears in Lanview Studio. However, you will not see new devices until they are approved. Open the Pending Approval group to see new devices and either approve or reject them.

8. Approve test devices

In Lanview Studio, go to the Pending Approval group and review the newly connected devices.

Approve only devices that you recognise and expect to manage.

After approval, confirm that the device appears correctly in Studio and that inventory or status information is being received. Inventory collection is not immediate on new devices. You can however speed this up by clicking Refresh Inventory in the device context menu.

9. Test common administration tasks

Before moving to wider deployment, test the tasks that your administrators will use most often.

This may include:

  • Viewing hardware and software inventory.
  • Opening the Device Window.
  • Reviewing services or events.
  • Running a safe test task.
  • Reviewing audit entries.
  • Testing Remote Desktop or Remote View and Control if enabled. Be aware by default the remote device will need to approve the Remote View and Control connection.
  • Confirming role restrictions using a non administrator account.

10. Prepare for wider rollout

Once the first devices are working correctly, prepare your wider deployment method.

This may include software deployment tooling, scripted installation, group-based rollout, support documentation, helpdesk procedures and internal approval steps.

Before rollout, confirm:

  • Client installation properties.
  • Firewall and connectivity requirements.
  • Device approval process.
  • Role assignments.
  • Audit expectations.
  • Support escalation process.
  • Backup and recovery approach.