Applies to: Office 2010
Topic Last Modified: 2012-01-27
Remote users who have limited network access can deploy Microsoft Office 2010 by using DVDs that contain customized installation images.
If you are deploying Office 2010 in an environment that includes users who work primarily in the field and who have limited access to your organization's network, you can create a customized Office 2010 installation image and make the installation files available on a DVD for those users. The installation image can contain multiple languages and Office products.
In this article:
Recommended Pre-Reading
We recommend that you read the following articles before you customize Office 2010:
Deploy a customized installation by using a DVD
The following table highlights the steps that are required to deploy a customized installation by using a DVD.
1. |
Create a network installation point that contains the Office 2010 products that you want to install. |
Create a network installation point for Office 2010 |
2. |
Copy the language packs that you want to use to the network installation point. This allows Setup to coordinate a single installation of multiple language versions of the product.
Note
This step also requires modifying the Config.xml file that is in the root of the product folder for the product that you are installing.
To modify the Config.xml file, open Config.xml in an editor such as Notepad. Clear the comment for the Display element line by deleting the opening <!-- and closing --> tags.
To prevent user intervention during the update process, you can modify the Display element as follows:
<Display Level="basic" CompletionNotice="yes" SuppressModal="yes" NoCancel="yes" />
You use the AddLanguage Element of the Config.xml file to add specific languages to the installation, and specify the Id attribute of the language tag of the language that you want to deploy. For example, you add the following line in Config.xml to add the French language version:
<AddLanguage Id="fr-fr" />
You can specify more than one language by including additional <AddLanguage> elements and attributes.
If you add more than one language to the installation, you must also set the <ShellTransform> attribute of the <AddLanguage> element of Config.xml to specify the language for the shell user interface. For example, you add the following elements 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:
<AddLanguage Id="match" ShellTransform="yes"/> <AddLanguage Id="en-us " /> <AddLanguage Id="fr-fr " /> <AddLanguage Id="de-de " /> <AddLanguage Id="es-es " />
In this case, Setup installs all specified languages plus the language that matches the user's locale, if that language is different and is available in the installation source.
Save the Config.xml file in the directory that contains Setup.exe.
|
Customize deployment of language setup and Proofing Tools in Office 2010
Language identifiers and OptionState Id values in Office 2010
Config.xml file in Office 2010 |
3. |
Use the Office Customization Tool (OCT) for the customizations and installation options that you want to apply.
Note
For initial installations, we recommend that you store the customization files in the Updates folder at the root of the network installation point.
If you plan to deploy multiple Setup customization files (.msp files), you can place only one customization .msp file for each Office 2010 product that you are installing in the Updates folder for an initial installation. You must deploy the rest of the customization .msp files for a product after the Office 2010 installation is completed. Only one Setup customization file per product in the Updates folder is supported.
If you are deploying an initial installation of Office 2010 and you also want to deploy Office 2010 software updates, such as service packs and hotfixes, Setup can apply the product updates as part of the installation process. You can place the Office 2010 product updates in the Updates folder. In scenarios such as this, where the Updates folder includes both one Setup customization .msp file and product updates, Setup applies only the Setup customization .msp file with the initial installation and the product updates are applied after the installation is complete.
Make sure that you enter the product key and accept the Microsoft Software License Terms on behalf of each user who installs Office 2010 with the Setup customization file. To do this, use the Licensing and user interface page of the Setup section of the OCT.
|
Customize Office 2010
Office Customization Tool in Office 2010 |
4. |
Copy the complete Office 2010 folder that contains the source files and your customizations from the network installation point to a DVD. Distribute the DVD to users. |
|
5. |
Instruct users to run Setup.exe from the DVD that you created. For example, instruct users to type the following at the command prompt:
<CD drive_name>:\Office14\setup.exe
Note
If you saved the Config.xml file to a location other than the directory that contains Setup.exe, instruct users to provide the path of your customized Config.xml file. For example, if you are customizing the Config.xml file for Microsoft Office Professional Plus, type the following at the command prompt:
<CD drive_name>:\Office14\setup.exe /config <CD drive_name>:\ProPlus.WW\Config.xml
If you put the custom Config.xml on a network share, instruct users to use a fully qualified path. For example: \server\share\Office14\setup.exe /config \server\share\ProPlus.WW\Config.xml.
|
|