Msiexec switches log file

Prompt before restarting option. Displays a message that a restart is required to complete the installation and asks the user whether to restart the system now. Log option. Writes logging information into a log file at the specified existing path. The path to the log file location must already exist. The installer does not create the directory structure for the logfile. For more information about all the methods that are available for setting the logging mode, see Normal Logging Windows Installer.

Skip to main content. Please create a new text file with a ". After this, double click the ". Therefore, this option should only be used for debugging purposes. In order to disable the debugging policy, you can delete the registry values you have previously added using "RegEdit. For information on how to make a custom event appear in the log, please see How to write a specific event in the log. Instal and configure COMs.

Table of Contents. How do I create an installation log? Windows Installer 4. Logging a silent install. This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies. Logging an MSI Installation. Modifier Description i Status messages - Indicates when actions are started and stopped.

Its value defaults to Yes. For this one, change its value to No. Just about any property you see in this table can be adjusted at the command line as you execute msiexec to kick off an installation. While this method is the comprehensive approach, it is also the time-consuming approach. Another alternative is to simply search the Internet for clues that others have found.

A popular website that contains installation hints for many common software packages is www. A growing number of software companies also recognize the need to provide silencing information about their installation packages. A second alternative is to find a software repackaging solution that handles much of this work for you. These solutions incorporate a range of tactics to gather the necessary silencing and customization information with the goal of presenting it in meaningful ways.

MSI packaging solutions can be found by many third-party companies with a range of price points and feature sets. One final element of MSI installations merits discussion.

This element consolidates a series of property changes and other MSI reconfigurations into a single file. An MST, or transforms file, is commonly used when an MSI's configuration database requires large scale changes to prepare itself for installation.

Rather than requiring you to enter a long list of alterations at the command line, a transforms file consolidates changes into a single file that is invoked at the command line. Creating your own transforms typically requires the use of a software. At the end of the day, getting a software installation packaged for silent installation is only the first step.

It can also be arguably the most difficult step. One packaged, you'll need a software deployment solution to execute the command you've created on entire groups of computers at once. Or, since this is a command line, you can keep walking the halls. Except this time you're not clicking Next, Next, Finish; you're typing long command strings into each computer's Run prompt. Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Log in. That syntax looks generally like this: msiexec. So, for example, if you wanted to install the Adobe Flash Player to your desktop and had the correct MSI available, you might do so with the following syntax: msiexec. Sleuthing for Custom Properties As I mentioned earlier, each MSI has its own custom name and value pairs that answer questions the installation requires. Transformers One final element of MSI installations merits discussion. The generic use of a transforms file follows this structure: msiexec.