When using the setup.exe, the following changes may be implemented to customize its behavior. The setup executable reads this settings file and writes tasks to the registry based on the information provided. This allows for control of many aspects of the Office 2003 Editions installation process. You can find a sample copy of this file on the Office 2003 Editions CD in the \Files\Setup folder.
Open setup.ini in a simple text editor such as Notepad and modify any of the following sections as desired:
1. MSI section - allows you to identify the MSI to be used.
2. Product section - contains the product code, name, and version information for and is used to determine whether the product is installed.
ProductName=Microsoft Office 2003
3. MST section - used to specify the full name and path of any optional transform files.
4. Options section - allows you to set several Windows Installer properties.
USERNAME=Your Customer Name
COMPANYNAME=Target Company Name
INSTALLLOCATION=C:\Program Files\Microsoft Office 2003
5. Display section - allows you to instruct setup to run in quite mode.
6. Logging section - this section provides settings for controlling the Setup log files.
Template=Microsoft Office 2003 Setup(*).txt
7. MinOSRequirement section - this section is used for defining the minimal OS requirement for the setup to run.
8. Cache section - provides settings to control the way Office installation files (CAB files) are cached on the local computer during Setup caching the install source locally.
9. OfficeWebComponents section - species the MSI file for Office Web Components.
10. ChainedInstall_n section - used to install an additional package (MSI file) or other executable file (such as an EXE file or a BAT file) as part of the Office installation. Add a [ChainedInstall_n] section to Setup.ini for each chained installation; replace the placeholder n with a consecutive number. Chained packages are installed in order after the core Office package is successfully installed.
Cmdline= /s /v/qb
Note For details on these sections and the available options and values, see http://office.microsoft.com/en-us/assistance/HA011513671033.aspx and naturally, you can obtain lots of command line installation information for your chained installs in the AppDeploy Package Knowledge Base.