Install LarisVMS
Three MSI installers: one web server, a recorder node on each recording machine, and optional media proxies.
Download LarisVMS 0.211.0
Released · Windows x64 · Release notes
- Web server Install on the server. Includes the web UI and API, and carries node/proxy builds for auto-update.LarisVMS-Web-0.211.0-x64.msi (304 MB)
- Recorder node Install on each machine that records cameras.LarisVMS-Node-0.211.0-x64.msi (141 MB)
- Media proxy Optional. Relays video for remote sites or low-bandwidth links.LarisVMS-Proxy-0.211.0-x64.msi (73 MB)
All versions, checksums, and source archives are on GitHub Releases.
Requirements
- Operating system: any 64-bit Windows version supported by .NET 10, for both the server and the recorder nodes. The MSIs are self-contained, so no .NET runtime is needed.
- Server: SQL Server (Express works) using SQL or Integrated authentication. For SQL Server Express, the
server name is
.\SQLEXPRESS. - Each recorder node: FFmpeg (
winget install ffmpeg --scope machine). - AI detection (optional): a GPU and its driver, or CPU only. NVIDIA needs CUDA Toolkit 12.x and cuDNN 9.x for CUDA or TensorRT acceleration; otherwise DirectML works out of the box. See AI hardware.
- Cameras: IP cameras with an RTSP stream (H.264 or HEVC). The current release adds cameras through ONVIF (Profile S or T); plain RTSP cameras are coming soon.
- Browser: a current Chrome, Edge, Firefox, or Safari. HEVC playback depends on browser support. On phones, Chrome (Android) or Safari (iOS).
Performance depends on your hardware: how many cameras and AI detection streams a node can handle comes down to its CPU, GPU, disks, and network.
Double-click an installer to be prompted for its settings, or pass them on the command line. Anything not given on the
command line is asked for. In a silent install (/qn), a missing required value stops the install with a
message naming the property.
1. Install the web server
msiexec /i LarisVMS-Web-0.211.0-x64.msi
# silent, with a certificate:
msiexec /i LarisVMS-Web-0.211.0-x64.msi HTTPSPORT=8444 CERTPATH=C:\certs\vms.pfx CERTPASSWORD=secret /qn| Property | Default | Purpose |
|---|---|---|
HTTPSPORT | 8444 | HTTPS port, plus its firewall rule. |
CERTPATH, CERTPASSWORD | blank | Server certificate (.pfx). Blank uses a self-signed certificate; a renewed file at the same path is
picked up automatically. A certificate your devices trust is also needed to install LarisVMS as a phone app. |
SERVICEACCOUNT, SERVICEPASSWORD | LocalSystem | Service account, for example one with SQL Integrated Security rights. |
INSTALLFOLDER | C:\Program Files\LarisVMS\Web | Install location. |
2. Run the setup wizard
Browse to https://<server>:8444/. The wizard sets up the database connection, the first admin account, and
the branding, and shows the node registration key. You can find the key again later under
Settings → Node defaults.
3. Install recorder nodes
Install FFmpeg on each recording machine first, then the node:
winget install ffmpeg --scope machine
msiexec /i LarisVMS-Node-0.211.0-x64.msi SERVERURL=https://<server>:8444 REGISTRATIONKEY=<key> STORAGEROOT=D:\Recordings /qn| Property | Default | Purpose |
|---|---|---|
SERVERURL, REGISTRATIONKEY | required on first install | Where the node registers. Not needed again once it's registered. |
STORAGEROOT | Where the node records. | |
ARCHIVEROOT | Second volume that receives aged-out footage. | |
FFMPEGPATH | auto-detected | Path to ffmpeg.exe. |
LIVEPORT | 8554 | Live video port, plus its firewall rule. |
INSECURETLS | 1 accepts the server's self-signed certificate. | |
CLIENTPORT, CLIENTENDPOINTHOST, CLIENTPFXPATH, CLIENTPFXPASSWORD,
CLIENTALLOWINSECURE | Lets browsers stream directly from this node. | |
SERVICEACCOUNT, SERVICEPASSWORD | LocalSystem | Run as an account that can reach SMB storage. |
INSTALLFOLDER | C:\Program Files\LarisVMS\Node | Install location. |
The node registers itself and appears under Settings → Nodes.
4. Install media proxies (optional)
msiexec /i LarisVMS-Proxy-0.211.0-x64.msi SERVERURL=https://<server>:8444 REGISTRATIONKEY=<key> CLIENTPORT=4443 /qn
Properties: SERVERURL, REGISTRATIONKEY, CLIENTPORT (default 4443),
CLIENTENDPOINTHOST, CLIENTPFXPATH, CLIENTPFXPASSWORD, CLIENTALLOWINSECURE,
INSECURETLS, SERVICEACCOUNT, SERVICEPASSWORD, INSTALLFOLDER, with the
same meanings as for the node.
5. Add cameras
Use Cameras → Discover, or add a camera by its ONVIF device service URL. Then assign each camera to a recorder node. Adding a camera by its RTSP URL is coming soon. For everything else, open Help in the sidebar.
6. Use it on your phone (optional)
Open the same address in your phone's browser. To install it as an app, choose Install app from the ⋮ menu
in Chrome on Android, or Share → Add to Home Screen in Safari on iOS. Phones won't install a site that uses
the self-signed certificate a fresh install starts with, so set CERTPATH to a certificate
your devices trust first.
Upgrading
Run the new version's MSI. Its settings are remembered from the previous install, so no properties are needed; secrets aren't stored, so a custom service account's password is asked for again. The web app applies database migrations itself when it starts. Upgrades never touch recordings, configuration, node registration, or the data-protection keys.
Recorder nodes and media proxies also update themselves. A new web install registers the node and proxy builds it carries as Pending under Settings → Node builds. Once you approve one, every older node downloads it, verifies its SHA-256, and installs it on its next check-in.
Uninstalling
Uninstalling removes the program, its service, and its firewall rules. Recordings, configuration, and everything under
%ProgramData%\LarisVMS are kept. Back up %ProgramData%\LarisVMS\keys: without it, encrypted
settings (camera, SMB, node, and email credentials) can't be recovered.
Installing from source
PowerShell scripts in the repository build from source and install on the same machine, taking the same settings as the MSIs. See the README for details.