Share via


Configure feature installation states for Office 2010

 

Applies to: Office 2010

Topic Last Modified: 2015-05-17

Banner stating end of support date for Office 2010 with link to more info

Use the Office Customization Tool (OCT) to create a Setup customization file (.msp file) to configure an Office 2013 installation for users.

After you create a network installation point but before you install Microsoft Office 2010, you can use the Office Customization Tool (OCT) to create a Setup customization file (.msp file) to configure the installation for users. You can use the OCT to change the default way that Office features are installed. You can set some features to be installed on the user's computer, some features to be installed only on first use, and some features not to be installed. You can even hide or lock features so that a user who runs Setup interactively can't change what you have configured. For information about the network installation point, see Create a network installation point for Office 2010.

In Office 2010, two architecture-specific versions of the Office Customization Tool (OCT) are available: one for 32-bit Office 2010 and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office 2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as shown in the following example: \\server\share\Office14\x86\setup.exe /admin. To run the 64-bit OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about 64-bit Office 2010, see 64-bit editions of Office 2010.

Configure installation states

Use the following procedure to configure feature installation states.

To configure Office feature installation states

  1. To start the OCT, from the root of the network installation point, type the following at the command prompt: setup.exe /admin.

  2. In the Select Product dialog box, select the product that you want to configure, and then click OK.

  3. In the left navigation pane, locate Features, and then click Set feature installation states.

  4. In the right navigation pane, expand the tree and select the feature that you want to customize. For example, if you opt not to install the Equation Editor, expand Microsoft Office and Office Tools, right-click Equation Editor, and then select the installation options Not Available, Hidden, and Locked. Setup does not install the Equation Editor and, if Setup is run interactively, this feature is not visible and the user can't install it.

  5. On the File menu, click Save As.

  6. In the Save As dialog box, specify a path and file name for the Setup customization file, and then click Save.

  7. On the File menu, click Exit.

  8. Copy the Setup customization file to the Updates folder in the network installation point.

When you run Setup to install Office, Setup uses the customization file that it finds in the Updates folder and configures Office features according to your customizations.

The following table describes the available installation options.

Option Description

Run from My Computer

Setup copies files and writes registry entries and shortcuts that are associated with the feature to the user's hard disk, and the feature (or application) runs on the user's computer.

Run all from My Computer

This option is the same as Run from My Computer, except that all child features that belong to the feature are also set to this state.

Installed on First Use

Setup leaves components for the feature and all of its child features in the local installation source until the user first attempts to use the feature, at which time the components are copied to the Office program folder on the user's local hard disk. Some features do not support Installed on First Use; this option is not available for these features in the OCT.

Not Available

The components for the feature, and all of the child features that belong to that feature, are not installed on the user's computer.

Note

The Not Available installation state is reversible. When Not Available is set, a feature will not be installed. However, the feature can be installed locally later by using an .msp or a Config.xml file.
To unlock and install a feature locally, you can edit the Config.xml file to modify the OptionState element as described in the note for the Locked feature state description. For more information about the Config.xml file, see Config.xml file in Office 2010.
You can also use the OCT to create an .msp file to install a feature locally. To do this, choose Set feature installation states in the navigation pane. In the details pane, select (right-click) a feature, and then set the feature installation state to Run All from My Computer. For more information, see Set feature installation states in Office Customization Tool in Office 2010.

Hidden

The feature and all of its child features do not appear in the feature tree when Setup runs interactively. Setup uses the default installation state, or the state specified in the customization file, to determine how to install the feature.

Note

The Hidden option is not reversible. After it is set, a Hidden feature will not be displayed in the feature tree during or after installation. You can't use another Config.xml file or apply a second .msp file after the initial installation to “unhide” a feature.
The feature remains hidden even if you opt to change your installation by using Programs and Features in Control Panel to change your Office 2010 installation.
It will also not be displayed in the Office Setup feature installation tree under the Add or Remove Features option for Office 2010. Though the feature remains hidden, you can unlock the feature to install and run it locally later by using an .msp file or a Config.xml file.

Locked

The feature can't be changed by the user during interactive Setup or maintenance mode.

Note

The Locked option is reversible. If you set the Locked option for a feature by using the OCT or the Config.xml file during initial installation, that feature can be unlocked and installed locally by using an .msp file or a Config.xml file at a later date.
For example, you can edit the Config.xml file to modify the OptionState element as shown in the following example. This adds the OptionState element line to install the feature (in this case, Microsoft Access 2010) on a user's computer, and to set child features of the feature to the specified state.

  • To edit the Config.xml file to modify the OptionState element, open the Config.xml file in the core product folder (core_product_folder_name.WW folder, for example, ProPlus.WW) for the Office 2010 product that you are installing. Use a text editor tool, such as Notepad, to modify the file.

  • Locate the line in the Config.xml file that contains the OptionState element:

    <!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->

  • Modify the OptionState element as follows and then save the Config.xml file:

    <OptionState Id=”ACCESSFiles” State=”local” Children=”force” />

For information about the OptionState element, see Config.xml file in Office 2010.

You can also use the OCT to create an .msp file to install a feature locally. To do this, choose Set feature installation states in the navigation pane. In the details pane, select (right-click) a feature, and then set the feature installation state to Run All from My Computer. For more information, see Set feature installation states in Office Customization Tool in Office 2010.

Note

The following subcomponents of Microsoft Publisher 2010 are not visible in the Setup feature installation state tree in Office 2010:

  • Commercial Printing and its Enhanced RGB to CMYK Conversion subcomponent

  • Font Schemes

  • PaperDirect Previews

  • Publisher Templates and its Business Publications and Other Publications subcomponents

When you change the installation state of a feature, Setup might change the installation state of a parent or child feature to match. For more information, see the Set feature installation states section in Office Customization Tool in Office 2010.

As with any deployment of Office, make sure that you test customizations and deployment in a non-production environment before you deploy Office 2010 to users in the organization.