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
Example custom properties file
The content category, MsgClassTest, and the property, MSGCLASS, are defined in the following example Custom Properties.xml
file. This file also defines how the content category and property are presented in the specified application. Custom Properties.xml
must be located in the folder, Custom Filter Rules
, in the Enterprise Vault installation folder.
<?xml version="1.0"?> <CUSTOMPROPERTYMETADATA xmlns:xsi="http://www.w3.org/2001/ XMLSchema-instance" xsi:noNamespaceSchemaLocation= "customproperties.xsd"> <CONTENTCATEGORIES DEFAULT="MsgClassTest"> <CONTENTCATEGORY NAME="MsgClassTest"> <INDEXEDPROPERTIES> <PROPERTY TAG="MSGCLASS"/> </INDEXEDPROPERTIES> </CONTENTCATEGORY> </CONTENTCATEGORIES> <CUSTOMPROPERTIES> <NAMESPACE TYPE="MAPI"> <PROPERTY TAG="MSGCLASS" NAME="0x001A" /> </NAMESPACE> </CUSTOMPROPERTIES> <PRESENTATION> <APPLICATION NAME="mysearch.asp" LOCALE="1033"> <FIELDGROUPS> <FIELDGROUP LABEL="Content Category"> <FIELD TAG="MSGCLASS" LABEL="Message Class" CATEGORY="MsgClassTest"/> </FIELDGROUP> </FIELDGROUPS> <AVAILABLECATEGORIES> <AVAILABLECATEGORY CONTENTCATEGORY="MsgClassTest" LABEL="Message Class Test"/> </AVAILABLECATEGORIES> </APPLICATION> </PRESENTATION> </CUSTOMPROPERTYMETADATA>
Settings in the file are used as follows:
The <CONTENTCATEGORY> element defines the content category, MsgClassTest.
In the <INDEXEDPROPERTIES> element, the <PROPERTY> element specifies that the MSGCLASS property is to be indexed when the content category is applied to an item.
In the <PROPERTY> part of the <CUSTOMPROPERTIES> element, the standard MAPI property (NAME="0x001A") is mapped to the Enterprise Vault property tag (TAG="MSGCLASS").
0x001A is the Identifier part (bits 16 to 31) of the hexadecimal MAPI tag for the message class property.
The <PRESENTATION> element defines how the message class property is displayed in the application specified in the <APPLICATION> element. In this example, NAME="mysearch.asp" identifies the search application. The language for this application (LOCALE) is US English.
In the context of the search application, <FIELDGROUPS> identifies the new search criteria to be added to the search page. As the new property is to be listed under its associated content category, <FIELDGROUP LABEL="Content Category"> identifies the top level search criteria label. The properties to be listed when a particular content category is selected are identified by the <FIELD> settings. The <AVAILABLECATEGORIES> element identifies the content categories that can be selected. In this example, there is only one content category, which has only one property.