Lenovo ThinkCentre E50 (English) Rescue and Recovery 4.5 Deployment Guide - Page 11

Installation log files, Using msiexec.exe

Page 11 highlights

• For installation target directory paths that do NOT contain spaces, use the following command line as an example: setup.exe /a /s /v"/qn TARGETDIR=F:\TVTRR" • For installation target directory paths that contain spaces, an escape character '/' must be placed preceding the double-quoted target directory: setup.exe /a /s /v"/qn TARGETDIR=\"F:\TVTRR\Rescue and Recovery\"" Note: If your version of Windows Installer is not current, setup.exe is configured to update the Windows Installer engine to version 3.0. This update will cause the installation action to prompt for a reboot even with an administrative extract installation. Use the reboot properly to prevent a reboot in this situation. If the Windows Installer is at least version 3.0, setup.exe will not attempt to install. Once an administrative installation has been completed, the administrative user can make customizations to the source files, such as adding settings to the registry. Using msiexec.exe To install from the unpacked source after making customizations, the user calls msiexec.exe from the command line, passing the name of the unpacked *.MSI file. The msiexec.exe file is the executable program of the Windows Installer used to interpret installation packages and install products on target systems. • For installation paths that do NOT contain spaces: msiexec.exe /a "Lenovo Rescue and Recovery.msi" /qn TARGERDIR=F:\TVTRR • For installation paths that contain spaces: msiexec.exe /a "Lenovo Rescue and Recovery.msi" /qn TARGERDIR=\"F:\TVTRR\Rescue and Recovery\" The following is an example to use msiexec.exe. msiexec /i "C:\WindowsFolder\Profiles\UserName\ Personal\MySetups\project name\product configuration\release name\ DiskImages\Disk1\product name.msi" Note: Enter the preceding command as a single line with no spaces following the slashes. For information on command line parameters and public properties, go to the Microsoft Web site at: http://www.microsoft.com Installation log files The log file rrinstall45w.log is created in the %temp% directory if the setup is launched by the setup.exe file (double-click the install.exe file to run it without parameters, or extract msi and run the setup.exe file). The log file contains log messages that can be used to debug installation problems. The log file includes any actions performed by the Add/Remove Programs applet from Control Panel. The log file is not created when your are running the setup.exe file directly from the MSI package. To create a log file for all MSI actions, you can enable the logging policy in the registry. To do this, create the following value: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer] "Logging"="voicewarmup" The following table shows examples of installations using the setup.exe file. Table 1. Examples of running Setup.exe Description Perform silent installation with no reboot. Perform administrative installation. Example setup.exe /s /v"/qn REBOOT="R"" setup.exe /a Chapter 2. Installation 5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86

For installation target directory paths that do NOT contain spaces, use the following command line
as an example:
VHWXS²H[H ±D ±V ±Y³±TQ 7$5*(7',5°)´?79755³
For installation target directory paths that contain spaces, an escape character '/' must be placed
preceding the double-quoted target directory:
VHWXS²H[H ±D ±V ±Y³±TQ 7$5*(7',5°?³)´?79755?5HVFXH DQG 5HFRYHU\?³³
Note:
If your version of Windows Installer is not current, setup.exe is configured to update the Windows
Installer engine to version 3.0. This update will cause the installation action to prompt for a reboot even with
an administrative extract installation. Use the reboot properly to prevent a reboot in this situation. If the
Windows Installer is at least version 3.0, setup.exe will not attempt to install.
Once an administrative installation has been completed, the administrative user can make customizations to
the source files, such as adding settings to the registry.
Using msiexec.exe
To install from the unpacked source after making customizations, the user calls msiexec.exe from the
command line, passing the name of the unpacked *.MSI file. The msiexec.exe file is the executable program
of the Windows Installer used to interpret installation packages and install products on target systems.
For installation paths that do NOT contain spaces:
PVLH[HF²H[H ±D ³/HQRYR 5HVFXH DQG 5HFRYHU\²PVL³ ±TQ 7$5*(5',5°)´?79755
For installation paths that contain spaces:
PVLH[HF²H[H ±D ³/HQRYR 5HVFXH DQG 5HFRYHU\²PVL³ ±TQ 7$5*(5',5°?³)´?79755?5HVFXH DQG 5HFRYHU\?³
The following is an example to use msiexec.exe.
PVLH[HF ±L ³&´?
WindowsFolder
?3URúOHV?
UserName
?
3HUVRQDO?0\6HWXSV?
project name
?
product configuration
?
release name
?
'LVN,PDJHV?'LVNµ?
product name
²PVL³
Note:
Enter the preceding command as a single line with no spaces following the slashes.
For information on command line parameters and public properties, go to the Microsoft Web site at:
Installation log files
The log file rrinstall45w.log is created in the %temp% directory if the setup is launched by the setup.exe file
(double-click the install.exe file to run it without parameters, or extract msi and run the setup.exe file). The log
file contains log messages that can be used to debug installation problems. The log file includes any actions
performed by the
Add/Remove Programs
applet from Control Panel. The log file is not created when your
are running the setup.exe file directly from the MSI package. To create a log file for all MSI actions, you can
enable the logging policy in the registry. To do this, create the following value:
>+.(<B/2&$/B0$&+,1(?62)7:$5(?3ROLFLHV?0LFURVRIW?:LQGRZV?,QVWDOOHU@
³/RJJLQJ³°³YRLFHZDUPXS³
The following table shows examples of installations using the setup.exe file.
Table 1. Examples of running Setup.exe
Description
Example
Perform silent installation with no reboot.
VHWXS²H[H ±V ±Yィ±TQ 5(%227°ィ5ィィ
Perform administrative installation.
VHWXS²H[H ±D
Chapter 2
.
Installation
5