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 Enterprise Vault proxy server configurations for access to Outlook RPC over HTTP clients
Optionally, you can use an Enterprise Vault server as a proxy server for Enterprise Vault requests from the Enterprise Vault Outlook Add-In when Outlook Anywhere is configured. The Enterprise Vault proxy server forwards Enterprise Vault requests to the Enterprise Vault server that hosts the archive. In environments with multiple Enterprise Vault sites, a separate Enterprise Vault proxy server is required for each site.
An Enterprise Vault proxy server is useful in the following situations:
If you do not want to publish multiple Enterprise Vault servers to external users.
If you want to publish separate URLs for external and internal Enterprise Vault users.
Note that an Enterprise Vault proxy server can only be used to manage connections from Outlook Anywhere clients. It cannot be used for other types of connections, such as OWA.
The figure, Figure: Example Outlook Anywhere configuration using an Enterprise Vault proxy server, illustrates an Enterprise Vault proxy server in an Outlook Anywhere configuration. The Enterprise Vault server that is used as a proxy server can also host archives, if required. Alternatively, you can set up a minimal Enterprise Vault server to be used as a proxy server only.
Settings in the Enterprise Vault Exchange Desktop policy let you configure the behavior of the Enterprise Vault Outlook Add-In when Outlook is configured to use RPC over HTTP.
The Enterprise Vault client contacts Enterprise Vault as follows:
The Enterprise Vault client first attempts to connect to the default Enterprise Vault server that hosts the archive.
If that is unavailable, the client uses the alternative web application URL that is configured in the Enterprise Vault Exchange Desktop policy.
This logic enables users to connect directly to the Enterprise Vault server that hosts the archive when they are in the office. When they are away from the office, the Enterprise Vault client connects to the Enterprise Vault proxy server.
If no URL is specified in the Enterprise Vault policy, and Enterprise Vault can determine the client's RPC over HTTP connection settings from the Outlook profile, then a URL is generated from the profile settings.
The Enterprise Vault proxy server connects to the Enterprise Vault server that hosts the archive using anonymous connections. For this reason you must configure support for anonymous connections on each Enterprise Vault server that the proxy server contacts.
In an Enterprise Vault cluster you need to configure each node in the cluster for anonymous connections.
Similarly, in building blocks configurations you may need to configure support for anonymous connections on the proxy server computer. This configuration is required for Virtual Vault users if a Storage Service can fail over to the Enterprise Vault proxy server computer.
Instructions for setting up an Enterprise Vault proxy server, and configuring support for anonymous connections are given in the following section:
See Setting up an Enterprise Vault proxy server to manage connections from Outlook Anywhere clients.