Enterprise Vault™ Setting up Exchange Server Archiving
- About this guide
- Distributing Exchange Server Forms
- Setting up archiving from mailboxes
- Points to note before you set up Enterprise Vault mailbox archiving
- Defining Exchange Server mailbox archiving policies
- Mailbox policy settings when setting up Exchange Server archiving
- Mailbox policy settings when setting up Exchange Server archiving
- Defining desktop policies in Exchange Server archiving
- Desktop policy settings in Exchange Server archiving
- Options tab (Exchange Server archiving desktop policy setting)
- Advanced tab (Exchange Server archiving desktop policy setting)
- Desktop policy settings in Exchange Server archiving
- Adding Exchange Server archiving targets
- Using customized shortcuts with Exchange Server archiving
- About editing automatic messages for Exchange Server archiving
- Enabling mailboxes for Exchange Server archiving
- Setting up users' desktops
- Enterprise Vault Outlook Add-In for Exchange Server archiving
- Enterprise Vault Client for Mac OS X with Exchange Server archiving
- Getting users started with Exchange Server archiving
- Setting up Vault Cache and Virtual Vault
- Vault Cache synchronization
- Vault Cache header synchronization and content download
- Vault Cache advanced settings
- Virtual Vault advanced settings
- Setting up archiving from public folders
- About public folder policy settings
- Exchange Public Folder policy settings
- Exchange Public Folder policy settings
- Adding public folder archiving targets
- Setting up archiving of journaled messages
- Envelope Journaling
- Setting up Enterprise Vault Office Mail App for Exchange Server 2013 and later
- About the Enterprise Vault Office Mail App
- Deploying the Enterprise Vault Office Mail App
- Troubleshooting the Enterprise Vault Office Mail App
- Setting up Enterprise Vault access for OWA clients on Exchange Server 2010
- About Enterprise Vault functionality in OWA clients
- Enterprise Vault OWA Extensions in an Exchange Server 2010 environment
- Configuring access to Enterprise Vault from Outlook RPC over HTTP clients
- Using firewall software for external access to OWA and Outlook
- Configuring filtering
- About filtering
- Configuring selective journaling
- Configuring group journaling
- Configuring custom filtering
- About custom filtering ruleset files
- About controlling default custom filtering behavior
- About the general format of ruleset files for custom filtering
- About rule actions for custom filtering
- About message attribute filters for custom filtering
- About the general format of Custom Properties.xml
- About content categories
- Defining how custom properties are presented in third party applications
- Custom properties example
About the general format of Custom Properties.xml
For Enterprise Vault to access and index additional custom or standard MAPI properties on Exchange Server messages, the properties must be defined in the file Custom Properties.xml
, which you create in the Enterprise Vault\Custom Filter Rules
folder on the computer running the archiving tasks enabled for custom filtering. The installed file, Enterprise Vault\Custom Filter Rules\Example Custom Properties.xml
provides an example of this file.
The file has the following sections:
<CONTENTCATEGORIES></CONTENTCATEGORIES> This section defines available content categories. A content category is a group of settings that will be applied to an item when it is archived. This can include custom properties to index.
<CUSTOMPROPERTIES></CUSTOMPROPERTIES> This section defines the additional message properties that are to be available to Enterprise Vault.
See Defining additional MAPI properties in custom properties.
<PRESENTATION></PRESENTATION> This section defines how the content categories and custom properties are displayed to users in proprietary third party applications.
Note:
The order of these sections is significant.
The following outline shows the general format of the file:
<?xml version="1.0"?> <CUSTOMPROPERTYMETADATA xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance" xsi:noNamespaceSchemaLocation="customproperties.xsd"> <!-- 1. DEFINITION OF CONTENT CATEGORIES AVAILABLE --> <CONTENTCATEGORIES> <CONTENTCATEGORY> ... </CONTENTCATEGORY> [<CONTENTCATEGORY> ... </CONTENTCATEGORY>] </CONTENTCATEGORIES> <!-- 2. DEFINITION OF CUSTOM PROPERTIES AVAILABLE --> <CUSTOMPROPERTIES> <NAMESPACE> ... </NAMESPACE> [<NAMESPACE> ... </NAMESPACE>] </CUSTOMPROPERTIES> <!-- 3. DEFINITION OF PRESENTATION PROPERTIES AVAILABLE --> <PRESENTATION> <APPLICATION> <FIELDGROUPS> <FIELDGROUP> ... </FIELDGROUP> [<FIELDGROUP> ... </FIELDGROUP>] </FIELDGROUPS> <AVAILABLECATEGORIES> <AVAILABLECATEGORY> ... </AVAILABLECATEGORY> [<AVAILABLECATEGORY> ... </AVAILABLECATEGORY>] </AVAILABLECATEGORIES> </APPLICATION> [<APPLICATION> ... </APPLICATION>] </PRESENTATION>
A summary description of all mandatory and optional elements and attributes in the file is provided in the following section:
See Summary of custom property elements and attributes.
Whenever you modify the file, you must restart the associated archiving tasks. In a distributed environment, you must copy the updated file to each computer with tasks enabled for custom properties, and then restart the associated tasks on each computer.
If Enterprise Vault Search is used to search for custom properties, then the Enterprise Vault Application Pool in IIS Manager must also be restarted.
When performing a search for custom properties using Enterprise Vault Search, you must enter the property name in the search criteria exactly as it is specified in the Custom Properties.xml file; the case used for the property name in the search criteria must match that used in the file. Values entered for custom properties are also case-sensitive.