MSI Software Installation (System Wide-All Users)

What MSI Software Installation does

This Automox Worklet™ installs MSI-based applications system-wide (for all users) on Windows endpoints. The Worklet is designed as a reusable template that requires minimal configuration: just specify the MSI filename, application name for detection, target version, and optional custom arguments.

The Worklet uses an advanced MSI property extraction function that reads mandatory properties directly from the MSI file using the Windows Installer COM object. This includes ProductCode (GUID), ProductVersion, ProductName, Manufacturer, and ProductLanguage. These properties enable accurate post-installation verification.

During remediation, the Worklet executes msiexec with standard silent installation arguments (/qn /norestart) plus any custom arguments you specify. Installation logging goes to the Windows temp directory for troubleshooting. Post-installation verification uses the ProductCode GUID for precise registry matching.

Why use MSI Software Installation through Automox

Many enterprise applications ship as MSI packages that require system-wide installation for proper functionality. This Worklet provides a standardized approach to deploying any MSI-based software without writing custom installation scripts for each application.

The Worklet handles common MSI deployment challenges automatically: silent installation flags, logging, custom properties, and post-installation verification. You upload the MSI as a Worklet payload and configure a few variables rather than building installation logic from scratch.

Version-aware evaluation prevents unnecessary reinstallation. The Worklet compares the target version against any existing installation, so it only runs remediation when the installed version is older than the MSI being deployed.

How MSI Software Installation works

1. Evaluation phase: The Worklet searches Windows registry uninstall keys for the specified $appName. It compares the installed DisplayVersion against the target $dispVer. If the installed version is greater than or equal to the target, the endpoint is compliant. Otherwise, it proceeds to remediation.

2. Remediation phase: The Worklet validates the payload file exists, extracts MSI properties using the Windows Installer COM object, constructs the msiexec command with /qn, /norestart, custom arguments, and logging, executes the installation, then verifies success by checking the registry for the ProductCode GUID and matching version.

MSI Software Installation requirements

• Windows 7 or later

• MSI installer file uploaded to Worklet payload

• Configure $fileName with the exact MSI filename including extension

• Configure $appName with the application name as it appears in Programs and Features

• Configure $dispVer with the target version for compliance detection

• Optional: Configure $custArgs for additional MSI properties (e.g., ALLUSERS=1)

• Administrative privileges for software installation

Expected state after MSI Software Installation

After successful remediation, the application appears in the Windows Programs list with the ProductCode GUID from the MSI. The Worklet outputs "Installation of [filename] Successful" if the registry verification passes. The application is available to all users on the endpoint.

Installation logs are saved to %WINDIR%\temp\[filename].log for troubleshooting. If installation fails, the Worklet exits with code 1603 and directs you to the log file. Subsequent Worklet runs compare the installed version and only remediate if an older version is detected.

How to validate msi software installation (system wide-all users) changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for msi software installation (system wide-all users).

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Get-ChildItem, Get-ItemProperty, Where-Object.

4. Validate remediation effects from script operations such as Split-Path, Test-Path, Get-MSIPropertyList, then rerun evaluation for compliance.