When you run Setup, you can use command-line options to change some of the parameters that Setup uses to install Office, such as display settings and default values for Setup properties. Command-line options override duplicate customizations in the Setup settings file or in a transform.
For more information about command-line options that you can use with Windows Installer, see Roadmap to Windows Installer Documentation on the MSDN Web site.
/?
Refer the user to the Office Resource Kit for information about command-line options.
/a [msifile]
Create an administrative installation point for the specified package. The package must be in the same folder as Setup.exe, or the path must be included on the command line.
Examples:
/a ProPlus.msi
/a "subfolder1\ProPlus.msi"/autorun
Run Setup automatically when the Office CD is inserted in the CD-ROM drive; used only in the Autorun.inf file.
/f[options] msifile
Force repair of an application associated with the specified package. The package must be in the same folder as Setup.exe, or the path must be included on the command line.
Note You must specify the same package (MSI file) that was used to install the application originally.
Valid values for options include the following:
| a |
Force reinstallation of all files regardless of checksum or version. |
| c |
Reinstall file if missing or corrupt. |
| d |
Reinstall file if missing or a different version is present. |
| e |
Reinstall file if missing or an equal or older version is present. |
| m |
Rewrite all required HKEY_LOCAL_MACHINE registry entries. |
| o |
Reinstall file if missing or an older version is present. |
| p |
Reinstall file only if missing. |
| s |
Reinstall all shortcuts and overwrite existing shortcuts. |
| u |
Rewrite all required HKEY_CURRENT_USER registry entries. |
| v |
Recopy the package (MSI file) from the original source and recache it on the local computer. |
Note The Detect and Repair command (Help menu) in Office applications performs the same function as /focums. Running Setup and selecting Reinstall performs the same function as /fecums.
Example:
/fp ProPlus.msi/i [msifile]
Install applications using the specified package. The package must be in the same folder as Setup.exe, or the path must be included on the command line.
Note The default behavior of Setup.exe performs the same function as /i.
Example:
/i ProPlus.msi
/i "subfolder1\ProPlus.msi"/joption [msifile] [/t mstfile]
Advertise the application on the computer and install on first use; you must specify an option to advertise the application to either the computer or the user. You can use /j only when running Setup from an administrative installation point. If no package is specified, Setup uses the package specified in Setup.ini. To apply a transform to the advertised application, use the option /t and specify an MST file.
Valid values for option include the following:
| m |
Advertise to all users on the computer. |
| u |
Advertise to the current user (not recommended for Office XP). |
Example:
/jm ProPlus.msi /t o10trns.mst
Note In addition to /t, you can use the following three command-line options when you use /j to advertise Office: /l, /q, and /settings.
For more information about advertising Office XP to users or computers, see Distributing Office to Users' Computers.
/l[options] logfile
Create a log of installation actions. The /l command-line option overrides default settings specified in the [Logging] section of Setup.ini.
Values for option include the following and capture the corresponding data.
| a |
Start of action notification |
| c |
Initial UI parameters |
| e |
Error messages |
| i |
Information-only messages |
| m |
Out-of-memory messages |
| o |
Out-of-disk space messages |
| p |
Property table list in form property=value |
| r |
Action data record; contains action-specific information |
| u |
User request messages |
| v |
Verbose; includes debug messages |
| w |
Warning messages |
| * |
Turn on all logging options except v |
| + |
Append to existing log file |
Default logging options for Office XP are vpiwaeo.
The /l option creates a log file for Setup and a log file for each Windows Installer task. Logfile is the name and path of the log file to create. When you include (*) in the log file name, Setup creates a unique file name for each instance of Setup.
Example:
/lv* "%temp%\Office Setup(*).txt"This command line creates the following verbose log files:
- Setup.exe log file – %temp%\OfficeSetup(0001).text
- OSP log file – %temp%\OfficeSetup(0001)_Task(0001).txt
- Office log file – %temp%\OfficeSetup(0001)_Task(0002).txt
For more information about logging, see Customizing How Setup Runs.
/noreboot
Do not restart the computer or display a restart dialog box at the end of the installation. The /noreboot option passes the REBOOT=ReallySuppress property to each package included in the Office installation except the last one.
/nosp
Override the System Files Update detection process and do not install the System Files Update package (Osp.msi).
For more information about the System Files Update, see Setup Components.
/q[options]
Set the Setup user interface display level.
Valid values for option include the following:
| b |
Display only simple progress indicators and error messages (Basic). |
| f |
Display all dialog boxes and messages; equivalent to omitting the /q option (Full). |
| n |
Display no user interface; equivalent to specifying /q with no options (None). |
| r |
Display all progress indicators and error messages but collect no user information (Reduced). |
| - |
Suppress all modal dialog boxes; used with b, f, n, or r. |
| + |
Add completion message to the n or b option. |
Note The completion message is displayed only when Setup does not have to restart the computer after the installation.
For more information about display settings, see Customizing How Setup Runs.
/settings file
Specify a custom Setup settings file for Setup.exe to use in place of Setup.ini. The settings file must be in the same folder as Setup.exe, or the path must be included on the command line.
Example:
/settings MyApp.iniFor more information about creating a custom Setup INI file, see Customizing the Office Installation.
/spforce
Install the System Files Update (Osp.msi) even if the detection process determines that it is not required. The /spforce option does not work on Microsoft® Windows® 2000 or Microsoft Windows Millennium Edition.
For more information about the System Files Update, see Setup Components.
/sponly
Install only the System Files Update (Osp.msi). Use the /sponly option to install the System Files Update on computers running under Windows 98 or Windows NT 4.0 before beginning the Office XP deployment process.
For more information about the System Files Update, see Setup Components.
/wait
Direct Setup.exe to allow Windows Installer (Msiexec.exe) to complete before terminating the installation process. The /wait option is no longer required; the functionality is now built into Setup.exe.
/webinstall path
For security reasons, Microsoft no longer recommends installing Microsoft Office XP from an administrative installation point on a Web server (HTTP source). This recommendation is true for all Windows Installer packages (MSI files) that are installed from an HTTP source, not just Office.
You can still use a hyperlink on a Web page to point to an Office administrative installation point that is hosted on a file server (for example, a UNC path). For more information, see Microsoft Does Not Recommend Installing Office XP from a Web Server.
/x [msifile]
Remove the application associated with the specified package. The package must be in the same folder as Setup.exe, or the path must be included on the command line.
Note You must specify the same package (MSI file) that was used to install the application originally.
Example:
/x ProPlus.msiproperty=value
Specify a property value on the command line. If the value contains spaces, enclose it in quotation marks ("). To specify two or more property-value pairs, separate them with spaces.
Example:
TRANSFORMS="c:\Acct Dept.mst" DISABLEROLLBACK=1 USERNAME="Manager"