Deploy multiple Setup customization .msp files
Applies to: Office 2010
Topic Last Modified: 2012-01-27
You can use the Office Customization Tool (OCT) to deploy multiple Setup customization files (.msp files) to configure Microsoft Office 2010.
To use the OCT to deploy multiple .msp files, you can create a basic customization file (.msp), and then use this initial .msp to create another customization file that includes all the settings in the original .msp file and additional applications and modified settings, for example. The second .msp file can be applied to a new set of users or to existing installations.
This approach is useful in phased deployments, or when you are deploying a standard core configuration with variations for the various departments in your organization. For example, you may want to deploy Microsoft Access 2010 only to a subset of users in your organization. In such cases, you can use the OCT to configure the feature installation state for Access 2010 as Not Available in the initial Setup customization .msp. That way, the users to whom you deploy the initial .msp file do not have Access 2010 installed on their computers. Then, you use the OCT to import the initial customization .msp file to create a second customization .msp file, and you configure the feature installation state for Access 2010 as Run all from My Computer so that Access is installed on users' computers.
In this article:
- Deploy multiple Setup customization files
We recommend that you read the following articles before you customize Office 2010: Plan volume activation of Office 2010, Deploy volume activation of Office 2010, Customization overview for Office 2010, Office Customization Tool in Office 2010, Config.xml file in Office 2010, Plan for multilanguage and Proofing Tools deployment for Office 2010, and Customize deployment of language setup and Proofing Tools in Office 2010.
Deploy multiple Setup customization files
The following table highlights the process for deploying multiple .msp files.
| Steps | Instructions | Reference |
|---|---|---|
1. |
Copy all files and folders from the Office 2010 CD to a folder on the network or on your computer. For example, copy the files to \\server\share\Office14. Copy all language packs or additional Office 2010 products to the same installation point. When you are prompted to overwrite duplicate Setup files, click No. |
|
2. |
Use the OCT to create the basic Setup customization .msp file. |
Customize Setup before installing Office 2010 Customize deployment of language setup and Proofing Tools in Office 2010 |
3. |
Use the OCT to import the initial customization .msp file to create the second customization .msp file that includes the customizations that you want to use. If you added additional languages to the network installation point, the Import feature allows you to modify the installation to add language packs. You do not have to create a new customization .msp file to add language packs. Important Importing customization .msp files is intended for equivalent cross-architecture products only. You can import a 32-bit Microsoft Office Professional Plus 2010 customization .msp file into the 64-bit version of the OCT for a 64-bit Office Professional Plus 2010 .msp file. However, you cannot import a 32-bit Microsoft Word 2010 stand-alone customization .msp file into the 64-bit OCT for a 64-bit Office Professional Plus 2010 .msp file; doing so is prevented and displays an error message. |
Import an Office 2010 Setup customization file Office 2010 client video: Office Customization Tool import feature (https://go.microsoft.com/fwlink/p/?LinkId=203128) Configure feature installation states for Office 2010 Change users' configurations after installing Office 2010 Customize deployment of language setup and Proofing Tools in Office 2010 |
4. |
Deploy the customization .msp file to users' computers. The Setup customization file is a Windows Installer package (.msp) that you apply to users' computers, just as you would apply a software update. Note: To apply the Setup customization .msp file, users can double-click the .msp file. Or, users can run Msiexec.exe at the command prompt and use one of the following command-line options to apply the .msp files: msiexec.exe /p \\server\share\custom.msp msiexec /update \\server\share\Patch1.msp where \\server\share indicates the path of the shared folder that contains the .msp files. For information about Windows Installer, see the following resources on the MSDN Web site:
Users can also use Microsoft System Center Configuration Manager 2007 to deploy the .msp files. |
Distribute product updates for Office 2010 Deploy Office 2010 by using System Center Configuration Manager 2007 |