<Configuration [Product="productID"] >

   ...

</Configuration>

The Product attribute identifies the product affected by this Config.xml file. The productID is defined in the Setup.xml file located in the core folder for the product, in the ID attribute of the Setup element.

The Product attribute is optional, unless you set the DisplayLevel attribute to "Basic" or "None". In this case, the Product attribute is required. If the product specified by the Product attribute does not exist in the network installation point, Setup ends the installation.

The productID for Office Enterprise 2007 is located in Enterprise.WW\Setup.xml in the following line:

	Copy Code
<Setup Id="Enterprise" Type="Product" ... >

You use this productID in Config.xml to specify Office Enterprise 2007 by entering the following:

	Copy Code
<Configuration Product="Enterprise"> ... </Configuration>

<AddLanguage

   Id="ll-cc" | "match"

   [ShellTransform="Yes"]

/>

The language must be available on the network installation point.

You can have multiple AddLanguage and RemoveLanguage elements. If both RemoveLanguage and AddLanguage elements specify the same language, the AddLanguage element takes precedence and the language is installed.

Note:
If more than one AddLanguage element is specified, then one (and only one) language must specify the ShellTransform element or Setup ends the installation.

There are three different language concepts you should know about when installing the 2007 Office system:

• Setup user interface (UI): the language of the installation.

• Shell UI: the language of shortcuts, right-click context menus, and tooltips.

• Office UI: the language of the Office user interface and menus.

When there are multiple Office languages, these three values are determined as follows:

By default, the Setup UI is dependent on the set of available resources for installation and the ability to match the user locale. The Setup UI will match the user locale by default. The Shell UI depends on the set of languages being installed and by default it follows the Setup UI. The default Office UI language depends on the user locale and current user settings. The default is to use the Windows user locale set on each user's computer. This means that in the default case, the Setup UI, Shell UI, and Office UI will all be the same.

A locale in the Windows operating systems is a set of user preference information related to the user's language, environment, and cultural conventions. This information is represented as a list of values used to determine the correct input language, keyboard layout, sorting order, and the formats used for numbers, dates, currencies, and time. The user locale is a per user setting that determines the formats used by default to display dates, times, currency, and numbers, and the sorting order of text. A user locale is specified for each account created on a computer.

If an administrator specifies multiple languages for installation in the Config.xml file, the shell UI language must be chosen from the set of installing languages. To do this, administrators specify the ShellTransform attribute of the AddLanguage element in the Config.xml file. This specifies which language Setup should use for the shell UI. However, this will not necessarily affect the choice of Setup UI or Office UI when installing on the user's computer.

For instance, if you have an Office image with English, French, German, and Spanish, to specify that Setup install full language support for all these languages and have the Shell UI follow the user's default regional options, you add the following elements in the Config.xml file:

<AddLanguage Id="match" ShellTransform="yes"/> <AddLanguage Id="en-us" /> <AddLanguage Id="fr-fr" /> <AddLanguage Id="de-de" /> <AddLanguage Id="es-es" />

In the preceding example, Setup installs all of the specified languages and the Shell UI matches the language of the user's locale. If there were more languages available in the source image, the match value in the preceding example may install an additional language in the case where the match language does not resolve to one of the other four explicitly called out languages. For instance, if Japanese was also included in the source, this example would install Japanese in addition to the other four languages when installed on a computer with the user locale set to Japanese.

<ARP attribute =" value " [attribute="value"] ... />

<CCP_DRIVE Value=" value " />

<Command

   Path="path"

   [QuietArg="arguments"]

   [Args="args"]

   [ChainPosition="Before" | "After"(default)]

   [Wait="mseconds"]

   [Execute="Install"(default) | "Uninstall"]

   [Platform="x86"(default) | "x64"]

/>

The following table describes the Command element attributes.

The Command element in the Config.xml file and the Add installations and run programs option in the OCT (command-lines entered in the Add Program Entry and Modify Program Entry dialog boxes) are intended to be used only for initial product installations and uninstallations. 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.

The command line can be specified to run an arbitrary command or to run a lightweight executable that you want to run when this product is installed.

The Command element in Config.xml and the Add installations and run programs option in the OCT do not provide the software deployment capabilities that an enterprise software deployment and management tool provides, such as the ability to track deployment progress and troubleshoot problems. Therefore, it is recommended that you limit the use of Command element in Config.xml and Add installations and run programs in the OCT to running only lightweight executables or arbitrary commands that will not make changes to the computer or that do not require user input. For example, you can run a utility to copy logs or a command to launch a Welcome page at the end of installation.

