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
Setting IGNORENODEFAULT registry entry for custom filtering
If the appropriate registry keys are configured to enable custom filtering and properties for archiving tasks, then certain configuration entities are required to define the default actions of the archiving tasks. For example, if specific targets are to be archived using particular filter rules, then a named XML ruleset file must exist for each of the archiving targets for custom filtering, and a Default Filter Rules.xml
file must also exist to provide filtering rules for the other archiving targets serviced by the archiving tasks. If this file does not exist, then the archiving tasks will stop and an error reported in the event log.
Alternatively, if the Default Filter Rules.xml
file does not exist, but you configure the IGNORENODEFAULT registry entry, the archiving tasks ignore the fact that the file is missing and use the default archiving task policy settings when archiving all targets that do not have a named ruleset file.
The IGNORENODEFAULT registry entry also enables you to restrict custom filtering to target archiving targets with named ruleset files only. (If the Default Filter Rules.xml
file exists, it is used as the default by all archiving tasks enabled for custom filtering.)
Similarly, to apply custom property indexing to specific target archiving locations, you would typically require the following configuration entities:
A
Custom Properties.xml
file with entries defining the custom properties to index and an associated content category.A separate, named ruleset file for each of the archiving targets requiring custom property indexing.
In
Custom Properties.xml
, a default content category to use for all messages archived from other locations that are not covered by the named ruleset files.
However, if you want to restrict custom filtering and custom property indexing to the named targets, it is more efficient to omit setting the default content category in Custom Properties.xml
and set the IGNORENODEFAULT registry entry. In this way, custom property indexing is applied only to locations explicitly defined by named ruleset files.
To set the IGNORENODEFAULT registry entry for custom filtering
- Log in as the Enterprise Vault Service account on the computer running the archiving tasks enabled for custom properties and filters.
- Start Regedit.
- Navigate to the following location:
HKEY_LOCAL_MACHINE \Software \Wow6432Node \KVS \Enterprise Vault \External Filtering \Journaling|Mailbox|PublicFolder
- Right-click the required archiving key (Journaling, Mailbox or PublicFolder) and select New,Key.
- Name the new key EnterpriseVault.CustomFilter.
- Right-click EnterpriseVault.CustomFilter and create a new DWORD called IGNORENODEFAULT.
- Set the value to 1 to ignore missing default files or settings.
This key will apply to all tasks for the selected type of archiving.
- Close Regedit.
- Restart the associated archiving tasks.
In a distributed environment, where you have archiving tasks running on more than one computer, you need to perform these steps on each computer running archiving tasks that have been enabled for custom filtering and properties.