Installing Lanview Server
Lanview Server is the central service for a Lanview installation. It should be installed before Lanview Studio is installed and before Lanview Client is deployed to managed devices.
Lanview Server manages device state, security, settings, audit records, repositories and communication with managed Clients.
Before installing
Before installing Lanview Server, decide:
- Which Windows device or server will host Lanview Server.
- What DNS name or IP address Lanview Studio and Clients will use to reach it. We recommend DNS name so that if the IP address changes, the client devices will not need to be updated.
- Which network ports will be used.
- Which administrators will have Server access.
- Whether firewall rules are required.
- How Server backup and recovery will be handled.
The default Client connection port is 45750.
The default Studio administration port is 45751.
Install Lanview Server
Run the Lanview Server installer on the device that will host the Server.
The Server installer installs the Lanview Server application files and registers the Lanview Server Windows service.
The Server service is configured to start automatically. After installation, confirm that the service is running before continuing with Studio setup or Client deployment.
Server installation location
Lanview Server application files are installed under:
C:\Program Files\Infinityscape\Lanview\Server\Lanview Server runtime data is stored under:
C:\ProgramData\Infinityscape\Lanview\Server\Runtime data is owned by Lanview Server. Administrators should use Lanview Studio and documented configuration methods rather than editing Server-managed data directly. Editing any configuration outside of Studio is unsupported.
Lanview AdminConsole
Lanview AdminConsole is installed with Lanview Server.
AdminConsole is intended for local Server administration and recovery operations. It is not a replacement for Lanview Studio as the normal administration interface. This tool is only installed with Lanview Server and not Lanview Studio or Client.
Use AdminConsole only where local Server-level access is appropriate.
First administrator account
A new Lanview Server requires an initial administrator account.
The first administrator is created through the supported Server bootstrap process. This can only be run once.
Creating the first admin account
- Open Lanview AdminConsole from the start menu on the Lanview Server device.
- Type bootstrapadmin in the console
- You will be guided through creating the default account. It is important to give all users a full name because this is seen by users when approving remote access and the central audit also logs full names.
- The password must meet standard complexity rules. The password can be any length and contain any characters.
Do not forget the username and password created here there is no way to reset or recover the admin account without a fresh install.
After the first administrator account has been created you can close the AdminConsole and install Studio.
All future new users can be created in Lanview Studio.
Connecting from Lanview Studio
After Lanview Server is installed and running:
- Install Lanview Studio on an administrator workstation.
- Open Lanview Studio.
- Enter the Lanview Server host name or IP address.
- Connect to the Studio administration port.
- Sign in using a Lanview administrator account.
If two-factor authentication is required, Lanview Studio will guide the user through verification or setup.
Server settings
Lanview Server settings are managed through supported Lanview interfaces.
Common settings include:
- Authentication and two-factor authentication.
- Audit mode and retention.
- Reason prompts for sensitive actions.
- Client and Studio connection port configuration.
- Remote View and Remote Control policy.
- Remote Desktop Protocol (RDP) defaults.
- Client identity rollout policy.
- Package, transfer and repository settings.
Very few settings require a Server restart or service restart depending on the setting and deployment stage.
Firewall and network access
Lanview Studio and Lanview Client must be able to reach Lanview Server on the configured ports.
The Lanview MSI installers create the normal Windows Firewall rules. Group Policy, endpoint security software or a later firewall configuration can replace or remove those rules.
The default Server rules are:
| Purpose | Direction on the Server | Protocol and port | Typical source |
|---|---|---|---|
| Client connections | Inbound | TCP 45750 | Managed Windows devices |
| Studio administration | Inbound | TCP 45751 | Administrator workstations |
Use the configured replacement ports if the defaults have been changed.
Wake-on-LAN uses outbound User Datagram Protocol (UDP), normally port 9, from Lanview Server to the relevant broadcast address. Microsoft Remote Desktop Protocol (RDP) uses its own Windows and firewall configuration and is separate from the Lanview Server ports.
Where Group Policy manages Windows Firewall:
- Create inbound rules for the configured Client and Studio ports.
- Limit the Client rule to the networks containing managed devices where practical.
- Limit the Studio rule to trusted administrator networks or workstations.
- Apply the policy to the Lanview Server device.
- Confirm that the rules remain enabled after Group Policy refresh.
- Test one Client connection and one Studio connection before wider deployment.
Do not expose the Studio administration port to networks that do not require Lanview administration access.
Verifying installation
After installation, confirm:
- The Lanview Server service is running.
- Lanview Studio can connect to the Server.
- The first administrator account can sign in.
- Server settings can be viewed by an authorised user.
- Test Clients can connect and appear for approval.
- Audit records are being created for sign in and administration activity.