MSI Software Installation - 64-Bit OS

What the deprecated 64-bit MSI installer Worklet does

This Automox Worklet™ is a deprecated stub from an earlier generation of the Automox catalog. The evaluation and remediation scripts contain only a header comment that flags the Worklet as deprecated and directs administrators to the current MSI deployment Worklet.

Because the scripts contain no PowerShell logic, this Worklet does not check for installed software, does not invoke msiexec, does not stage an installer, and does not change state on the endpoint. Any policy still scoped to this Worklet will run to completion without modifying the target endpoint.

The page is kept so existing links continue to resolve and so administrators looking for the legacy Worklet by name can find the current replacement quickly. New MSI deployment policies should reference the MSI Software Installation (System Wide-All Users) Worklet instead.

Why this 64-bit MSI Worklet is deprecated

Automox consolidated MSI deployment behind a single, system-wide Worklet that handles 64-bit and 32-bit packages from one code path. Maintaining a separate 64-bit-only Worklet created drift between siblings: the install context, the silent flag handling, and the validation logic could diverge over time, which is unsafe for software lifecycle automation.

The active replacement, MSI Software Installation (System Wide-All Users), targets every Windows endpoint Automox supports today. It accepts a configurable MSI source, applies a silent install for all users, and reports the msiexec exit code back to the Automox console, so it covers the same use cases this 64-bit-only Worklet was originally written for.

How the deprecated Worklet behaves

1. Evaluation phase: The evaluation script contains only a deprecation comment block. PowerShell parses the file, finds no executable statements, and exits successfully without checking installed products, registry entries, or product GUIDs. Automox treats the endpoint as compliant and remediation is not scheduled.

2. Remediation phase: If remediation runs anyway, the script contains only a deprecation comment. msiexec is not invoked, no installer is staged, and no files are written. The script returns exit code 0 and the policy reports success while making no change to the endpoint.

Migration requirements for existing 64-bit MSI policies

• Identify every Automox policy currently scoped to this deprecated Worklet under Policies, then disable or delete those policies before assigning the replacement

• Add the MSI Software Installation (System Wide-All Users) Worklet from the Worklet catalog and create a fresh policy targeting the same endpoint groups

• Configure the MSI source location and product detection values in the replacement Worklet (local path, UNC share, or HTTPS URL reachable from the Automox agent context)

• Confirm endpoints run a supported version of Windows (Windows 10, Windows 11, Windows Server 2016, Windows Server 2019, or Windows Server 2022)

• Run the replacement policy against a pilot group first, verify the msiexec exit code in the activity log, then expand scope to the rest of the fleet

Expected outcome after migrating off this Worklet

After moving to the MSI Software Installation (System Wide-All Users) Worklet, MSI deployments produce real state changes on the endpoint, surface msiexec exit codes in the Automox activity log, and validate the install through registry inspection. Policies still pointed at this deprecated Worklet will continue to report success with no underlying work, which is misleading evidence for audit and software-compliance reporting.

Validate the migration by triggering the new policy against a single pilot endpoint, then confirming the application appears under Settings, Apps, Installed apps, and inside the registry uninstall hive at HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. Once the pilot run is clean, retire any remaining references to the 64-bit MSI Worklet so the catalog reflects only the supported install path.