Runs the Office Customization Tool to create a Setup customization (MSP) file.

Example

Applies the specified Setup customization file to the installation. You can specify a path to a specific customization file (MSP file) or to the folder where you store customization files.

Note:
The /adminfile command-line option can be used only during initial installation of the product.

The recommended location for customization files is the Updates folder at the root of the network installation point. When you store a customization file in this folder, you do not need to specify the file on the command line. Setup automatically finds the customization file that matches the product that is being installed and applies the file during the installation.

If you store more than one customization file per product in the Updates folder, Setup applies all of the files to the installation. If you want to create unique configurations for different groups of users, you must store the customization files in a separate folder and specify the customization file you want on the command line.

Example

Specifies the Config.xml file that Setup uses during the installation. By default, the Config.xml file that is stored in the core product folder directs Setup to install that product. For example, the Config.xml file in the Pro.WW folder installs Microsoft Office Professional 2007.

You can edit Config.xml to make additional customizations to the installation, including specifying one or more language versions to install. Use /config on the Setup command line to point to the location of the default Config.xml file for a product or to point to a custom Config.xml file.

Example

\\server\share\Office12\setup.exe /config \\server\share\Office12\Pro.WW\Config.xml

where Office12 is the root of the network installation point.

Note:
You must use a fully qualified path. Setup does not recognize relative paths with /config.

Used with a modified Config.xml file to run Setup in maintenance mode and make changes to an existing Office installation. For example, you can use the /modify option to add or remove features. Look up the value of [ProductID]in the Setup.xml file for the product you want to modify.

The Setup.xml file is located in the core product folder on the network installation point. In Setup.xml, [ProductID] is equal to the value of the Id attribute of the Setup element. For example:

	Copy Code
- <Setup Id="Pro" Type="Product" ProductCode="{30120000-0011-0000-0000-1000000FF1CE}">

Example

Runs Setup to repair the specified product from the user's computer. Look up the value of [ProductID] in the Setup.xml file for the product you want to modify.

Example

Runs Setup to remove the specified product from the user's computer. Look up the value of [ProductID] in the Setup.xml file for the product you want to modify.

Example

\\server\share\Office12\setup.exe /uninstall Enterprise

where Office12 is the root of the network installation point, and Enterprise is the [ProductID] ([ProductID] is equal to the ID attribute of the Setup element listed in \\server\share\Office12\Enterprise.WW\setup.xml), where Enterprise.WW is the location of the Microsoft Office Enterprise 2007 installation files.

You can customize the /uninstall option by using it with /config and a modified Config.xml file. This is essential if you want to run a "silent" uninstall. In enterprise deployments, we recommend that you run a silent uninstall to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are in use.

To run a silent uninstall

1. Using a text editor, edit the following element attributes in the \\server\share\Office12\Enterprise.WW\SilentUninstallConfig.xml file:

   	Copy Code
   <Configuration Product="Enterprise"> <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> </Configuration>

2. At the command line, use the following syntax:

   	Copy Code
   \\server\share\Office 12\setup.exe /uninstall Enterprise /config \\server\share\Office 12\Enterprise.WW\SilentUninstallConfig.xml

Note:

In the 2007 Office system, you cannot use the Setup.exe command line to set Windows Installer properties, such as PIDKEY or DISPLAY. Setup does not pass these properties to Windows Installer. Instead, you make these customizations by using the Office Customization Tool or Config.xml. For a complete list of Setup properties, including blocked and unsupported properties, see Setup properties in the 2007 Office system.

This topic is included in the following downloadable book for easier reading and printing:

• Technical reference for the 2007 Office release

  See the full list of available books at Downloadable content for the 2007 Office Resource Kit .

Concepts