To control the installation, first edit the Config.xml file in a text editor to include the elements you need with the appropriate settings for those elements. Then run setup.exe /config [path and file name] to specify that Setup.exe runs and uses the options you set in the Config.xml file.

Important:

Use a text editor, such as Notepad, to edit Config.xml. Do not use a general-purpose XML editor such as Microsoft Office Word 2007.

The product DVD contains examples of Config.xml files. The example files are stored under the \Files folder at the root of the DVD, in folders that correspond to different scenarios. The folders are:

Setup Contains a config.xml file for use in setting up a clean installation. You must run psconfig.exe after running Setup to finish configuring the server or server farm.

SetupFarmSilent Contains a config.xml file for use in setting up a server farm in silent mode.

SetupGradualUpgradeSilent Contains a config.xml file for use in upgrading an existing server farm gradually.

SetupSilent Contains a config.xml file for use in setting up a clean installation for a single server (stand-alone, with Windows Internal Database) in silent mode.

SetupUpgradeSilent Contains a config.xml file for use in upgrading an existing server farm gradually.

Important:

The default configuration files included with Windows SharePoint Services 3.0 omit the SETUP_REBOOT setting. You must include this setting if you want to suppress reboots during a command-line installation.

The following table contains a list of the elements in Config.xml. These elements can appear in any order, except for Configuration, which must be first, and elements such as Command, whose order in Config.xml affects how they are processed during installation.

Setup looks for a copy of Config.xml in the same folder as Setup.exe. If a copy is not found there, Setup uses the Config.xml file that resides in the core \Files folder for the product that you are installing.

You can also use the /config Setup command-line option to specify the location of the Config.xml file. For example:

Important The default configuration files included with Windows SharePoint Services 3.0 omit the SETUP_REBOOT setting. You must include this setting if you want to suppress reboots during a command-line installation.

Specifies a command line to run. The Command element commands are processed only during initial installations and uninstallations. If Command element commands are used for customizations after the initial installation, they are ignored.

String of arguments to be appended to the command line when DisplayLevel=None.

Args

string

String of arguments to be passed to the executable.

ChainPosition

Before

This command is executed before the primary product installation.

After (default)

This command is executed after the primary product installation.

Wait

mseconds

When you install with the DisplayLevel attribute set to "Full" or "Basic", this is the number of milliseconds to wait after you run the program before you continue the installation. The default is 0 (zero), which indicates no waiting.

QuietWait

mseconds

When you install with the DisplayLevel attribute set to "None", this is the number of milliseconds to wait after you run the program before you continue the installation. The default is 0 (zero), which indicates no waiting.

Execute

Install (default)

Setup executes this command when the primary product is installed.

Uninstall

Setup executes this command when the primary product is uninstalled.

Platform

x86 (default)

Specifies that this program requires the Intel x86 platform. This command runs only if the computer on which the installation is run matches this platform requirement.

x64

Specifies that this program requires a 64-bit processor that supports the x64 extensions to the x86 architecture. This command runs only if the computer on which the installation is run matches this platform requirement.

The command line can be specified for a chained installation or an executable that runs when this product is installed. If this is specified, you must specify a command line for Setup.exe rather than a single MSI file.

If there are two or more Command elements in the Config.xml file, they will run in the order in which they are specified in Config.xml.

The fully qualified path to the folder used for the log file. You can use environment variables. The default is %temp%.

Template

filename.txt

The name of the log file. If you insert the string * anywhere in the file name, a unique log file is created for each installation performed by Setup.exe (see the explanation below). If * is not included and the file name specified already exists, log information is appended to the existing file. The .txt file extension must be included. The default template is SetupExe(*).log.

You can specify a * anywhere in the Template value. Setup inserts a string in that location with the following format:

YYYYMMDDHHMMSSxxx

where:

YYYY = Year

MM = Month

DD = Day

HH = Hour

MM = Minutes

SS = Seconds

xxx = a unique string generated by Setup

Note:

The Logging element is used by Setup only if you specify the Config.xml file by using the Setup /config command-line option. If you do not specify a Config.xml file to use, then Setup uses the default logging options.

Specifies (for Windows Installer) whether or not to allow a reboot after Setup is complete. Use ReallySuppress to specify no reboot. Must be specified at the global level, not per package.

SETUP_REBOOT

Never, AutoAlways, Always, AutoIfNeeded, IfNeeded

Specifies (for Setup.exe) whether or not to allow a reboot after Setup is complete. Use Never to specify no reboot. Must be specified at the global level, not per package.

SETUPTYPE

CLEAN_INSTALL, V2V_GRADUAL_UPGRADE, V2V_INPLACE_UPGRADE

Specifies whether to install a new copy of the product or technology (CLEAN_INSTALL), install the new version side by side with the previous version for a gradual upgrade (V2V_GRADUAL_UPGRADE), install the new version and upgrade the previous version in place (V2V_INPLACE_UPGRADE). Must be specified at the global level, not per package.

SETUPCALLED

0 | 1

Use as part of the Package Id attribute.

SERVERROLE

SINGLESERVER, WFE

Specifies the type of server you are installing to: stand-alone (SINGLESERVER) or front-end Web server (WFE).

USINGUIINSTALLMODE

0 | 1

Specifies whether you are performing a silent install (0) or using the user interface for Setup (1).

Not all Windows Installer properties can be specified in the Setting element. If a blocked property is specified, Setup ends the installation process. If a supported property is specified, Setup passes the property directly to Windows Installer.