Important:

Chaining is not as reliable as installing each product separately. For example, if you chain two installations together and one of the products fails or encounters an unexpected error, the primary installation and the chained installation might not be completed successfully. Therefore, using the chaining approach is not recommended. The recommended method for installing multiple products together in enterprise environments is to use a deployment management program, such as Microsoft System Center Configuration Manager 2007 or Microsoft Systems Management Server (SMS) 2003, or a third party tool, instead of chaining.

The use of Args and QuietArg is as follows:

• The Args attribute is always appended to the command. This can include switches such as "/install" or "Company=MyCorporation".

• The QuietArg attribute is also appended if setup is running silently (with Display set as Display="none"). In such cases, you can specify the QuietArg attribute with the "/quiet" switch, for example, you can use: QuietArg="/quiet".

The following statements apply to the Wait attribute:

• Setting the Wait attribute to 0 milliseconds indicates no waiting after you run the program before you continue the installation; the command will execute and move on immediately.

  Return codes are only respected if the Wait value is nonzero. If you specify 0, Setup will not wait to continue the installation after running the specified program; therefore, there is no return code to report in that case.

• Setting the Wait attribute to any positive nonzero value will wait exactly the number of milliseconds you specify. If the process ends earlier than the specified time, setup will continue. If the process has not ended when the specified time is up, setup will fail.

• Setting the Wait attribute to -1 indicates to wait indefinitely. This can be problematic because if the command process stops responding (hangs), setup will stop responding and will wait indefinitely for the command to run.

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

<COMPANYNAME Value=" companyname " />

<Display

   Level="None" | "Basic" | "Full"(default)

   CompletionNotice="Yes" | "No"(default)

   SuppressModal="Yes" | "No"(default)

   NoCancel="Yes" | "No"(default)

   AcceptEula="Yes" | "No"(default)

/>

If this element is not defined, the default settings are used. If an invalid value is specified, Setup ends the installation.

If the Level attribute is set to "Basic" or "None" and you supply a product key using the PIDKEY element, Setup assumes that you also accept the license agreement on behalf of the user.

Note:

In enterprise deployments, it is recommended that you set the Display level value to none to direct Setup to run a silent install, to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are in use. Setting the Display Level value to none assumes that the SuppressModal and CompletionNotice attributes are silenced and that the end-user license agreement (EULA) is accepted. Administrators must also make sure that no Office applications are running during an installation of the 2007 Office system. If you set the Display level value to basic and SuppressModal to yes, users may be prompted if any Office files are in use. Setting Display level to none prevents prompting users in such cases. The SuppressModal attribute does not prevent files in use messages from displaying; only Display level set to none prevents their display. The Display element is used by Setup only if Setup finds the Config.xml file in the same folder as setup.exe, or if you specify the Config.xml file by using the Setup /config command-line option. If Setup uses the Config.xml file in the product folder, then Setup uses the default display options.

<DistributionPoint Location=" path " />

If this is not specified, then Setup assumes that the Setup.exe file is located at the root of the network installation point.

Note:
The DistributionPoint element is used by Setup only if Setup finds the Config.xml file in the same folder as setup.exe, or if you specify the Config.xml file using the Setup /config command-line option. If Setup uses the Config.xml file in the product folder, it ignores this element because the network installation point has already been found.

<INSTALLLOCATION Value=" path " />

You can use system environment variables in the path. If this element is not specified, Office is installed in %ProgramFiles%\Microsoft Office.

<LIS

[CACHEACTION="CacheOnly" | "RemoveCacheOnly"]

[SOURCELIST=" semicolon-delimited-path-list "]

/>

By default, the LIS is created in the folder \MsoCache\All Users at the root of the drive into which Office is installed. Setup customization files and software updates in the Updates folder in the network installation point are also copied.

If you specify INSTALLLOCATION, the drive designation in the path is used to determine on what drive the LIS is created. For example, if the INSTALLLOCATION path is E:\office\files, the LIS is created on drive E. The sources listed by the SOURCELIST attribute are kept with the installed product and are used by Setup if the local installation source (LIS) on the user's computer is missing or corrupted.

<Logging

   Type="Off" | "Standard"(default) | "Verbose"

   Path="path"

   Template="filename.txt"

/>

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

YYYYMMDDHHMMSS xxx

where:

1. YYYY = Year

2. MM = Month

3. DD = Day

4. HH = Hour

5. MM = Minute

6. SS = Seconds

7. xxx = a unique string generated by Setup

