Server Startup Configuration

Lanview Server uses startup configuration to apply settings and start its network services when the Windows service starts.

Where to edit startup configuration

In Lanview Studio, open Settings > Server > Startup Configuration.

Use the Startup Configuration editor provided by Studio rather than editing the Server file directly. Studio submits the configuration to Lanview Server so it can be validated, backed up and applied through the supported administration path.

Access requires the relevant Server settings permission.

What startup configuration does

Startup configuration can define Server runtime behaviour such as:

  • connection ports
  • device presence timings
  • automatic ping behaviour
  • Wake-on-LAN settings
  • audit settings
  • remote access policy
  • Client identity mode
  • file cache settings
  • task and transfer limits
  • package policy settings
  • notification settings

It can also start Lanview networking using server.start.

Installer preservation

The Server installer installs a default startup configuration only when one is missing.

Existing startup configuration is preserved during repair, reinstall and upgrade.

Runtime commands and startup configuration

Some config.* commands affect the running Server. A runtime change is not necessarily retained after the Server restarts.

Where a setting must remain in effect, update it through the Startup Configuration editor or the documented persistent settings option.

Useful commands

server.start
config
config.listenport
config.audit.mode
config.clientidentity.mode

Cautions

Invalid startup configuration can prevent Clients or Studio from connecting.

Startup configuration uses Lanview console command syntax; it is not a Windows batch file.

Do not place passwords, recovery codes, tokens or licence material in startup configuration.