Option

Description

 

 

*x

Extra debugging information

*+

Append to existing log file

*!

Flush each line to the log

**

Log all information except for v and x options

Creating an installation log

1.Determine the path of the MSI file (for example, C:\MyPackage\Example.exe).

2.Decide the path of the log (for example, C:\log\example.log).

3.Open cmd.exe. You can use any command shell.

4.Use the msiexec command line to launch the MSI with logging parameters.

Any installation logging command line must have this form:

msiexec /i <path_to_msi> /L*V <path_to_log>

The following is a sample command for creating the installation log. The /i parameter launches the MSI package. Be sure to specify the actual paths to your MSI file and log file.

msiexec /i "C:\MyPackage\Example.msi" /L*V "C:\log\example.log"

If you want the log to be created next to the MSI, you can specify only the name of the log file: msiexec /i "C:\MyPackage\Example.msi" /L*V "example.log"

After the installation is finished, the log is complete.

Using an .exe bootstrapper

When the installation package is included in an .exe bootstrapper, do not use msiexec. in the command line. For example:

"C:\MyPackage\Setup.msi" /L*V "example.log"

Creating an uninstall log

Launch the installer with the logging command, for example:

"C:\MyPackage\Setup.exe" /L*V "example.log"

This command puts the package into maintenance mode, and you can choose to uninstall it. Because the package was launched with logging, an uninstall log is generated.

Creating a patch install log

To create a log for a patch installation, follow the procedure in "Creating an installation log (on page 34)," but replace the /i parameter with /p, for example:

msiexec /p "C:\MyPackage\Patch.msp" /L*V "C:\log\patch.log"

Using the .exe boostrapper

Another approach is to create a log file by using the /L*V parameters in the command line of the Installer Bootstrapper. Also, these parameters can be always passed to the MSI when the package is launched through the .exe bootstrapper.

If you want your installation package to create a log, follow these steps:

Windows Server environments 34