Installing VCC 360 Desktop

We provide two Windows installers for VCC Live 360. Which one you need depends on how you install:

Quick guide — which one to download?

• Installing for yourself, on your own machine? → Use the .exe installer. No admin rights needed, one download, auto-updates included.
• IT admin deploying to many machines (Group Policy, Intune, SCCM/MECM, or any software-distribution tool)? → Use the .msi package. It installs per-machine, silently, and provisions the app for every user who logs in.

The EXE installer

The .exe (vcc-live-<version>.exe) is an NSIS installer, the standard format for Electron applications.

• Installs per-user into %LOCALAPPDATA% — no administrator rights required.
• Lets you choose the installation directory during setup.
• Includes the auto-updater: the app checks for new versions and updates itself in the background, so users always run the latest release without IT involvement.

Command-line flags

Example — silent per-user install that starts the app afterwards:

vcc-live-1.2.3.exe /currentuser /force-run /S

Silent uninstall:

"%LOCALAPPDATA%Programsvcc-liveUninstall VCC Live 360.exe" /S

The MSI package

The .msi (vcc-live-<version>.msi) exists for enterprise deployment. MSI is the format that Group Policy, Intune, and SCCM consume natively, with standardized silent installation and reliable version detection for inventory.

Our MSI is not a plain repackage of the app — it is a custom Active Setup provisioning installer:

1. The MSI installs per-machine (ALLUSERS=1) and places the application installer under C:ProgramDataVCC Live 360.
2. It registers an Active Setup entry in HKLMSOFTWAREMicrosoftActive SetupInstalled Components. Windows runs Active Setup once per user at logon — so every user who logs into the machine automatically gets VCC Live 360 installed into their own profile, silently, on first login. New users created later are covered too.
3. It adds a “Reinstall VCC Live 360” Start Menu shortcut, so a user can re-run the per-user setup themselves if their installation ever breaks — no IT ticket needed.

This design combines the best of both worlds: IT deploys one per-machine MSI, while each user ends up with a normal per-user installation that supports self-updating.

Version notes for deployment tools:

• Because MSI limits version fields to 255, the MSI’s registered version drops the 20 year prefix (e.g. app version 2026.x.y appears as 26.x.y in Windows Installer). Keep this in mind when writing detection rules.
• Each build has a new ProductCode under a stable UpgradeCode ({246129A8-9BBB-4B6D-A655-4985F566FCEC}), so deploying a newer MSI upgrades the existing installation — no manual uninstall step.

Command-line usage

Standard msiexec flags apply. Typical silent deployment:

msiexec /i vcc-live-1.2.3.msi /qn /norestart /L*V "C:logsvcc-live-install.log"

Silent uninstall (by product code, no MSI file needed):

msiexec /x {PRODUCT-CODE-GUID} /qn /norestart

Note: uninstalling the MSI removes the machine-wide provisioning; per-user installations already created in user profiles are removed via their own per-user uninstaller.

Summary