|
When you run Setup for Microsoft® Office 2003, 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.
Note In most cases, command-line options override duplicate customizations in the Setup settings file (Setup.ini) or in a transform (MST file).
For more information about command-line options that you can use with Microsoft Windows Installer (Msiexec.exe), see the Roadmap to Windows Installer Documentation on the MSDN Web site. /a [msifile]
Create an administrative installation point for the specified package (MSI file). The package must be in the same folder as Setup.exe, and both must be at the root of the administrative installation point.
Examples:
/autorun
Run Setup automatically when the Office CD is inserted into the CD-ROM drive; used only in the Autorun.inf file. /f[options] [msifile]
Force repair of an application associated with the specified package (MSI file). The package must be in the same folder as Setup.exe, and both must be at the root of the administrative installation point. Alternatively, you can specify the product code for the package; the product code can be copied from the [Product] section of the Setup settings file.
Note You must specify the same package 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 |
Retrieve the package from the original source and recache it on the local computer. |
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.
Important If a user applies a client patch to a computer, you cannot use the /f switch to recache and reinstall Office on that computer from an updated administrative installation point. In this case, users must uninstall Office and reinstall from the updated administrative image.
Examples:
/fpiwae Pro11.msi
/fvm {12345678-1234-1234-1234-123456789123}
/i [msifile]
Install applications using the specified package. The package must be in the same folder as Setup.exe, and both must be at the root of the administrative installation point.
Note By default, Setup.exe directs Windows Installer to perform the same function as /i.
Example:
/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 should 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 2003). |
Note In addition to using /t to specify a transform, you can use the following command-line options when you use /j to advertise Office: /l, /q, and /settings.
For more information about advertising Office 2003 to users or computers, see Running Setup from an Installation Image.
Example:
/jm Pro11.msi /t Custom.mst
/l[options] logfile
Create a log of installation actions for Setup and a log file for each Windows Installer task. The /l 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 |
Logfile specifies 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 log files:
- Setup.exe log file
"%temp%\OfficeSetup(0001).txt"
- Windows Installer log file for core Office 2003 package
"%temp%\OfficeSetup(0001)_Task(0001).txt"
The following example shows default logging options for Office 2003:
For more information about logging, see Customizing How Setup Runs. /p [mspfile]
Apply an administrative update (MSP file) to a client installation of Office. You can also use /p to apply an update to an administrative installation by including the /a option and the name and path of the MSI file on the administrative installation point. To apply the patch quietly, include /qb on the command line; to generate a log file, include /l.
Examples:
msiexec /p [mspfile] /qb /l[options]
msiexec /p [mspfile] /a [msifile] /qb /l[options]
For more information about patching Office installations, see Distributing Office 2003 Product Updates. /q[options]
Set the Setup user interface display level.
Valid values for options 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; use only with b. |
| + |
Add completion message to the n or b option. |
| ! |
Hide the Cancel button; use only with /qb. |
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:
For more information about creating a custom Setup INI file, see Methods of Customizing Office. /skiplangcheck
For information about this command-line option, see the [Product] entry in the reference topic Setup Settings File. /webinstall path
No longer supported by Setup. For security reasons, Microsoft no longer supports installing Office from an administrative installation point on a Web server (HTTP source). Installing from an HTTP source is not recommended for Office or any other Windows Installer package (MSI file).
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). /x [msifile]
Remove the application associated with the specified package. The package must be in the same folder as Setup.exe, and both must be at the root of the administrative installation point.
Note You must specify the same package that was used to install the application originally.
Example:
property=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.
For more information about properties you can set for Office, see Setup Properties.
Example:
TRANSFORMS="C:\Acct Dept.mst" DISABLEROLLBACK=1 USERNAME="Manager"
|
IN THIS CHAPTER
Printer-friendly version
