HP IO manual Creating an installation log, Creating an uninstall log, Creating a patch install log

Page 34

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

Image 34
Contents HP IO Accelerator Version 3.2.3 Windows User Guide Page Contents Maintenance Resources Contents summary About this guideOverview IntroductionProduct naming Performance attributes IO Accelerator capacity 320GB 640GB Models AJ878B BK836ASupported firmware revisions Required operating environmentSupported hardware Page Introduction Uninstalling a previously-installed driver Installation overviewWindows Server environments Installing software on a Windows operating system Using the Setup Wizard Windows Server environments Windows Server environments Windows Server environments Windows Server environments Upgrading device firmware from VSL 1.x.x or 2.x.x to Upgrading procedure Fio-bugreportManual installation on Windows Server Fio-update-iodrive iodriveversion.fffManually installing on Windows Server Performing the upgrade Upgrading the device firmware using WindowsManually installing on Windows Server 2008 Viewing the firmware versionUpgrading driver software using Windows Fio-detach /dev/fct0Windows Server environments Defragmentation Silent install optionOutdated firmware check Enabling PCIe power IO Accelerator namingWindows Server environments Fio-config -p Fiopreallocatememory 1072,4997,6710,10345 Creating a RAID configurationSetting up Snmp for Windows operating systems Snmp details for Windows operating systemsUsing test mode registry values Via garbage collectionSnmp MIB fields supporting Windows Server Snmp test registry entry DescriptionWindows Server environments Windows Installer logging options Using installation logsMsiexec /i C\MyPackage\Example.msi /L*V C\log\example.log Creating an uninstall log Creating an installation logCreating a patch install log Automated logging with the Windows Installer Logging Policy Troubleshooting event log messagesError ioDrivex Common maintenance tasks MaintenanceMaintenance tools Uninstalling the IO Accelerator driver packageUnmanaged shutdown issues Enabling PCIe power overrideEnabling Autoattach Enabling the override parameter Fio-config /dev/fctx -p PCIeGLOBALSLOTPOWERLIMIT Fio-config /dev/fct2 -p PCIeGLOBALSLOTPOWERLIMITUtilities reference UtilitiesFio-attach Fio-attach device options Fio-beaconFio-bugreport Fio-beacon device optionsFio-config device options Fio-configCompressing Fio-config options FioexternalpoweroverrideFio-detach Fio-detach device optionsFio-format Fio-format device options deviceFio-pci-check options Options Fio-pci-checkFio-status Fio-status device optionsFfield Geometry and capacity information not available. appears Fio-sure-erase Fio-sure-erase options deviceFio-trim-config Fio-trim-config options Options Fio-update-iodriveFio-update-iodrive iodriveversion.fff options Format domainbusslot.func Health metrics Monitoring IO Accelerator healthNand flash and component failure Health monitoring techniquesFlashback substitution events Software RAID and health monitoringMonitoring IO Accelerator health Introduction to Trim Using TrimTrim support Trim platformsEnabling Trim Starting and stopping TrimControlling Trim aggressiveness Trim configurations Introduction to Windows page files Using Windows page files with the IO AcceleratorConfiguring IO Accelerator paging support RAM consumptionFio-config -g Fiopreallocatememory Fio-config -p Fiopreallocatememory 1234,17834Fio-config -p Fiopreallocatememory Non-paged memory poolSetting up page files Windows page file managementSystem drive paging file configuration Guaranteeing minimum committable memoryVerifying page file operation Virtual Memory performanceDir c /ah Disabling Dvfs Performance and tuningIntroduction to performance and tuning Limiting Apci C-statesSetting Numa affinity Setting the interrupt handler affinityIntroduction to Numa architecture Numa configurationFio-config -p Fioaffinity 4,n1,0xf5,n07,g19,g2,0xff0 Fioaffinity parameterAdvanced configuration example Checking the log for errors Fio-config -p Fioaffinity 5,g0,0xf6,0xfResources Subscription serviceFor more information HP contact information Support and other resourcesBefore you contact HP Customer Self RepairRéparation par le client CSR Riparazione da parte del cliente Reparaciones del propio cliente Reparo feito pelo cliente Support and other resources Support and other resources Support and other resources Warranty information Safety and regulatory complianceRegulatory information Acronyms and abbreviations NumaSMI-S Documentation feedback Index Using the IO Accelerator as a swap