Note:
The Logging element is used by Setup only if Setup finds the Config.xml file in the same folder as setup.exe, or if you specify the Config.xml file using the Setup /config command-line option. If Setup uses the Config.xml file in the product folder, then Setup uses the default logging options.

	Copy Code
<Logging Type="standard" Path="%temp%" Template="MyLog(*).txt" />

With this example, Setup creates a log file each time it installs the product. Setup uses unique file names such as the following:

	Copy Code
%temp%\MyLog(20060428110717CFC).txt %temp%\MyLog(20060429113143C70).txt

<MinOSRequirement

   VersionNT="version"

   WindowsBuild="number"

   ServicePackLevel="number"

/>

The following values can be used.

Setup does not proceed with the installation if the user's computer has an operating system with a version earlier than what is specified here (or the Office default if this element is not specified). You cannot specify a version of Microsoft Windows here that is earlier than the version required by the 2007 Office system.

For information about system requirements, see Getting started with the 2007 Office system.

<OptionState

   Id="optionID"

   State="Absent" | "Advertise" | "Default" | "Local"

   [Children="force"]

/>

A feature is an item that the user can choose to install. The Id value for a feature is defined in the Option element of the Setup.xml file in the core product folder.

For a list of OptionState Id Values, see Config.xml file OptionState Id values. For information about modifying the OptionState element in Config.xml, see the Modifying the Config.xml File OptionState element section in Use Group Policy Software Installation to deploy the 2007 Office system.

<PIDKEY Value=" 25-character-key " />

When the PIDKEY value is set, users are not required to enter a product key when they install Office.

<RemoveLanguage Id=" ll - cc " />

If the language is not installed on the user's computer, the RemoveLanguage element is ignored.

You can have multiple AddLanguage and RemoveLanguage elements. If both RemoveLanguage and AddLanguage elements specify the same language, the AddLanguage element takes precedence and the language is installed.

<Setting Id=" name " Value=" value " />

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. For a complete list of Windows Installer properties, including an explanation of supported and blocked properties, see Setup properties in the 2007 Office system.

The Setting element supports the REMOVEPREVIOUS setting. This setting removes the specified application from the installation and uses the following syntax:

<Setting Id="REMOVEPREVIOUS" Value="Option Id" />

where Option Id is the identifier value for the 2007 Office system application. To specify multiple applications, use a comma-separated list to indicate the appropriate Option Id values. For a complete list of Option Id values, see Config.xml file OptionState Id values.

Note:
If you are installing Outlook, a previously installed version of Outlook is always removed, regardless of the user's preference.

If you specify REMOVEPREVIOUS with an Option Id value, only the specified applications are removed.

If you do not specify REMOVEPREVIOUS, any previously installed Office applications for which a replacement is being installed are removed. This is the default behavior.

If you specify REMOVEPREVIOUS with a blank value (REMOVEPREVIOUS=""), no applications are removed.

The Setting element also supports the SETUP_REBOOT property. SETUP_REBOOT initiates a reboot after installation and uses the following syntax:

<Setting Id="SETUP_REBOOT" Value="value" />

where value can be one of the following:

• AutoAlways--Always initiate a reboot. Do not prompt the user.

• Always--Always prompt for a reboot at the end of setup.

• IfNeeded--Prompt for a reboot at the end of setup if setup requires a reboot. (Default)

• AutoIfNeeded--Initiate a reboot if setup requires a reboot. Do not prompt the user.

• Never--Never initiate or prompt for a reboot.

<SetupUpdates

   [CheckForSUpdates="Yes"(default) | "No"]

   [SUpdateLocation="path-list"]

/>

Setup looks in all the specified folders for Setup customization files that were created for the product that is being installed, and applies them in alphabetical order by file name. If a Setup customization file was specified on the Setup command line, that file is applied first, followed by any files found in the folder specified by this element.

<USERINITIALS Value=" value " />

<USERNAME Value=" value " />

The Office 2007 Username element data is populated as follows.

If the user who is running Office is the same user who installed Office, the Username and Initials supplied during setup are used. The user is not prompted when Office first starts. This case is most popular for home users who install Office themselves.

If the user who is running Office is not the same user who installed Office, Office prompts the user to confirm his or her Username and Initials when Office first starts. This case is most popular in a corporate environment, where an administrator installs Office on behalf of the user.

The value for the Username element shown to the user at first boot time may be pre-populated with a default value from a previously installed version of Office or from the currently logged on user. Note that the default value is not used unless it is confirmed by the user. If there is a previous version of Office installed on the computer, the registry key created by the previous version of Office is used. For example, if the prior Office installation is Office 2003, the registry key is provided at HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\UserInfo.