Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search.
Microsoft's documentation for msiexec says this:. I think it might help to have an example installer log. What is 'all logging information' vs verbose logging? Guessing this is going to be a unique Microsoft thing. Likewise, v indicates a particular set of items to be logged; it's not a generic verbose logging level.
Debug Logging Verbose : Advanced, slow logging for maximum details captured. This is - as far as I can tell - the most information you can capture in an MSI log:. Advanced installer and an old blog from the MSI team of many years ago have a few clues to their content:. This old dialog from a log-command generation tool might help. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
The executable program that interprets packages and installs products is Msiexec. Note that Msiexec also sets an error level on return that corresponds to system error codes.
Command-line options are case-insensitive. The command-line options in the following table are available with Windows Installer 3.
Only public properties can be modified using the command line. All property names on the command line are interpreted as uppercase but the value retains case sensitivity. For more information, see About Properties. You can put the property anywhere except between an option and its argument.
Property values that are literal strings must be enclosed in quotation marks. The user interface level of the installation can be configured according to the target environment. For example, a package distributed to clients should have a full UI, while a package deployed through Group Policy should have no user interface.
Sometimes an installation overwrites files which are in use or needs to reboot the machine in order to finish it.
The reboot policy used by the installation can be set through these options:. When debugging an installation package you can use multiple logging parameters in order to create a log. This will make the package go into maintenance mode and you can choose to uninstall it. Since the package was launched with logging, an uninstall log will be generated. If you want your installation package to always create a log, you can follow these steps:.
This way, when the user launches the installation through the bootstrapper, an installation log "package. The command line received by the bootstrapper overrides the command line in the "MSI Command Line" field. Therefore, if you launch an EXE package with logging parameters, these parameters will be used for creating the log. In order to enable this option, you need to import the registry settings below.
Please create a new text file with a ".
0コメント