Config.xml file OptionState ID values for Office 2010
Applies to: Office 2010
Topic Last Modified: 2011-04-14
The OptionState element of the Config.xml file provides options for specifying how individual product features are handled during installation. The value for the Id attribute of the OptionState element is located in the Setup.xml file in the product folder of the product that you are installing. For example, if you are installing Microsoft Office Professional Plus 2010, the file is ProPlus.WW\setup.xml.
For information about OptionState element and Config.xml, see OptionState element in Config.xml file in Office 2010. The article includes an example of a Config.xml file for a typical installation, see Sample Config.xml file.
In this article:
OptionState Id values
Config.xml file OptionState element
OptionState element syntax
Modifying the OptionState element in Config.xml
OptionState Id values
The following table provides the Id values for the applications that are installed with Microsoft Office 2010.
OptionState Id | Application and subfeature |
---|---|
ACCESSFiles |
Microsoft Access databases |
Access_PIA |
Primary interoperability assembly that allows Microsoft Access programmability with Microsoft .NET Framework |
AccessAddinPWFiles |
A wizard that creates a Windows Installer Package (MSI) to install your database and any supporting files and optionally includes the Microsoft Access Runtime, or prompts the user to download the Microsoft Access Runtime |
AccessBarcodeControl |
Barcode Control |
AccessBDCFiles |
Components that allow Microsoft Access to consume data through the SharePoint Business Connectivity Services (BCS) entity model |
AccessHelpFiles |
Help for Microsoft Access |
AccessLobiDependencies |
Additional components that are required to enable BCS connectivity |
AccessWizards |
Database experts that ask questions about a commonly used item that you want to create, and then build the item for you |
DeveloperWizards |
Database experts that ask questions about a more advanced item that you want to create, and then build the item for you |
AccessTemplatesIntl |
Templates are complete Microsoft Access database applications used to track, store, and report business and personal data. You can store the data within .accdb files or in lists on a Microsoft Windows SharePoint Services Web site |
EXCELFiles |
Microsoft Excel |
Excel_PIA |
Primary interoperability assembly that allows Microsoft Excel programmability with .NET Framework |
ExcelAddinFiles |
Microsoft Excel problem-solving tools and utilities |
ExcelAddInEuroToolFiles |
Microsoft Excel Eurotool Add-in |
ExcelHelpFiles |
Help for Microsoft Excel |
ExcelSampleFiles |
Easy-to-use examples for Microsoft Excel |
ExcelTemplatesFiles |
Microsoft Excel Spreadsheet Templates for expense reports, invoices, timecards, purchase orders, and loan amortization |
ExcelXMLEditVerb64 |
When users install a 32-bit version of Office 2010 on a 64-bit computer, registry file extensions are installed so that the 32-bit version of Office handles the XML file extension |
GrooveFiles |
Microsoft Groove Server 2010 |
OneNoteFiles |
Microsoft OneNote |
OneNoteHandwritingFonts |
Typefaces that enable you to type with text that resembles handwriting |
OneNoteHelpFiles |
Help for Microsoft OneNote |
OneNotePIA |
Primary interoperability assembly that allows Microsoft OneNote programmability with .NET Framework |
OneNoteToAddIns |
OneNote integration functionality with other applications |
OneNoteMobileSyncDesktop |
OneNote Mobile desktop synchronization component that lets you synchronize OneNote Mobile on your device to the desktop |
OUTLOOKFiles |
Microsoft Outlook |
Outlook_PIA |
Primary interoperability assembly that allows Microsoft Outlook programmability with .NET Framework |
OutlookHelpFiles |
Help for Microsoft Outlook |
OutlookImportExportFiles |
Import from and export to popular e-mail programs, personal information managers, and standard file formats |
OutlookMAPI2 |
Contains language-neutral Messaging Application Programming Interface (MAPI) core components that are required by Microsoft Outlook |
Outlook64Files |
Binary files in a 32-bit Outlook 2010 installation on a 64-bit Windows operating system |
OutlookSearchPHAndPluginReg |
Used for Microsoft Outlook Search functionality, which is a core part of Microsoft Outlook |
OutlookSearchShellReg |
Used for Microsoft Outlook Search functionality, which is a core part of Microsoft Outlook |
Outlook64SearchShellReg |
Used for Microsoft Outlook Search functionality, which is a core part of Microsoft Outlook |
OutlookStationeryFiles |
Microsoft Outlook Stationery |
OutlookVBScript |
Debugging tool for Visual Basic Scripting Edition. Used to automate Outlook custom forms |
OutlookTemplateFiles |
Microsoft Outlook Template Files |
OutlookMessaging |
Microsoft Outlook Messaging Components |
OutlookAddIns |
Microsoft Outlook Add-Ins |
OutlookOms |
Microsoft Outlook Mobile Service |
PPTFiles |
Microsoft PowerPoint |
OrgChartFiles |
Program that can be used to revise a Microsoft Organization Chart OLE object that is created with previous versions of this program |
PowerPoint_PIA |
Primary interoperability assembly that allows Microsoft PowerPoint programmability with .NET Framework |
PPTPresentationTemplates |
Templates and designs that help you create presentations |
PPTHelpFiles |
Help for Microsoft PowerPoint |
PPTSoundFiles |
Sounds used for Microsoft PowerPoint preset animation effects |
PPTXmlEditVerb64 |
When users install a 32-bit version of Office 2010 on a 64-bit computer, registry file extensions are installed so that the 32-bit version of Office handles the XML file extension |
PubPrimary |
Microsoft Publisher |
PubComPrinting |
Tools for printing color publications at commercial printing services |
Publisher_PIA |
Primary interoperability assembly that allows Microsoft Publisher programmability with .NET Framework |
PublisherHelpFiles |
Help for Microsoft Publisher |
WORDFiles |
Microsoft Word |
Word_PIA |
Primary interoperability assembly that allows Word 2010 programmability with .NET Framework |
WordBibliographyFiles |
Files that you can use with the Word Bibliography feature |
WORDBordersFiles |
Provides page borders that can be used to enhance documents |
WordCalligly |
Word Calligraphy Add-in |
WordEnvelopWizard |
Word Envelope Wizard Add-in |
WordGenko |
Word Genko Add-in |
WORDHelpFiles |
Help for Word |
WordQuickFormatsFiles |
Word Quick Formats theme files |
WORDDocumentTemplates |
Word wizards and templates |
WordXmlEditVerb64 |
When users install a 32-bit version of Office 2010 on a 64-bit computer, registry file extensions are installed so that the 32-bit version of Office handles the XML file extension |
XDOCSFiles |
Microsoft InfoPath |
XDocs_PIA |
Primary interoperability assembly that allows for Microsoft InfoPath programmability with .NET Framework |
XDOCSHelpFiles |
Help for Microsoft InfoPath |
SHAREDFiles |
Shared files for use with Microsoft Office |
AceRepl |
Installs the Microsoft Access Database Replication Conflict Manager, which you can use to resolve conflicts between replicated databases |
CAGFiles |
Collection of popular clip art that can be used to enhance Microsoft Office documents |
IMEMain_1028 |
Microsoft Office IME (Chinese Traditional) |
IMEMain_1041 |
Microsoft Office IME (Japanese) |
IMEMain_1042 |
Microsoft Office IME (Korean) |
IMEMain_2052 |
Microsoft Office Pinyin IME |
ConvertersFiltersFile |
File converters and graphics filters |
InternationalSupportFiles |
Files for international support |
OArt_DocTheme |
Set of coordinated design elements that include colors, fonts, fills, and effects that can be used within Microsoft Office documents |
OfficeDigitalSFiles |
Digital certificate for signing a Visual Basic for Applications project. Allows you to avoid unnecessary security warnings |
OffproFonts |
Fonts for International languages |
ProofingTools |
Tools for proofreading Office documents |
PubFontsSys |
Extra fonts for more design flexibility |
TCDRegistration |
ActiveX control that allows Microsoft Office clip art and templates to be downloaded from Office.com and to be opened automatically in the associated programs |
THEMESFiles |
Set of coordinated design elements that include body and heading styles, background images, bullets, and horizontal lines |
VBAFiles |
Components to support creating, editing and executing VBA macros in Office applications |
TOOLSFiles |
Applications and support files for use with Microsoft Office |
DocServicesFiles |
Document Update Utility that keeps documents on your computer up-to-date with copies of those documents in document workspaces |
EquationEditorFiles |
Inserts mathematical symbols and equations into documents |
Forms_PIA |
Primary interoperability assembly that enables Microsoft Forms 2.0 programmability with .NET Framework |
GRAPHFiles |
Creates charts from Microsoft Word, Microsoft PowerPoint, and Access data |
HTMLSourceEditing |
HTML source editor for HTML authoring of Office documents |
MSOfficeDocumentImaging |
Enables you to easily scan, perform optical character recognition (OCR), search through, extract text from, and view image documents |
MSTagPluginsFiles |
Provides intelligent recognition of data types within Microsoft Excel and Word, and useful actions for working with the data types |
OISFiles |
Microsoft Office Picture Manager is installed with the selected options |
OSESupp |
Document publishing tools and collaboration tools for use with SharePoint Products and Technologies or Microsoft FrontPage Server Extensions, and an Office List component for use with SharePoint Products and Technologies |
QueryFiles |
Provides direct database connectivity to analyze data in Microsoft Excel |
SetLanguageFiles |
Sets language options for all Office programs |
SmartTag_PIA |
Primary interoperability assembly that enables smart tag programmability with .NET Framework |
WebDriveFiles |
Enables you to use web Folders on Office-compatible Internet service providers |
The following table provides OptionState Id values for Microsoft Project 2010.
OptionState Id | Application and sub-feature |
---|---|
PROJECTFiles |
Project is installed with only the selected options. |
Project_PIA |
Primary interoperability assembly that enables Project programmability with .NET Framework |
ProjectHelpFiles |
Project end-user documentation and language reference that include Microsoft Visual Basic, ActiveX Data Objects (ADO), and Data Access Objects (DAO) |
ProjectStdHelpFiles |
Project end-user documentation and language reference that include Microsoft Visual Basic, ActiveX Data Objects (ADO), and Data Access Objects (DAO) |
ProjectTemplates |
Collection of templates that includes Project templates to create new projects and Microsoft Excel templates to use with the Visual Reports feature |
ProjectWebProj |
Resource substitution wizard is used to automatically staff enterprise projects according to outline codes associated with the task's project, outline codes that are associated with resources, and the availability of those resources |
The following table provides OptionState Id values for Microsoft SharePoint Designer.
OptionState Id | Application and sub-feature |
---|---|
WAC_SPD |
Microsoft SharePoint Designer |
WAC_HelpFiles_SPD |
Help for SharePoint Designer |
WAC_ThemesTypical_SPD |
Coordinated design elements that include body and heading styles, background images, bullets, and horizontal lines |
WAC_ThemesAdditional_SPD |
Additional coordinated design elements that include body and heading styles, background images, bullets, and horizontal lines |
WAC_PIA_SPD |
Primary interoperability assembly that enables SharePoint Designer programmability with .NET Framework |
The following table provides OptionState Id values for Microsoft Visio 2010.
OptionState Id | Application and sub-feature |
---|---|
VISIOFiles |
Microsoft Visio |
Visio_PIA |
Primary interoperability assembly that enables Microsoft Visio programmability with .NET Framework |
VisMAddons |
Tools that extend the functionality of the Microsoft Visio program (uses Metric units) |
VisUSAddons |
Tools that extend the functionality of the Microsoft Visio program (uses US units) |
VisMSolutions |
Collections of shapes, stencils, and templates for Microsoft Visio drawings (uses Metric units) |
VisUSSolutions |
Collections of shapes, stencils, and templates for Microsoft Visio drawings (uses US units) |
VisioHelpFiles |
Help for Microsoft Visio |
VisioPreviewerFiles |
Viewer for Microsoft Visio drawings that can also be used for previewing Visio drawings in Microsoft Outlook |
Config.xml file OptionState element
Administrators can modify the Config.xml file to configure attributes for the OptionState element to specify the following installation behaviors:
The feature or subfeature is not installed.
The feature or subfeature is installed the first time that it is used by the user.
The feature or subfeature is installed locally on the user's computer.
Subfeatures of the feature are set to the specified state.
OptionState element syntax
The OptionState element uses the following syntax. The attribute and element names are case-sensitive.
<OptionState
Id="optionID"
State="Absent" | "Advertise" | "Local"
[Children="force"]
/>
where:
optionId is the identifier for a feature or sub-feature that is to be installed.
Absent specifies that the feature or sub-feature is not installed.
Advertise specifies that the feature or sub-feature is installed on first use.
Local installs the feature or sub-feature on the user's computer.
Force sets all features or sub-features to their specified states.
If you set the installation state of an application in Office 2010 to "Absent," the shortcut for that application is not created on the user's computer when Office is assigned. For example, the following element definition in Config.xml prevents the shortcut for Microsoft Access 2010 from being created and Microsoft Access 2010 is not installed on the user's computer:
<OptionState Id="ACCESSFiles" State="Absent" />
Modifying the OptionState element in Config.xml
Administrators can edit the Config.xml file to customize the installation. By default, the Config.xml file that is stored in the core product folders (core_product_folder_name.WW folder such as ProPlus.WW) directs Setup to install that product. For example, the Config.xml file in the ProPlus.WW folder installs Microsoft Office Professional Plus 2010.
To modify the OptionState element
Open the Config.xml file in a text editor tool such as Notepad.
Locate the line in Config.xml that contains the OptionState element, as shown in the following example:
<!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->
Modify the OptionState element entry by specifying the options that you want to use. For example, use the following syntax if you do not want Microsoft Publisher 2010 to be installed:
<OptionState Id="PubPrimary" State="Absent" />
Repeat the previous step to specify OptionState options for other features and subfeatures that you want to change.
Save the Config.xml file.