Availability: This article describes the MSI installer shipped with portier Vision 5.5.0 and later. Older versions use an NSIS installer with different parameters; see the section at the end.
From version 5.5.0 onwards, portier Vision is delivered as a signed MSI package. This means Vision can be deployed with standard Windows tools: Group Policy (GPO), Microsoft Intune, SCCM/MECM, PDQ Deploy, or a PowerShell/batch script around msiexec. The package installs per-machine under C:\Program Files (x86)\portier\Vision; upgrades from older MSI versions are detected and replaced automatically.
Standard command for an unattended install:
msiexec /i PortierVision-5.5.0.msi /qn /norestart/i — install
/qn — no UI, no dialogs
/norestart — suppress automatic reboot
Local administrator rights are required because the MSI installs per-machine.
On a fresh machine the target path can be set via the INSTALLFOLDER property:
msiexec /i PortierVision-5.5.0.msi /qn /norestart INSTALLFOLDER="D:\portier\Vision"Important: if any Vision install already exists on the machine (MSI or legacy NSIS), the installer reads the existing path from HKCU\Software\portier\Vision\InstallPath or HKLM\Software\portier\Vision\InstallPath and overwrites any command-line INSTALLFOLDER value. This is by design: upgrades stay in place. To change the install path, uninstall first.
Every install writes HKLM\Software\portier\Vision\UpdateMode = Auto. To suppress the built-in auto-updater because your software-distribution tool manages updates centrally, deploy the value Managed or Notify via GPO or Intune policy. Group Policy is reapplied after MSI installation and overwrites the value.
Details on the three modes: Automatic updates for portier Vision.
For a detailed install log:
msiexec /i PortierVision-5.5.0.msi /qn /norestart /l*v "C:\Temp\vision-install.log"/l*v captures all messages including verbose output. The log file is the first place to look when a deployment fails.
If the original MSI file is available:
msiexec /x PortierVision-5.5.0.msi /qn /norestartWithout the MSI file, read the Product Code from the Uninstall registry hive and pass it to msiexec:
$entry = Get-ItemProperty HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* |
Where-Object DisplayName -eq 'PortierVision' | Select-Object -First 1
if ($entry) {
Start-Process msiexec.exe -ArgumentList "/x $($entry.PSChildName) /qn /norestart" -Wait
}Do not use Get-WmiObject Win32_Product or Get-CimInstance Win32_Product: that class triggers a Windows Installer consistency check across every MSI on the machine and routinely takes minutes per host.
The UpgradeCode {3F8A6B2D-4E17-4F9C-8A5B-2C6D1E3F4A7B} stays constant across versions. The ProductCode (which msiexec /x needs) changes with every version and lives in the Uninstall registry under PSChildName.
Running a newer MSI over an existing install is a major upgrade: the MSI removes the old version (including gracefully stopping a running PortierVision.exe via Windows Restart Manager) and installs the new one. No separate uninstall step is needed. Registry-based user settings and database connections survive.
On every fresh install and major upgrade the MSI launches PortierVision.exe automatically in the logged-in user's context. For an unattended rollout through Intune or SCCM in SYSTEM context without an interactive user, the launch silently no-ops. When the MSI runs interactively under an admin account, or via a script on a workstation with an active user session, Vision opens immediately after install completes. There is currently no MSI parameter to suppress this; plan rollouts for times when the machines are not actively in use.
msiexec /fa PortierVision-5.5.0.msi /qn/f = repair, a = reinstall all files. Useful after a corrupted install.
Versions before 5.5.0 use an NSIS installer (SetupPortierVision_X.Y.Z.exe). Silent parameters are /S (silent), /D=<path> (no quotes), and component flags /vision=, /firebird=, /reports=. For new rollouts, move to 5.5.0 or later so the standard MSI tooling is available.