Creating an uninstall log, Creating a patch install log – HP PCIe IO Accelerators for ProLiant Servers User Manual
Page 58
Windows Server environments 58
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
)," 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:
1.
Open the Installer project of your installation package.
2.
Go to the Media page and select the Bootstrapper tab.
3.
Select the Create EXE setup file option.
4.
Set the MSI Command Line field to /L*V "C:\package.log".
When the user launches the installation through the bootstrapper, a log of the installation
("package.log") will be created automatically in the "C:\" drive.
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.
Automated logging with the Windows Installer Logging Policy
To enable automated logging for debugging purposes, create a registry value.
1.
From a command line, run regedit.exe.
2.
Locate the following registry key:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
3.
Create a new STRING Entry named Logging.
4.
Change its value using the logging options discussed previously. Note that you cannot use the
wildcard () for this approach.
The .LOG file will be created in the Temp folder of the current user account with a name of this form:
MSI.LOG.