Skip to main content

Handling Renamed MSI Files in MDM/Intune Deployments

Describes the process for specifying a an original filename for MDM systems that rename MSI files for deployment.

Updated over 3 months ago

Many modern MDM systems (including Microsoft Intune) rename or stage MSI files under GUID-based filenames before calling Windows Installer. This does not affect the MSI’s internal ProductCode or version, but it does mean that the physical filename on disk may no longer reflect the original name.

Since the IT Agent RMM Sender relies on the MSI filename to carry tenant-specific information, the intended filename must be explicitly passed into the installer as a property.

Use the public property ORIGINALFILENAME on the msiexec command line. For example, from an elevated command prompt:

msiexec /i 290928309480923402.msi /qn ORIGINALFILENAME="sender_test-tenant.us1.itagent.io_FD5391AB.msi"

The installer records the ORIGINALFILENAME property into the registry value InstallerFileName under the application’s registry key.

If ORIGINALFILENAME is not specified, the installer will instead record the filename portion of the OriginalDatabase property, which under MDM will usually be a GUID-style or short cached name.

Did this answer your question?