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
Summary of default behavior for custom filtering
Table: Example custom filter and custom property configurations shows ten different configurations for custom filtering and properties.
The resulting actions taken by archiving tasks in each case are described in Table: Resulting actions for example configurations.
In all cases it is assumed that the appropriate registry settings have been configured to enable the archiving task for custom filtering. The following configuration entities are considered:
Named XML ruleset files in the folder,
Enterprise Vault\Custom Filter Rules
. In the example cases shown,John Doe.xml
andSam Cole.xml
are named ruleset files for the mailboxes John Doe and Sam Cole respectively.Remember that named ruleset files can also be created for Exchange Server public folders or specific Exchange Server journal mailboxes.
The default ruleset file for all types of archiving,
Enterprise Vault\Custom Filter Rules\Default Filter Rules.xml
.The custom properties file,
Enterprise Vault\Custom Filter Rules\Custom Properties.xml
, with custom properties defined for indexing.Content category entries in the
Custom Properties.xml
file.The registry setting, IGNORENODEFAULT, with a value of 1.
Table: Example custom filter and custom property configurations
Case | Custom properties file exists | Default content category defined | Named ruleset file exists: John Doe.xml | Named ruleset file exists: Sam Cole.xml | Default ruleset file exists | IGNORENODEFAULT set |
---|---|---|---|---|---|---|
1 | No | No | No | No | No | No |
2 | No | No | No | No | No | Yes |
3 | No | No | Yes | No | No | No |
4 | No | No | Yes | No | No | Yes |
5 | No | No | Yes | No | Yes | No |
6 | No | No | Yes | No | Yes | Yes |
7 | Yes | No | No | Yes | No | No |
8 | Yes | No | No | Yes | No | Yes |
9 | Yes | Yes | No | Yes | No | No |
10 | Yes | Yes | No | Yes | No | Yes |
Table: Resulting actions for example configurations
Case | Resulting action |
---|---|
1 | An error is written to the event log and the archiving task stops, because custom filtering is enabled but there is no ruleset file or custom property file. |
2 | Missing defaults are ignored and both mailboxes are archived according to the default mailbox policy. |
3 | An error is reported for Sam Cole's mailbox and the archiving task stops, because no default ruleset file or custom properties file exists. |
4 | John Doe's mailbox is archived according to rules in |
5 | John Doe's mailbox is archived according to rules in No custom properties are indexed. Content categories cannot be used. |
6 | As for case 5. The fact that IGNORENODEFAULT is set makes no difference. |
7 | An error is reported for John Doe's mailbox and the archiving task stops, because there is no applicable named ruleset file or default ruleset file or custom property file. |
8 | John Doe's mailbox is archived according to rules in the default mailbox policy. Sam Cole's mailbox is archived according to the rules in Sam Cole.xml. |
9 | All messages are archived from John Doe's mailbox and custom properties indexed. Messages are archived from Sam Cole's mailbox according to the rules in |
10 | As for case 9. The fact that IGNORENODEFAULT is set makes no difference. |
More Information