Availability: This article describes the MSI installer for portier Vision from version 5.5.0 onwards. Older versions use the NSIS installer with different parameters; see section at the end.
What's changed
From version 5.5.0 onwards, portier Vision is delivered as a signed MSI package. This allows Vision to be distributed using standard Windows tools: Group Policy (GPO), Microsoft Intune, SCCM/MECM, PDQ Deploy, or a PowerShell/batch script via msiexec. Per machine installation goes to C:\Program Files (x86)\portier\Vision; upgrades from older MSI versions are automatically detected and replaced.
Component selection
The MSI always installs all components. Individual component selection is no longer available. The component flags from the NSIS installer (/vision=, /firebird=, /reports=) are discontinued without replacement; if carried over from old scripts, they have no effect.
Silent installation
Standard command for unattended installation:
msiexec /i PortierVision-5.5.0.msi /qn /norestart/i — Installation
/qn — no UI, no dialogs
/norestart — suppresses automatic restart
Local administrator rights are required because the MSI is installed per-machine.
Custom installation directory
The target path can be set on a fresh machine via the INSTALLFOLDER property:
msiexec /i PortierVision-5.5.0.msi /qn /norestart INSTALLFOLDER="D:\portier\Vision"Important: If a Vision installation already exists on the machine (whether MSI or legacy NSIS installation), the installer reads the existing path from HKCU\Software\portier\Vision\InstallPath or HKLM\Software\portier\Vision\InstallPath and overwrites any INSTALLFOLDER value from the command line. This is intentional: upgrades stay in place. If you want to change the path, you must uninstall first.
Configure update behavior during rollout
Vision installs after every setup HKLM\Software\portier\Vision\UpdateMode = Auto. If you want to suppress the built-in auto-updater because your software distribution manages updates centrally, set the value via GPO or Intune policy to Managed or Notify. The group policy is reapplied after MSI installation and overwrites the value.
Details on the three modes: Automatic updates for portier Vision.
Logging
For detailed installation logging:
msiexec /i PortierVision-5.5.0.msi /qn /norestart /l*v "C:\Temp\vision-install.log"/l*v logs all messages including verbose output. If you encounter errors in software distribution, this file is your first point of contact.
Silent uninstall
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 and pass it:
$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: this class triggers a Windows Installer consistency check across all installed MSIs and often takes several minutes per machine.
The UpgradeCode {3F8A6B2D-4E17-4F9C-8A5B-2C6D1E3F4A7B} remains constant across versions. The ProductCode (which is needed for msiexec /x) changes with each version and is found in the uninstall registry under PSChildName.
Upgrades between MSI versions
Running a newer MSI version over an existing installation is a major upgrade: the MSI first removes the old version (including a detailed stop of a running PortierVision.exe via the Windows Restart Manager) and then installs the new version. No separate uninstallation is required. User settings in the registry and database connections are retained.
Note: automatic start after installation
After each reinstallation or major upgrade installation, the MSI automatically starts PortierVision.exe in the context of the logged-in user. In an unattended rollout via Intune or SCCM in the SYSTEM context without a logged-in user, this start runs silently in the background. If, on the other hand, the MSI is run interactively under an admin account or via script on a workstation with an active user session, Vision opens immediately after completion. This behavior cannot currently be suppressed via an MSI parameter; plan rollouts accordingly for times when machines are not actively in use.
Reinstall and repair
msiexec /fa PortierVision-5.5.0.msi /qn/f = repair, a = reinstall all files. Useful after a corrupted installation.
Legacy installer (before version 5.5.0)
Versions before 5.5.0 use an NSIS installer (SetupPortierVision_X.Y.Z.exe). The silent parameters are /S (silent), /D=<path> (without quotes) as well as component flags /vision=, /firebird=, /reports=. For new rollouts, you should switch to 5.5.0 or newer to have all standard MSI tools available.