# Fleet Deployment
Silent install and fleet deployment of Vrex on Windows
Deploy Vrex silently across multiple Windows machines using Intune, SCCM, or a deployment script.

## Install model

Vrex installs per-user, not per-machine. The installer targets the current user's profile:

```
%USERPROFILE%\AppData\Local\Programs\VrexLauncher2.0\
```

This means the deployment script runs in user context, and each user gets their own installation. There is no official system-wide installation path — see [Workarounds](#workarounds) if you need one.

## Silent install

Download the installer from [vrex.no/download](https://vrex.no/download), then run:

```
VrexLauncher##.exe -silent
```

Replace `##` with the version number in the downloaded filename. The installer creates Start menu shortcuts and sets up the launcher. No user interaction is required.

## Auto-update behaviour

The Vrex Launcher checks for updates automatically on startup and keeps the application current. This means:

- You only need to distribute the installer once
- Users always run the latest version after their first launch
- **Users with an outdated version will see a warning**, and mismatched versions across participants in a session may break collaboration

If version control matters for your environment, see the bypass workaround below.

## Licensing at scale

SSO is the right path for fleet deployments. Once SSO is configured, user accounts are created automatically at first login — no manual licence assignment, no per-user setup.

See [SSO Setup](/v2/it/sso) for the full configuration guide. To start the SSO process, email [admin@vixel.no](mailto:admin@vixel.no).

## Workarounds

These approaches are **not officially supported or tested by Vrex**. They can work depending on your deployment setup, but treat them as workarounds, not standard paths.

**Per-machine installation**
There is no system-wide installer. Workaround: install on one machine, then distribute the installed application folder to other machines. Shortcuts will need to be created or deployed separately.

**Offline installation**
There is no offline installer. The standard installer always fetches the latest version. Workaround: perform a full online install on one machine, then distribute the installed folder to offline machines manually.

**Bypassing the launcher (version pinning)**
The launcher auto-updates. To control which version users run, change the shortcut target to point directly to `Vrex.exe` instead of `VrexLauncher.exe`. Users will not receive automatic updates and will see version warnings when their version is outdated. Mismatched versions may break session collaboration.

## Need a custom deployment?

For larger or complex rollouts, email [support@vixel.no](mailto:support@vixel.no). Include your deployment tool, expected user count, and any specific constraints.