Skip to content

Windows client

The Windows client is a single setup EXE. It installs a background service plus the tray app; after that the machine keeps itself up to date automatically. Installing needs administrator rights once — your users never do.

Prerequisites

  • A running backend (Community or Pro).
  • Windows 10 or 11, x64 or ARM64, and administrator rights on the machine.
  • The installer. Two ways to get it:
    • Your backend's downloads page — https://vpn.example.com/downloads (public, hand this link to anyone). It serves whatever you've published on Admin → Releases.
    • The pre-configured package — on Admin → Releases → Windows, click Download installer package: a ZIP with the installer plus a settings file that bakes in your server address, so step 3 below is skipped entirely. Use this for rollouts.

Steps

1. Run the installer

Run the setup EXE on the target machine and follow the wizard. It installs the service and the tray app and starts both.

2. Enter your server address

If you used the plain installer (not the pre-configured package), the tray icon asks for the server address on first run. Enter your backend hostname — for example vpn.example.com (the https:// is fixed) — and confirm.

3. Activate the machine in the admin panel

The machine now appears in your admin panel as a pending client (the Overview page shows a Pending counter — click it). Open the new client, assign it to its customer, and click Activate. The client picks this up on its own within a few minutes — nothing more to do on the machine.

Rolling out to many machines

The installer also runs fully unattended:

ValeniusSetup-x.y.z.exe /SILENT /BACKENDURL=https://vpn.example.com

or place the valenius-setup.ini from the installer package next to the EXE. Both suppress the first-run prompt — ideal for GPO/Intune deployment.

Verify it works

  1. The Valenius tray icon is visible on the machine.
  2. In the admin panel, the client shows as online (green) after activation.
  3. Give it a VPN profile (see First steps) and click Connect in the tray — the icon shows a green check when the tunnel is up and verified.

Common problems

The machine never appears as pending in the admin panel. The server address is wrong or unreachable from the machine. Click the tray icon — if it still asks for the server address, re-enter it. The backend must be reachable at https://<your-host>/ with a valid certificate.

Two entries with the same name, one pending. The machine was reinstalled from scratch and got a new identity. Delete the old entry, then activate the new one.

The first-run prompt keeps coming back. The address you entered didn't answer. Check for typos and confirm the URL opens in a browser on that machine.

Updates: do I ever reinstall by hand? No. Once installed, the service checks your backend hourly and updates itself silently — publishing a new version on Admin → Releases is all you do. Learn more →