[Guide] How to Deploy MSI Format App with Parameters?

Modified on Thu, 29 Aug at 4:54 PM

Using parameters to install MSI files allows for automated, silent installations, reducing the need for manual intervention and minimizing user disruption. Additionally, it enables customization of the installation process, ensuring consistent configurations across multiple devices.

Reminder:

Please evaluate and test whether there are any system or application conflicts between the parameters and your applications before you release them to all your devices.
When you include one or more parameters, separate them using space.

Install options

Set the install type for launching an installation package.

/i	Specifies normal installation.
/a	Specifies administrative installation.
/ju	Advertise the product to the current user.
/jm	Advertise the product to all users.
/j/g	Specifies the language identifier used by the advertised package.
/j/t	Applies transform to the advertised package.
/x	Uninstalls the package.

Display options

You can configure what a user sees during the installation process, based on your target environment.

/quiet	Specifies quiet mode, which means there's no user interaction required.
/passiveSpecifies	Specifies unattended mode, which means the installation only shows a progress bar.
/qn	Specifies there's no UI during the installation process.
/qn+	Specifies there's no UI during the installation process, except for a final dialog box at the end.
/qb	Specifies there's a basic UI during the installation process.
/qb+	Specifies there's a basic UI during the installation process, including a final dialog box at the end.
/qr	Specifies a reduced UI experience during the installation process.
/qf	Specifies a full UI experience during the installation process.

Restart options

If your installation package overwrites files or attempts to change files that are in use, a reboot might be required before the installation completes.

/norestart	Stops the device from restarting after the installation completes.
/promptrestart	Prompts the user if a reboot is required.
/forcerestart	Restarts the device after the installation completes.

Logging options

If you need to debug your installation package, you can set the parameters to create a log file with specific information.

/li	Turns on logging and includes status messages in the output log file.
/lw	Turns on logging and includes non-fatal warnings in the output log file.
/le	Turns on logging and includes all error messages in the output log file.
/la	Turns on logging and includes information about when an action started in the output log file.
/lr	Turns on logging and includes action-specific records in the output log file.
/lu	Turns on logging and includes user request information in the output log file.
/lc	Turns on logging and includes the initial UI parameters in the output log file.
/lm	Turns on logging and includes out-of-memory or fatal exit information in the output log file.
/lo	Turns on logging and includes out-of-disk-space messages in the output log file.
/lp	Turns on logging and includes terminal properties in the output log file.
/lv	Turns on logging and includes verbose output in the output log file.
/lx	Turns on logging and includes extra debugging information in the output log file.
/l+	Turns on logging and appends the information to an existing log file.
/l!	Turns on logging and flushes each line to the log file.
/l*	Turns on logging and logs all information, except verbose information (/lv) or extra debugging information (/lx).

Update options

You can apply or remove updates using an installation package.

/p	Installs a patch. If you're installing silently, you must also set the REINSTALLMODE property to ecmus and REINSTALL to ALL. Otherwise, the patch only updates the MSI cached on the target device.
/update	Install patches option. If you're applying multiple updates, you must separate them using a semi-colon (;).
/package	Installs or configures a product.

Repair options

You can use this command to repair an installed package.

/fp	Repairs the package if a file is missing.
/fo	Repairs the package if a file is missing, or if an older version is installed.
/fe	Repairs the package if file is missing, or if an equal or older version is installed.
/fd	Repairs the package if file is missing, or if a different version is installed.
/fc	Repairs the package if file is missing, or if checksum does not match the calculated value.
/fa	Forces all files to be reinstalled.
/fu	Repairs all the required user-specific registry entries.
/fm	Repairs all existing shortcuts.
/fs	Turns on logging and includes out-of-disk-space messages in the output log file.
/fv	Runs from source and re-caches the local package.