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 content categories
In the <CONTENTCATEGORIES> section of Custom Properties.xml
, you define the content categories that you want to apply to filtered messages.
A content category defines a group of settings that are to be applied to an item when it is archived.
The settings can include the following:
The retention category to assign to the item
The destination archive
A list of the additional message properties that Enterprise Vault is to index
There can be more than one content category defined in the <CONTENTCATEGORIES> element.
In ruleset files, the actions associated with a rule can include assigning a particular content category to messages that satisfy the rule. The content category definition in Custom Properties.xml
provides the default settings for the content category. Some of these can be overridden for particular rules.
The following example shows entries for a content category called Litigation:
<!-- 1. DEFINITION OF CONTENT CATEGORIES AVAILABLE --> <CONTENTCATEGORIES DEFAULT="Litigation"> <CONTENTCATEGORY NAME="Litigation" RETENTIONCATEGORY="Litigation" ARCHIVEID="15165263832890493848568161647.server1.local"> <INDEXEDPROPERTIES RETRIEVE="Y"> <PROPERTY TAG="CaseAuthor"/> <PROPERTY TAG="CaseStatus"/> </INDEXEDPROPERTIES> </CONTENTCATEGORY> </CONTENTCATEGORIES>
<CONTENTCATEGORIES></CONTENTCATEGORIES> defines the content category section in the file.
The DEFAULT attribute specifies the content category to be used as the default. This default applies to all types of archiving enabled for custom filtering.
This attribute is optional, if custom filtering is used, but mandatory if there are no ruleset files (unless the registry setting IGNORENODEFAULT is configured).
If filters are configured in ruleset files and a default content category is specified, any item that does not match any rules will be archived according to the settings in the default content category. If no default content category is specified, then a content category will only be applied to an item if specified by a matching rule in a filter ruleset file.
If no applicable ruleset files exist, then you must specify a default content category using the DEFAULT attribute in the <CONTENTCATEGORIES> element in
Custom Properties.xml
. The settings in the content category are then applied to all messages archived (unless the registry setting IGNORENODEFAULT is configured).The actions of archiving tasks are determined by combinations of ruleset files, custom properties, content categories and the registry setting IGNORENODEFAULT.
The <CONTENTCATEGORY> element defines a particular content category. There must be at least one content category defined.
The content category NAME is used to identify this content category in the presentation section of the file, rules in custom filter ruleset files and external subsystems, such as the Enterprise Vault Indexing service. The name must have at least five characters, which can include alphanumeric characters only (A-Z a-z 0-9); space and underscore characters are not permitted.
If the content category is included in the presentation section of the file, it will be possible to search on the content category name in order to find all items archived using this particular content category.
RETENTIONCATEGORY is optional and enables you to assign a retention category to each item archived using this content category. The retention category must already exist in Enterprise Vault.
Note:
Some Enterprise Vault features, such as the retention folders and classification features, can override this retention category. For more information on retention, see the Administrator's Guide.
ARCHIVEID is optional and enables you to specify a destination archive for the item. The archive must exist and be enabled. To find the ID of an archive, display the archive properties in the administration console and click the "Advanced" tab.
The <INDEXEDPROPERTIES> element is mandatory and groups the additional properties that Enterprise Vault is to index.
The RETRIEVE attribute (optional) determines whether or not the defined properties should be returned with archive search results. By default, the properties are not displayed with search results (RETRIEVE="N").
A <PROPERTY> element is required for each additional property to be indexed.
The TAG value must match the associated Enterprise Vault TAG value specified in the custom properties section.
See Defining additional MAPI properties in custom properties.