How to create and deploy custom 2007 Office configurations


To deploy a custom configuration, perform the following tasks.

!—->

1. Create a network installation point

·         Copy all the files and folders from the 2007 Office system CD to a folder on the network or on your computer. For example, copy the files to \servershareOffice12.

·         Copy all language packs and additional Office products you want to deploy to the same network installation point. When you are prompted to overwrite duplicate Setup files, click No.

For more information, see Create a network installation point for the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179063.aspx).

 

2. Use the Config.xml file to customize the installation

To specify installation options, such as the path to the network installation point, the product to install, and custom setup options, and to specify the languages to install, use the Config.xml file that is located in the root of the product folder for the product that you are installing.

To edit the Config.xml file, use a text editor such as Notepad.

1.       To modify the display options that users see during installation, locate the line in the Config.xml file that contains the Display element:

<!– <Display Level=”full” CompletionNotice=”yes” SuppressModal=”no” AcceptEula=”no” /> –>

To prevent user intervention during the installation and to specify display options, you can modify the Display element information as shown in the following example:

<Display Level=”none” CompletionNotice=”no” SuppressModal=”yes” AcceptEula=”yes” />

For information, see Display element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

2.       To specify additional languages to install, use the AddLanguage elements and attributes in the Config.xml file.


Note:

If you are adding more than one AddLanguage element, you must add the ShellTransform attribute of the AddLanguage element. This attribute specifies the language that Setup uses for the shell user interface. For example, to specify that Setup install full English, French, German, and Spanish language support with the user’s default regional options language as the default installation language, you add the following AddLanguage elements and attributes 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 plus the language that matches the user’s locale, if that language is different and is available in the installation source. For more information, see AddLanguage element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

For more information, see Customize and deploy multiple language versions of the 2007 Office system (http://technet.microsoft.com/en-us/library/dd162397.aspx).

You can also use the Config.xml file to configure additional options such as the following:

·         Specify the path to the network installation point. For information, see DistributionPoint element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

·         Specify the 25-character volume license key. For information, see PIDKEY element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

·         Specify the fully qualified path to the folder on users’ computers in which the product is installed. For information, see INSTALLLOCATION element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

·         Specify logging options for Setup. For information, see Logging element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

·         Specify how the local installation source (LIS) is cached on the user’s computer. For more information, see LIS element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

·         Set the user or company name for the user on whose computer the product is being installed. For information, see USERNAME and COMPANYNAME element in Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

You can use the Config.xml file to customize many of the same options that you can configure with the Office Customization Tool, including a few additional options that are not available in the OCT. For a complete description of the areas you can configure in Config.xml, see Config.xml file in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179195.aspx).

3.       When you complete the Config.xml customizations, save the Config.xml file. You can use the /config Setup command-line option to specify the location of the Config.xml file, as shown in the following example:

\serversharesetup.exe /config \servershareEnterprise.WWconfig.xml

For information about the /config Setup command-line option, see the “/config [path]” section in Setup command-line options for the 2007 Office system (http://technet.microsoft.com/en-us/library/cc178956.aspx).

To see an example of a custom Config.xml file, see Config.xml Example in Deploy custom configurations of the 2007 Office system (step-by-step) (http://technet.microsoft.com/en-us/library/cc178960.aspx).

 

3. Create additional customizations with the Office Customization Tool (OCT)

Use the OCT to customize Setup, and configure additional customizations and installation options. This creates a Setup customization file (MSP file). For a complete description of the areas you can configure with the OCT, see Office Customization Tool in the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179097.aspx).

Note: A cumulative update for 2007 Microsoft Office system was published on December 16, 2008, Cumulative update packages for the 2007 Microsoft Office core suite applications and for 2007 Microsoft Office servers: December 16, 2008 (http://support.microsoft.com/kb/960709). Be sure to use the newest OCT hotfix package (http://support.microsoft.com/kb/958651) before deployment. This update includes a hotfix for the OCT.

1.       From the root of the network installation point you created previously, run the following command-line option to start the OCT: setup.exe /admin.

2.       Customize Setup to specify how you want Setup to manage the installation. For information, see Customize Setup before installing the 2007 Office system (http://technet.microsoft.com/en-us/library/cc179121.aspx).

3.       Set feature installation states. For information, see Configure feature installation states of the 2007 O

Comments (2)

  1. Anonymous says:

    Pingback from Microsoft Deployment Workbench, command parameters for silent installation of various applications | Sysadmins of the NorthSysadmins of the North