Office Customization Tool in Office 2010
Applies to: Office 2010
Topic Last Modified: 2017-04-03
To customize an installation of Microsoft Office 2010, you can use the Office Customization Tool (OCT).
In this article:
Overview of the Office Customization Tool
New Office Customization Tool features in Office 2010
Architecture-specific versions of the Office Customization Tool
Importing Office Customization Tool .msp customization files
Configuring Setup, Features, Additional content, and Outlook settings
Setup
Features
Additional content
Outlook
Downloading updated OCT files
Overview of the Office Customization Tool
The OCT is part of the Setup program and is the recommended tool for most customizations. You run the OCT by typing setup.exe /admin at the command line from the root of the network installation point that contains the Office 2010 source files. For example, use the following: *\\server\share\Office14\*setup.exe /admin. The OCT is available only with volume licensed versions of Office 2010 and the 2007 Office system. To determine whether an Office 2010 installation is a volume licensed version, check the Office 2010 installation disk to see whether it contains a folder named Admin. If the Admin folder exists, the disk is a volume license edition. If the Admin folder does not exist, the disk is a retail edition. For information about the network installation point, see Create a network installation point for Office 2010.
When you run the OCT, you choose to create a new Setup customization (.msp) file or to open an existing .msp file. If you create a new file, the OCT displays a list of the products that are available on the network installation point. You must select a single product that you want to customize.
If you use the OCT to modify an existing .msp customization file, we recommend that you select the .msp file for the same product that you customize. For example, if you customize Microsoft Office Professional Plus 2010, select an Office Professional Plus 2010 customization .msp file.
Note
The Office 2010 release requires Windows Installer 4.0 on computers that are running the 64-bit version of the OCT or importing 64-bit customization .msp files. Windows Installer 3.1 does not recognize properties such as “ProgramFiles64Folder,” which are used by the 64-bit version of the OCT and the OCT Import feature. For information about Windows Installer, see Windows Installer (https://go.microsoft.com/fwlink/p/?LinkID=111108).
By using the OCT, you customize Office and save your customizations in a Setup customization .msp file. You place the file in the Updates folder on the network installation point. When you install Office, Setup looks for a Setup customization file in the Updates folder and applies the customizations. The Updates folder can only be used to deploy software updates during an initial installation of Office 2010.
Important
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 installation is completed. Only one Setup customization file per product in the Updates folder is supported. If you are deploying multiple Office 2010 products, such as Microsoft Office Professional Plus 2010 and Microsoft Visio Professional 2010, you can include one customization .msp file for Office Professional Plus 2010 and one customization .msp file for Visio Professional 2010 in the Updates folder. The customization .msp files that you place in the Updates folder are deployed first. Therefore, they must include any Setup customizations that can't be changed after the installation, for example, the installation location.
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.
As an alternative to placing the customization .msp file in the Updates folder, you can use the Setup command-line option /adminfile to specify the fully-qualified path of the location of the .msp file. For example, type: setup.exe /adminfile \\server\share\mychanges\custom.msp.
If you use a folder other than the Updates folder for your customization files, you can specify the folder's location in the Config.xml file by using the SUpdateLocation attribute of the SetupUpdates element. The Config.xml file is located in the core product folder (core_product_folder_name.WW folder, for example, ProPlus.WW for Microsoft Office Professional Plus 2010) for the Office 2010 product that you install. For more information, see Config.xml file in Office 2010.
You can also use a Setup customization file to change an existing installation. Because a Setup customization file is an expanded form of a Windows Installer .msp file, you apply the customization file to the user's computer exactly as you would a software update. The user's existing Office installation is updated with the customizations that you make. For example, if you change the installation states of some features to Not Available and apply the resulting customization file to an existing installation of Office, those features are removed from the user's computer.
Some options in the OCT are applicable only to a new installation of Office. These options are identified in the OCT and in the OCT Help. For example, you can use the Default installation path option (in the Installation location and organization name section) to specify the folder where Office is to be installed on the user's computer. However, if a customization file is applied to an existing installation, the Default installation path option is ignored (you must uninstall and reinstall Office to change the installation location).
Before you exit the OCT, click the File menu and then click Save as to save the Setup customization file.
Every time that you save a customization file in the OCT, the tool updates the customization file’s sequencing number with the current computer date and time stamp and generates a new update globally unique identifier (GUID). The OCT .msp files are applied chronologically according to their time stamp.
To show the sequencing behavior, assume that you have created the following OCT .msp maintenance files:
An OCT .msp file that is named “uninstall-access.msp” in which you set Microsoft Office Access to Not Available. This file is saved first so that it has a lower sequencing number and an older date and time stamp. This .msp file is sequenced first and Access 2010 is set to Not Available on users' computers.
An OCT .msp file named "install-access.msp" in which you set Microsoft Office Access to Run All from My Computer (by selecting the product and setting the installation state in the Set feature installation states section). This file is saved last so that it has a higher sequencing number and a newer date and time stamp. This .msp file is sequenced later than the first OCT .msp file, "uninstall-access.msp". Therefore, the Access 2010 feature is set to Run All from My Computer on users' computers.
The OCT includes four major sections: Setup, Features, Additional Content, and Outlook. Each section contains several pages of options. When you change an option, the page name in the left pane of the OCT changes to bold type. If you open an existing Setup customization file, the bold page names indicate where options are customized.
The following table lists options that are available in the OCT.
| Section | Page |
|---|---|
Setup |
|
Installation location and organization name |
|
Additional network sources |
|
Licensing and user interface |
|
Remove previous installations |
|
Add installations and run programs |
|
Office security settings |
|
Modify Setup properties |
|
Features |
|
Modify user settings |
|
Set feature installation states |
|
Additional content |
|
Add files |
|
Remove files |
|
Add registry entries |
|
Remove registry entries |
|
Configure shortcuts |
|
Outlook |
|
Outlook profile |
|
Add Accounts |
|
Export Settings |
|
Specify send receive groups |
New Office Customization Tool features in Office 2010
The Office 2010 release provides the following new features:
Two architecture-specific versions of the OCT, 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. The OCT files are located in the Admin folder under the x86 (32-bit) and x64 (64-bit) folders, respectively.
For information about 64-bit Office 2010, see 64-bit editions of Office 2010.
Import feature that allows administrators to import 32-bit OCT customization .msp files into the 64-bit version of the OCT and 64-bit .msp files into the 32-bit version of the OCT. This allows administrators of mixed environments (32-bit and 64-bit) to do the Setup customizations one time.
Support for adding multiple Outlook e-mail accounts.
For more information about how to import .msp customization files, see Import an Office 2010 Setup customization file.
Architecture-specific versions of the Office Customization Tool
As mentioned earlier in this article, administrators run the following command-line option to start the OCT from the root of the network installation source: setup.exe /admin. You use the same command to run the 32-bit or 64-bit version of the OCT. Running setup.exe /admin on a 32-bit computer starts the 32-bit OCT, and running this command on a 64-bit computer starts the 64-bit OCT.
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.
Setup detects which products are available to create Setup customization updates and lists the results in the Create a new Setup customization file for the following product list. Because the 64-bit and 32-bit Office files are in different root directories, the 32-bit OCT lists all the 32-bit Office products in the product selection dialog box (Create a new Setup customization file for the following product), and the 64-bit OCT lists the 64-bit Office products.
Administrators use the 32-bit OCT to create, edit, and save OCT customization updates for the 32-bit Office products, and the 64-bit OCT to create, edit, and save OCT updates for the 64-bit Office products.
Office 2010 includes two architecture-specific folders: one for 32-bit and one for 64-bit, with a separate Config.xml file and Updates subfolder in the 32-bit and 64-bit folders.
Note
Office 2010 does not support side-by-side installations of 64-bit and 32-bit Office on the same computer, including across applications. For example, there is no support for side-by-side installations of the 2007 Office system 32-bit with Office 2010 64-bit, or for Microsoft SharePoint Workspace 2010 64-bit and Microsoft Excel 2010 32-bit. You can't use the Office 2010 customization tools to configure side-by-side installations or customizations of 64-bit and 32-bit Office. For example, you can't create a custom side-by-side installation with 64-bit Microsoft Office Professional 2010 and 32-bit Visio 2010 single image. For more information about 64-bit Office, see 64-bit editions of Office 2010.
Importing Office Customization Tool .msp customization files
The OCT provides support for importing Setup customization .msp files as follows:
32-bit Setup customization .msp files can be imported into 64-bit OCT and can then be used to customize 64-bit Office products.
64-bit Setup customization .msp files can be imported to 32-bit OCT and can then be used to customize 32-bit Office products.
A 32-bit Setup customization .msp file that is imported to 64-bit OCT is converted to 64-bit, and a 64-bit customization .msp file that is imported to 32-bit OCT is converted to 32-bit. To import a customization .msp file, in the Office Customization Tool, click the File menu and then click Import. In the Open dialog box, select the .msp file that you want to convert, and then click Open to start the conversion.
Note
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 can't 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 an error message is displayed.
You can't import 2007 Office system Setup customization .msp files into the Office 2010 OCT.
The Import feature can also be used when you have created an initial Setup customization .msp file for an Office 2010 product (for example, Microsoft Office Professional Plus 2010) and then later want to modify the installation to add language packs. In such cases, you first add the language packs to the network installation point that contains the Office product source files. Then you run the OCT from the root of the network installation point, create a new Setup customization file for the same product (in this example, Microsoft Office Professional Plus 2010), and then import the original customization .msp file that you created previously for Microsoft Office Professional Plus 2010. To import an .msp customization file, in the OCT, click the File menu, and then click Import. In the Open dialog box, select the previously created customization .msp file that you want to update. On the File menu, click Save As. Specify a unique name for the .msp file, and then click Save. Importing the previously created .msp file into the OCT will update the .msp file and include the added languages.
For more information about how to import .msp customization files, see Import an Office 2010 Setup customization file. For information about how to create a network installation point, see Create a network installation point for Office 2010.
Configuring Setup, Features, Additional content, and Outlook settings
The following sections provide information about the OCT areas that you can configure:
Setup
Features
Additional content
Outlook
Note
If the geographic location of the computer on which you are running the Office Customization Tool is set to a European location, and you are creating a new Setup customization .msp file or you open an existing customization .msp file for which no file format settings have been configured for Excel, PowerPoint, or Word, you might see a dialog box that prompts you to choose a default document format. Administrators can choose to keep the current settings for the Setup customization file, or choose Office Open XML formats which support all the features of Office 2010, or OpenDocument formats to use the ODF format.
To learn about the file formats, click Learn more in the dialog box to display the OCT online Help.
Setup
Use the Setup section to specify the following:
Default installation location
Default organization name
Additional network installation sources
Product key
End-user license agreement (EULA)
Display level
Previous versions of Office to remove
Custom programs to run during installation
Security settings
Setup properties
Installation location and organization name
Specify a default organization name and installation location for all users whose installation includes this Setup customization file:
Default installation path – This option specifies where Setup installs Office on the user's computer. You can use the predefined folder keyword [ProgramFilesFolder] to specify a path to standard folders in Windows. The default path is [ProgramFilesFolder]\Microsoft Office. This option is recognized only when you first install Office on a user's computer. You can't change the installation path without uninstalling and reinstalling Office.
Organization name – This name appears in the About text box (Help menu) and on the banner pages of Office applications. The name that you specify is used as the default company name for all users whose installation includes this customization file.
Additional network sources
Specify additional servers that have a copy of the network installation point.
Setup looks for servers in this list, in the order specified, if it is installing a feature on demand or if it is repairing Office and the original network installation point is unavailable.
Click Add to add a source to the list. To edit a path, select a server from the list and then click Modify. To remove a server from this list, select the server and then click Remove. To change the order of the list, select a server and then click the Move arrows to move the server up or down in the list. To remove all servers from the list, select Clear existing server list.
Note
The OCT verifies all server paths and connects to any available servers during the initial installation process to load balance the file copy process when it creates the Local Install Source (LIS). However, be aware that an unavailable source that is specified as an additional source does not cause the installation to fail.
Add/Modify Network Server Entry dialog box
In the Add Network Server Entry dialog box or Modify Network Server Entry dialog box, enter the path of a server and then click OK.
You can use a UNC path or, if all users have access to the server that uses the same drive letter, you can use a drive letter in the path. The path can contain environment variables that are delimited by percent (%) if the variables are defined for all users.
For example:
z:\office
\\server1\share\office_root
%USERNAME%\office_root
Licensing and user interface
Use this section for the product key and to accept the Microsoft Software License Terms on behalf of each user who installs Office by using the Setup customization file. Set the Display level of the user interface. These options are recognized by Setup only when you first install Office on a user's computer.
Use KMS client key A product key entry is not required for enterprise deployments that use Key Management Service (KMS) activation because all Volume License editions of Office 2010 have a KMS client key pre-installed. KMS is one of the methods that are provided by Office Activation Technologies for activating products licensed under Microsoft Volume Licensing programs. Only a KMS host computer needs a KMS host key to be activated and to establish a local activation service in your environment. Office 2010 connects to the local KMS host for activation. By default, the Use KMS client key option is selected in Enter a valid product key and licensing agreement for users.
For more information about the licensing options for Office 2010, see the Volume activation overview for Office 2010 and Volume activation quick start guide for Office 2010 included in the current release.
Enter another product key You can enter a valid Multiple Activation Key (MAK) key in the OCT by using the Enter another product key option in Enter a valid product key and licensing agreement for users in the results pane. A MAK key is another method that Office Activation Technologies provide to activate products licensed under Microsoft Volume Licensing programs. By using a MAK key, clients activate Office 2010 online by using the Microsoft hosted activation servers or by telephone.
To use a MAK key, in the Enter another product key text box, enter the MAK key (25 numbers or characters) without spaces.
Important
This information applies only to volume-licensed editions of Office 2010. It doesn't apply to Office Professional Plus for Office 365, which is licensed through subscription.
You can also use the Enter another product key option to enter a KMS key for Microsoft Visio Standard 2010 or Microsoft Visio Professional 2010. Visio 2010 is preinstalled with the Microsoft Visio Premium 2010 KMS client key by default. This enables all the Microsoft Visio Premium 2010 features. However, if you have a license agreement for either Microsoft Visio Standard 2010 or Microsoft Visio Professional 2010, you must install the appropriate KMS client key. The features that are available depend on the key that is installed.
For more information, including a list of KMS keys for license agreements for Microsoft Visio Standard 2010 and Microsoft Visio Professional 2010, see Deploy Visio 2010 in Deploy volume activation of Office 2010.
Note
You can also activate Office 2010 at the time that you install a MAK key by setting the AUTO_ACTIVATE property value. To do this, follow these steps:
-
In the OCT, select Modify Setup properties on the left pane, and then click Add in the right pane.
-
In the Add Property Value dialog box, in the Name box, type AUTO_ACTIVATE. Note that property names must be uppercase.
-
In the Value box, type 1, and then click OK.
-
I accept the terms in the License Agreement Select this check box to accept terms of your license agreement on behalf of the user.
If Display level is set to Basic or None and you supply a product key, Setup assumes that you also accept the license terms on behalf of the user. In this case, even if you do not select the I accept the terms in the License Agreement check box, the user is not prompted to accept license terms either during installation or the first time that an Office application runs.
Display level Select the user interface that you want displayed to users during installation. The options are as follows:
Full - default Setup runs interactively, displaying all the user interface options and messages.
Basic Setup displays the Welcome screen, prompts for the product key and license terms (if needed), and displays a progress bar and completion notice. No other options are presented to the user.
None Setup runs silently and displays no user interface.
Important
In enterprise deployments, we recommend that you set Display level to None to ensure that Setup runs silently, to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are being used. Setting Display level to None assumes that the Suppress modal and Completion notice options are silenced and that the license terms are accepted. Administrators must also make sure that no Office applications run during an installation of Office 2010.
If you set Display level to Basic and select the Suppress modal option, users may be prompted if there are any Office files as they are being used. Setting Display level to None prevents prompting users in these cases. The Suppress modal option does not prevent files-in-use messages from being displayed; only Display level set to None prevents files-in-use messages from being displayed.
Completion notice Select this check box if you want Setup to display a message to the user when installation is complete.
Suppress modal Select this check box if you do not want Setup to display error messages and other dialog boxes that might interrupt the installation. If you set Display level to Full, error messages and other dialog boxes are displayed regardless of the state of this check box.
No cancel Select this check box if you want to disable the cancel button (the X in upper-right corner). This setting only applies when Display level is set to Full or Basic.
Note
The Setup customization file (.msp) sets the licensing information only during the initial installation.
The previous options are identical to the settings in the Config.xml file that are shown in the following table.
| OCT option | Config.xml setting |
|---|---|
Product key |
PIDKEY element |
I accept the terms in the License Agreement |
AcceptEula attribute of the Display element |
Display level |
Level attribute of the Display element |
Completion notice |
CompletionNotice attribute of the Display element |
Suppress modal |
SuppressModal attribute of the Display element |
Note
If there are multiple products on the network installation point and you do not specify which product Setup is to install, Setup uses full display level when it prompts the user for a product, regardless of how you set Display level in the Setup customization file. You use the /config command-line option to specify which product to install. For more information, see Run Setup from a network installation point.
Remove previous installations
Specify previous versions of Microsoft Office applications to keep or remove. This option is only recognized by Setup when you first install Office on a user's computer.
By default, Setup removes previous versions of Office applications. To keep an installed Office application, click Remove previous installations in the OCT, and in the results pane select Remove the following earlier versions of Microsoft Office programs, in the list select the Office application that you do not want to remove, click Details, and in the Select Earlier Versions to Remove dialog box, under Choose which earlier versions you want Setup to remove, clear the check box for the product you want to remove, and then click OK.
Note
Microsoft Outlook 2010 can't coexist with previous versions of Outlook. If you choose to keep previous versions, do not install Outlook 2010.
Add installations and run programs
Run additional executable programs before or after the Office installation is complete. Setup runs command lines in the order listed in the tool and does not finish the installation until all command lines are executed.
In the OCT, click Add installations and run programs and in the results pane click Add to add a program to the list. To change a program, select the program in the list and then click Modify. To remove a program, select the program and then click Remove. To change the order of programs in the list, select a program and then click the Move arrows to move the program up or down in the list.
Note
Do not add a program that requires the computer to be restarted, unless it is the last program in the list. If a custom program restarts the computer, the Office installation is complete, but custom programs that appear later in this list do not run.
Command-lines entered in the Add Program Entry and Modify Program Entry dialog boxes or by using the Command in the Config.xml file are intended to be used only for initial product installations and uninstalls. The Command element commands are processed only during initial installations and uninstalls. If Command element commands are used for customizations after the initial installation, they are ignored.
Add/Modify Program Entry dialog box
When you add or modify a program entry, you enter the following information in the Add Program Entry dialog box or Modify Program Entry dialog box, and then click OK.
Target Enter the path and file name of the executable program.
Arguments Enter a string of command-line options; for example, /q /path c:\temp.
Run this program after the Office product has been installed. The program runs after the Office installation is complete. This is the recommended option. If the program does not close correctly or if the program restarts the computer, the Office installation is not affected. However, programs further down the list do not run.
Run this program before the Office product has been installed. The program runs before the Office installation starts. If the program does not close correctly or if it restarts the computer, Office is not installed, and programs further down the list do not run.
In the Add Program Entry dialog box or Modify Program Entry dialog box, you can include any of the following standard Windows folders in the path of the executable file.
| Folder | Description |
|---|---|
[INSTALLLOCATION] |
The folder in which Office is installed |
[WindowsFolder] |
Windows folder |
[SystemFolder] |
Windows System32 folder |
[ProgramFilesFolder] |
Program Files folder |
[CommonFilesFolder] |
Program Files\Common Files folder |
[DesktopFolder] |
Windows Desktop folder |
[StartMenuFolder] |
Windows Start menu |
[ProgramMenuFolder] |
Windows Start\Programs menu |
Office security settings
Customize the security settings for Office applications.
Important
Security settings specified in a Setup customization (.msp) file provide only initial default settings on users' computers. Users can change the settings after installation. To help lock down and enforce security settings, you must use Group Policy. For more information, refer to the recommendations in the 2007 Microsoft Office Security Compliance Management Toolkit (https://go.microsoft.com/fwlink/p/?LinkId=158689).
The following table lists the available options.
| Setting | Description |
|---|---|
Trusted Publishers |
Manage the list that identifies trusted sources for digitally signed macros, add-ins, Microsoft ActiveX controls, and other executable code that is used by Office applications. Office applications share a certificate-based list of trusted sources with Internet Explorer. Click Add to add a digital certificate (CER file). |
Trusted Locations |
Manage the list that identifies locations from which any file can be opened without a check by the Trust Center security feature. Click Add to add a new location, enter the following information, and then click OK:
|
Remove all Trusted Locations written by OCT during installation |
Clears the Trusted Locations list on the user's computer. Use this check box to clear the Trusted Locations list on the user's computer without adding new locations. |
Default Security Settings |
Set default security levels for add-ins, templates, and Office applications. You can set security options for the following Office applications:
The following security options are available:
|
Unsafe ActiveX Initialization |
Determine whether unsigned and, therefore, potentially unsafe, ActiveX controls can initialize using persisted data, that is, data that is saved from one instance of the control to the next. The possible values are as follows:
|
Modify Setup properties
Modify Setup properties that are applied during the Office installation. You can customize Setup properties only when you first install Office on a user's computer. Properties set in a customization file do not take effect if you apply the file to an existing installation.
To add a property, click Add. To modify a property that you have added, select the property and then click Modify. To remove a property that you have added, select the property and then click Remove.
For more information about properties and their values, see Setup properties in Office 2010.
Add/Modify Property Value dialog box
When you add or modify a Setup property, enter the information that is shown in the following table in the Add/Modify Property Value dialog box, and then click OK.
| Setting | Description |
|---|---|
Name |
The property name. Property names must be all uppercase. |
Value |
The value of the property. |
Features
Use the Features section to configure user settings and to customize which Office features are installed.
Modify user settings
Set the default values of Office application settings for users who install Office with this customization file.
Note
Using the OCT to configure user settings establishes the initial default values for the settings. Users can modify most of the settings after Office is installed. If you want to enforce user settings, use Group Policy.
You can use the OCT to provide default user settings for the following Office applications. Some applications also provide computer settings, including: Microsoft Excel 2010, Microsoft SharePoint Workspace 2010, Microsoft InfoPath 2010, Microsoft Office 2010 System, Microsoft Project 2010, Microsoft Word 2010, and Microsoft Visio 2010.
Microsoft Access 2010
Microsoft Excel 2010
Microsoft SharePoint Workspace 2010
Microsoft InfoPath 2010
Microsoft Office 2010 System
Microsoft OneNote 2010
Microsoft Outlook 2010
Microsoft PowerPoint 2010
Microsoft Project 2010
Microsoft Publisher 2010
Microsoft SharePoint Designer 2010
Microsoft Visio 2010
Microsoft Word 2010
To configure an option, expand the tree on the left, and click the user-interface element. Configurable settings associated with that element appear on the right. Double-click a setting, and select one of the options shown in the following table.
| Setting | Description |
|---|---|
Not Configured |
The setting remains as it is. |
Enabled |
The setting is modified based on your choices in the dialog box. |
Disabled |
The setting is disabled. Disabling an option may differ from not configuring the option. See the description of the specific option for more information. |
Click Show all settings to display all available user settings. Click Show configured settings only to display only those settings that you have configured.
Select the Migrate user settings check box to preserve users' custom settings from an earlier version of Office. If you change user settings and also select this check box, Setup first applies the modified settings and then migrates the user's existing custom settings, overwriting any conflicting settings.
Note
When you click Enabled to view the options for a setting and then click OK, Previous Setting, or Next Setting, the status changes to Configured, even if you do not change the setting. Inadvertently configuring the setting with an empty hyperlink, path, or file name can cause errors. If you clicked Enabled and want to ignore your changes or avoid configuring the setting, click Cancel. You can also return a setting to the Not Configured state by double-clicking the setting, selecting Not Configured, and clicking OK.
Set feature installation states
Customize how Office features are installed on the user's computer.
To change the installation state of a feature, click Set feature installation states in the OCT and in the results pane right-click the feature, and in the shortcut menu click the installation state. Some parent features consist of multiple child features. Click the plus sign (+) to the left of the parent feature to expand to view child features.
When you change the installation state of a feature, the name of the feature and the names of all its child features (if any) are displayed in bold font. This indicates that Setup will apply these changes to the installation. Features that are not displayed in bold font are installed by using the default installation state. To remove a change, select the feature and select the Reset option or select the feature and click the Reset Branch button.
The following feature installation states are typically available to users during Setup. Not all installation states are available for every feature. For example, if a feature contains a component that can't be advertised, Installed on First Use is not included in the list of available installation states for that feature.
| State | Description |
|---|---|
Run from My Computer |
Setup copies files and writes registry entries and shortcuts associated with the feature to the user's hard disk. The application or feature runs locally. |
Run All from My Computer |
Same as Run from My Computer, except 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 its child features in the local installation source until the user attempts to use the feature for the first time, at which time the components are installed. This is also known as an advertised feature. |
Not Available |
The components for the feature and the child features that belong to this feature are not installed on the 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. |
Note
The following subcomponents of Microsoft Publisher 2010 are not visible in the Setup feature installation state tree in the Office 2010 release:
-
Commercial Printing and the Enhanced RGB to CMYK Conversion subcomponent
-
Font Schemes
-
PaperDirect Previews
-
Publisher Templates and the Business Publications and Other Publications subcomponents
The following options are also available for each feature.
| Option | Description |
|---|---|
Hidden |
Setup does not display the feature in the feature tree during installation if Setup runs interactively. The symbol [H] is prepended to the feature name to indicate the feature is hidden. 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. |
Locked |
The installation state that you choose for this feature can't be changed by the user during installation or in maintenance mode after Office is installed. The symbol [L] is prepended to the feature name to indicate the feature is locked. 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 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. |
Reset |
The feature is returned to its default installation state. This is the same as selecting the feature and clicking the Reset Branch button. |
If you explicitly set a feature to its default state, the symbol [F] is prepended to the feature name to indicate that the feature will be forced into this state. This is useful if you are creating a Setup customization file to modify an existing Office installation. If you do not change the installation state of a feature, Setup does not change the feature on the user's computer. If you specify a change, including setting the feature to its default state, Setup ensures that the feature is set to that state on the user's computer.
When you change the installation state of a feature, Setup might change the installation state of a parent or child feature to match the installation state. For example, if you set a parent feature to Installed on First Use, but set a child feature to Run from My Computer, Setup also changes the state of the parent feature to Run from My Computer.
Setup does not display hidden features in the feature tree when users run Setup interactively. The feature is installed according to its defined installation state. Child features that belong to the hidden feature are also hidden.
Tip
The best use of the Hide setting is to simplify the feature tree for users. For example, you might hide the Office Tools branch of the feature tree so that users do not have to decide which tools that they need. Only the tools that you select are installed.
If you set a feature to Not Available and hide the feature in the feature tree, users can still change the setting and install the feature by installing the parent feature or by running Setup in maintenance mode. For example, if you set the Name Smart Tag Plugin feature to Not Available and Hidden, users can still install the feature by setting the parent Smart Tags Plugins feature to Run All from My Computer.
If you want to help prevent users from installing hidden features, select the Not Available, Hidden, and Locked installation states. In this case, the feature or application is not installed and is not available in maintenance mode. Users can't install the feature by changing the state of the parent feature. The only way to reverse the Not Available, Hidden, and Locked installation state selection after Office is installed is to use the OCT to create a Setup customization file that is configured to change the installation state of the feature. Then you apply the customization file to the user's computer.
Additional content
Use this section to add or remove custom files, registry entries, and shortcuts during the installation.
Add files
Add files to users' computers when Office is installed.
To create a list of files to add to the user's computer during installation, click Add, select the file that you want to add to the list, and click Add again. To change the destination path of a file, select the file in the Add custom files list and click Modify. To remove a file from the list, select the file and click Remove. You can use the SHIFT and CTRL keys to select multiple files at the same time.
When you add files to an Office installation, note the following:
Files are copied into the Setup customization file when you save the customization file and exit the OCT. Large files increase the size of the customization file and the time that is required to create the file.
If you revise a file that is currently included in the customization file, you must open the customization file by using the OCT, remove the file from the Add files list, add the revised version, and save the customization file.
If the user removes, repairs, or reinstalls Office, the custom files are removed or reinstalled together with Office. Setup does not reinstall a custom file if the file has changed since installation.
File Destination Path dialog box
In the Destination path on the user's computer dialog box, enter the folder where you want to install the file on users' computers, and click OK.
You can select multiple files at the same time by using the SHIFT and CTRL keys. These files will be associated with the same destination folder. You can use the special folder names that are shown in the following table in the destination path.
| Folder | Description |
|---|---|
[INSTALLLOCATION] |
The folder in which Office is installed |
[ROOTDRIVE] |
The local disk drive with the most free space |
[ProgramFilesFolder] |
Program Files folder |
[CommonFilesFolder] |
Program Files\Common Files folder |
[WindowsFolder] |
Windows folder |
[SystemFolder] |
Windows System32 folder |
[PersonalFolder] |
The user's My Documents folder |
[AppDataFolder] |
The user's Application Data folder |
[NetHoodFolder] |
The user's My Network Places folder |
Remove files
Remove files from users' computers when Office is installed.
To create a list of files to remove from the user's computer during installation, click Add. To modify the path or name of a file, select the file in the Remove files list and click Modify. To remove a file from the list, select the file and click Remove. You can use the SHIFT key and CTRL key to select multiple files at the same time.
Note
Files listed in the Remove files list are removed from the user's computer before files listed in the Add files list are installed. Therefore, you can delete existing files on a user's computer and replace them with new versions. If the destination file on a user's computer is renamed or modified, an added file that has the same name does not replace it.
File Path dialog box
In the File path dialog box, enter the path and file name of the file that you want to add to the list of files to remove from the user's computer, and click OK.
The path must begin with a drive letter, a UNC path, or one of the special folders shown in the following table.
| Folder | Description |
|---|---|
[INSTALLLOCATION] |
The folder in which Office is installed |
[ROOTDRIVE] |
The local disk drive with the most free space |
[ProgramFilesFolder] |
Program Files folder |
[CommonFilesFolder] |
Program Files\Common Files folder |
[WindowsFolder] |
Windows folder |
[SystemFolder] |
Windows System32 folder |
[PersonalFolder] |
The user's My Documents folder |
[AppDataFolder] |
The user's Application Data folder |
[NetHoodFolder] |
The user's My Network Places folder |
Add registry entries
Add or modify registry entries on users' computers when Office is installed.
To create a list of registry entries to add to users' computers, click Add. To change an entry in the list, select the entry and click Modify. To remove an entry from the list, select the entry and click Remove. Click Import to add a set of entries from a registry file (.reg file). If an entry in the .reg file duplicates an entry in the list, the OCT prompts you to choose whether to overwrite existing registry entries with entries in the .reg file.
Important
Registry entries customized in this section might override settings customized elsewhere in the OCT. Use this section to customize options that can't be set directly in the Office user interface and that are not configurable by using other methods in the OCT.
You should not use the Add registry entries section of the OCT to add registry-based policy keys (Group Policy-based registry keys). Configuring and distributing those settings in a customization update (.msp file) to users is not supported, and the settings might not be applied correctly. Registry-based policy settings are settings that are stored in any of the four registry locations for Group Policy settings:
For user policy settings:
-
HKCU\Software\Policies
-
HKCU\Software\Microsoft\Windows\CurrentVersion\Policies
-
HKLM\Software\Policies
-
HKLM\Software\Microsoft\Windows\CurrentVersion\Policies
Add/Modify Registry Entry dialog box
In the Add/Modify Registry Entry dialog box, enter the information that is shown in the following table for each registry entry, and then click OK.
| Setting | Description |
|---|---|
Root |
Select the branch that contains the entries that you want to add or modify. Settings are applied once per user (HKEY_CURRENT_USER) or once per computer (HKEY_LOCAL_MACHINE). You can't add registry entries to the root of HKEY_USERS or HKEY_LOCAL_MACHINE. |
Data type |
Select a data type for the registry value. |
Key |
Enter the name of the subkey where the entry is stored. For example, Software\Microsoft\Office\14.0\Common. |
Create empty key |
Select this check box if the registry entry does not contain a value name or value data. Some settings are determined by the presence or absence of the registry entry. |
Value name |
Enter a name for the new registry entry. If you include Value data but leave this field blank, the value is assigned the name <Default>. A key can have only one <Default> value name. |
Value data |
Enter the data (value) to store in the new registry entry. The data must match the data type. |
Remove registry entries
Remove registry entries from users' computers when Office is installed.
To create a list of registry entries to remove from users' computers, click Add. To change an entry in the list, select the entry and click Modify. To remove an entry from the list, select the entry and click Remove.
To create a list of registry entries to remove from users' computers, click Add and enter the following information for each registry entry.
Note
If the user removes, repairs, or reinstalls Office, the custom registry entries are removed or reinstalled with Office.
Delete/Modify Registry Entry dialog box
In the Delete/Modify Registry Entry dialog box, enter the information that is shown in the following table for each registry entry, and then click OK.
| Entry | Description |
|---|---|
Root |
Select the branch that contains the entries that you want to remove. |
Key |
Enter the full name of the subkey where the entry is stored. For example, Software\Microsoft\Office\14.0\Common. |
Value name |
Enter the name of the registry entry that you want to remove. Leave this field blank to remove the entire subkey, including all its value entries. |
Configure shortcuts
Add shortcuts to files installed with Office 2010 or files that were already on the user's computer. You can configure shortcuts only when you first install Office on a user's computer. This option is ignored if you apply the Setup customization file to an existing installation.
Click Add to add a new shortcut. To modify a shortcut in the list, select the shortcut and click Modify. To remove a shortcut from the list, select the shortcut and click Remove.
Shortcuts with Yes in the Installed column are configured during installation. Shortcuts with No in this column are configured if the corresponding product is later installed.
Note
If you add a shortcut to a custom application or file, that shortcut is not updated or removed if the user modifies, repairs, reinstalls, or removes Office.
Add/Modify Shortcut Entry dialog box
In the Add/Modify Shortcut Entry dialog box, enter the information that is shown in the following table for the shortcut that you create or modify, and then click OK.
| Setting | Description |
|---|---|
Target |
Specify the application associated with the shortcut by selecting a predefined application keyword or by entering the name and path of the file to which the shortcut will point. If you select an application keyword, the OCT automatically enters information in the remaining boxes. The names in the list correspond to features that you select on the Set feature installation states page of the OCT, plus any custom files that you add to the installation on the Add files page. If you enter a name and path and the name or path contains a space, you must enclose the entire string in double quotation marks (""). You can add command-line options for the application by using the Arguments field. |
Location |
Specify the folder in which the shortcut is created by selecting a predefined folder keyword or by entering the name and path of the location of the shortcut. You can specify a subfolder by appending a backslash (\) followed by the subfolder name. For example, to install the Microsoft Word 2010 shortcut in the Microsoft Office subfolder in the Programs folder in the Start menu, select [ProgramMenuFolder] and append the subfolder name as follows: [ProgramMenuFolder]\Microsoft Office. You can use the following special folders for Location:
|
Name |
Enter any string to specify a name for the shortcut. |
Start in |
Enter a path to specify the default starting folder for the application. If you leave this box blank, the default folder is set to the folder where the destination file resides. If the path is not valid on a user's computer, the user sees an error message when the user tries to use the shortcut. |
Arguments |
Enter optional arguments to pass to the application on the command line. |
Shortcut key |
Enter an optional keyboard shortcut for the application or file. The syntax for the shortcut key is as follows: [modifier+]VK_key where modifier is SHIFT, CTRL, ALT, or EXT, and VK_key is a virtual key name (virtual key names, and hexadecimal key codes and descriptions are provided in the following table). The modifier is optional. You may specify more than one, in any order, separated by plus signs (+). If you use a modifier, it must precede the virtual key name. You must enter one virtual key name. Do not use spaces anywhere in the key definition. For example, CTRL+VK_F12 CTRL+SHIFT+VK_A ALT+CTRL+VK_SNAPSHOT Some key combinations, such as CTRL+ALT+VK_DELETE, might be used by the system or other processes. These combinations must not be used to open the application on the user’s computer. |
Run |
Select the kind of window in which the application or file is to start (Normal window, Minimized, or Maximized). |
Change Icon |
Select a different icon for the shortcut. |
The following table lists virtual key names and their corresponding hexadecimal key codes.
| Virtual Key Name | Key Code (Hex) | Description |
|---|---|---|
VK_0 – VK_9 |
30-39 |
Keys 0-9 |
VK_A – VK_Z |
41-5A |
Keys A-Z |
VK_NUMPAD0 – VK_NUMPAD9 |
60-69 |
Keys 0-9 on the numeric keypad |
VK_F1 ... VK_F24 |
70-87 |
Function keys F1-F24 |
VK_LBUTTON |
01 |
Left mouse button |
VK_RBUTTON |
02 |
Right mouse button |
VK_CANCEL |
03 |
Control-break processing |
VK_MBUTTON |
04 |
Middle mouse button (three-button mouse) |
VK_BACK |
08 |
BACKSPACE key |
VK_CLEAR |
0C |
CLEAR key |
VK_RETURN |
0D |
ENTER key |
VK_PAUSE |
13 |
PAUSE key |
VK_CAPITAL |
14 |
CAPS LOCK key |
VK_PRIOR |
21 |
PAGE UP key |
VK_NEXT |
22 |
PAGE DOWN key |
VK_END |
23 |
END key |
VK_HOME |
24 |
HOME key |
VK_LEFT |
25 |
LEFT ARROW key |
VK_UP |
26 |
UP ARROW key |
VK_RIGHT |
27 |
RIGHT ARROW key |
VK_DOWN |
28 |
DOWN ARROW key |
VK_SELECT |
29 |
SELECT key |
VK_EXECUTE |
2B |
EXECUTE key |
VK_SNAPSHOT |
2C |
PRINT SCREEN key |
VK_INSERT |
2D |
INS key |
VK_DELETE |
2E |
DEL key |
VK_HELP |
2F |
HELP key |
VK_MULTIPLY |
6A |
Multiply key |
VK_ADD |
6B |
Add key |
VK_SEPARATOR |
6C |
Separator key |
VK_SUBTRACT |
6D |
Subtract key |
VK_DECIMAL |
6E |
Decimal key |
VK_DIVIDE |
6F |
Divide key |
VK_NUMLOCK |
90 |
NUM LOCK key |
VK_SCROLL |
91 |
SCROLL LOCK key |
Outlook
Use the Outlook section of the OCT to customize the default Microsoft Outlook 2010 profile and to set Outlook 2010 and Microsoft Exchange Server 2010 options.
Outlook Profile
Customize a user's default Outlook profile, which is the set of values in the Windows registry that defines user-specific information. An Outlook profile can contain multiple e-mail accounts. Users can have multiple Outlook profiles. However, you can configure only one profile in the Setup customization file. The settings in the following table enable you to customize a user’s Outlook profile.
| Setting | Description |
|---|---|
Use existing profile |
Use the profile already configured on the user’s computer, or if no profile exists, prompt the user to create a profile the first time Outlook starts. |
Modify profile |
Select one of two options:
If no default profile exists or there is no profile by the name that you specify with the second option, Outlook creates a profile based on the options that you choose in the other Outlook sections of the OCT. Outlook uses the default profile name or uses the profile name that you specify. |
New profile |
Create a new profile on the user’s computer and make it the default profile. Existing profiles are not removed and remain available to users. You must enter a name in the Profile name text box. To find the name of an existing profile, go to Mail in the Control Panel and click Show Profiles. Outlook creates the profile based on the options that you choose in the other Outlook sections of the OCT. |
Apply PRF |
Import an Outlook profile file (.prf) to define a new default profile or to update an existing profile. Selecting this option does not update the OCT with the settings in the .prf file. Enter a name and path for the profile in the Apply the following profile (PRF file) text box. If you created a .prf file for an earlier version of Outlook, you can import it to Outlook 2010 if the profile defines only MAPI services. |
Add Accounts
Include new Outlook e-mail accounts in the user’s profile.
Select the Do not customize Outlook profile and account information option if you do not want to add accounts to a new or modified Outlook profile.
Select the Customize additional Outlook profile and account information option to specify new account information in a new or modified Outlook profile.
Click Add to add a new account to the list. To modify an account in the list, select the account and then click Modify. To remove an account from the list, select the account and then click Remove.
You can also specify the following:
Deliver new mail to the following location When you configure an Exchange Server computer or add an Outlook data file (.pst), select this option to specify a delivery location for new e-mail messages. The default location is the Exchange Server computer, if one is configured; otherwise, the location defaults to the .pst file on the user’s computer.
Default e-mail account Select the account that is the default e-mail account for users.
Add Account and Account Settings dialog box
If you are adding a new account, select the kind of account to add and then click Next.
In the *<account type> *Settings dialog box, set the options that are appropriate for the kind of account that you are adding or modifying, such as account name, user name, mail server, and e-mail address. Click More Settings for additional configuration options. If you are adding or modifying an Exchange account, see Exchange settings in the next section. Click Finish when you are finished.
To ensure that e-mail services do not overlap, Outlook might not enable you to add more than one new account for the same kind of service. For example, Outlook verifies that all POP accounts have unique names. The following table shows how Outlook determines whether a new account of the same type as an existing account can be added to the Setup customization file.
| Account type | More than one of this type allowed? | Data used to determine whether conflict exists |
|---|---|---|
POP3 |
Yes |
Account name |
IMAP |
Yes |
Account name |
Outlook Data File (.pst) |
Yes |
File name and path of .pst file |
Outlook Address Book |
No |
Existence of account |
LDAP |
Yes |
Account name |
Exchange |
Yes |
Account name |
Exchange settings
Configure users' Microsoft Exchange settings in a new or modified Outlook profile. The following table lists the possible settings.
| Setting | Description |
|---|---|
Account name |
Specify a name for the Account type. |
User name |
Identify the user by using a specific value or replaceable parameter. If you specify the default %USERNAME%, Outlook uses the user's exact logon name, instead of prompting the user with possible variations when Outlook starts. |
Exchange Server |
Enter the name of an Exchange server that is likely to be available when users start Outlook. When a user starts Outlook for the first time, Outlook replaces this value with the user’s correct Exchange server. Provide only a literal server name in this text box; for example, Exch-2-Srvr. Do not include backslashes (\\) or similar syntax. |
Overwrite existing Exchange accounts |
Select this option to replace an existing Exchange Server account in the user’s profile with this account. |
More Exchange Server Settings
Click the More Settings button in the Exchange Settings dialog box to configure Exchange Server offline use options and the Outlook Anywhere feature.
Exchange
Use the following options to configure user’s Outlook profiles for offline use and Outlook Anywhere.
| Option | Description |
|---|---|
Enable offline use |
|
Configure Outlook Anywhere |
Connect to Exchange Mailbox using HTTP Select this option to enable Outlook Anywhere. If you have enabled Outlook Anywhere, you can configure the following options:
|
Cached Mode
Use the following options to configure users' Outlook profiles to use a local copy of the Exchange mailbox.
| Option | Description |
|---|---|
Do not configure Cached Exchange Mode |
By default, Exchange mailboxes can be accessed from the Exchange Server computer, instead of being cached on users’ computers in an offline Outlook Data File (.ost). |
Configure Cached Exchange Mode |
Create an .ost file or use an existing .ost file. Users work with a local copy of their Exchange mailbox. If you select Use Cached Exchange Mode, you can configure Cached Exchange Mode for users by using the following options:
|
Export Settings
Export settings to a Outlook profile file (.prf).
Click the Export Profile Settings button to save the Outlook profile settings that you have defined in a .prf file.
Tip
An efficient way to create an Outlook .prf file is to use the OCT to make selections and then export them to a .prf file, even if you are not using a Setup customization file when you deploy Office. You can edit the .prf file to make additional customizations that are not exposed in the OCT. For example, you can add an e-mail provider that is not listed in the OCT.
Specify Send/Receive Groups
Define Send/Receive groups for Exchange accounts and folders, and specify the tasks that are performed on each group during a Send/Receive in Outlook. A Send/Receive group contains a collection of Outlook accounts and folders. You can specify different options for Send/Receive groups when Outlook is online and offline, as shown in the following table.
| Option | Description |
|---|---|
Do not configure Send/Receive settings |
Do not configure settings for Send/Receive groups. Outlook is configured to use only the All Accounts group and its default settings. (If users have created additional groups, those groups migrate when users upgrade to Outlook 2010.) |
Configure Send/Receive settings |
Configure settings for Send/Receive groups (Exchange accounts and folders only).
|
New Exchange Group dialog box
Enter the name of the Exchange send/receive group that you are creating in the New Group Name box and then click OK.
Modify Group dialog box
When you modify a group, select from the following options in the Modify Group dialog box and then click OK.
Select the options shown in the following table under Select options for this Send/Receive group.
| Option | Description |
|---|---|
Send mail items |
Send mail items from the Outbox when you execute a Send/Receive for this group. |
Receive mail items |
Receive mail items when you execute a Send/Receive for this group. |
Make folder home pages available offline |
Refresh the content in folder home pages when you execute a Send/Receive for this group. |
Synchronize forms |
Synchronize forms when you execute a Send/Receive for this group. |
Under Change folder options for this Send/Receive group, select a folder and provide the information that is shown in the following table.
| Option | Description |
|---|---|
Include this folder in Send/Receive |
Add this folder to the set of folders that are updated during a Send/Receive for this Send/Receive group, and select from the following options:
|
Rename Exchange Group dialog box
Enter the new name of the Exchange send/receive group in the New Group Name box and then click OK.
Send/Receive settings for the selected group
Specify settings for the Send/Receive group selected in the list. The name of the selected group appears in the option label. You can specify different settings for when Outlook is online or offline.
When Outlook is Online
Include this group in Send/Receive Execute a Send/Receive action on this group when the user clicks Send/Receive.
Schedule an automatic Send/Receive every n minutes Choose the interval between each Send/Receive action.
Perform an automatic Send/Receive when exiting Automatically execute a Send/Receive action for this group when the user exits Outlook.
When Outlook is Offline
Include this group in Send/Receive Execute a Send/Receive action on this group when the user clicks Send/Receive.
Schedule an automatic Send/Receive every n minutes Choose the interval between each Send/Receive action.
Exchange Address Book
Download offline address book Download the offline address book (OAB) when the user clicks Send/Receive.
Click Address Book Settings to open the Modify Address Book Settings dialog box. You can select Download changes since last Send/Receive to download only updates to the address book since the last download. To download the full address book with each Send/Receive, clear the Download changes since last Send/Receive check box.
Modify Address Book Settings dialog box
Configure the default way in which Outlook updates the offline address book (OAB). Select from the following options:
Download changes since last Send/Receive Outlook downloads only the changes that were made to the address book since the last Send/Receive. This generally takes less time to download than downloading the complete address book.
Full Details When the address book is downloaded, Outlook copies all of the details for each entry.
No Details When the address book is downloaded, Outlook copies only essential information, such as the name and e-mail address for each entry. This takes less time to download, but address details are not included in the offline address book. This is a legacy option supported by Outlook Address book (OAB) versions 2.0 and 3.0. If Outlook connects to a server that supports OAB 4.0 or a later version, the full details are downloaded even if this option is selected.
Downloading updated OCT files
You can download the latest version of the OCT and .opax settings files from the Microsoft Download Center: Office 2010 Administrative Template files (ADM, ADMX/ADML) and Office Customization Tool (https://go.microsoft.com/fwlink/p/?LinkId=189316). The download package includes an \Admin folder that contains the OCT and OCT files (.opax and .opal files).
To update the OCT, replace the /Admin folder in your Office 2010 installation files or installation image with the new /Admin folder that is included in the download package.
For more information about the download, see Office 2010 Administrative Template files (ADM, ADMX, ADML) and Office Customization Tool.
See Also
Concepts
Setup architecture overview for Office 2010
Config.xml file in Office 2010
Setup properties in Office 2010
Import an Office 2010 Setup customization file
Customization overview for Office 2010
Customize the installation for Office 2010
Customize setup for Office 2010
Create custom configurations of Office 2010
Customize deployment of language setup and Proofing Tools in Office 2010
Configure Outlook 2010
Change users' configurations after installing Office 2010
View Office Customization Tool output in Office 2010
Group Policy overview for Office 2010
Use Group Policy to enforce Office 2010 settings
Office 2010 Administrative Template files (ADM, ADMX, ADML) and Office Customization Tool
Other Resources
Office 2010 Administrative Template files (ADM, ADMX, ADML) and Office Customization Tool download