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 deploying the Office Mail App with the New-App cmdlet
Figure: New-App cmdlet overview shows the process when you use the New-App cmdlet to deploy the Enterprise Vault Office Mail App for an individual user. A simplified representation of the syntax is shown at the top of the figure.
The process is similar when you deploy the Office Mail App for a whole organization. You still specify only one mailbox in the New-App cmdlet. This mailbox must be one whose archive is stored on the Enterprise Vault server to which you want all organization level requests to be sent. In this case the Exchange Server configures the manifest file for all the mailboxes in the organization. The result is that a single Enterprise Vault server has to serve the Office Mail App to all users.
In the figure, the numbered stages are as follows:
- You run the PowerShell cmdlet New-App in the Exchange Management Shell.
The cmdlet specifies the following:
A mailbox (MBX1) that is enabled for archiving and that you want to enable for the Office Mail App.
The URL of the
OfficeMailAppManifest.aspx
page.The server that is specified in the URL can be any Enterprise Vault server in your site. In this example, the URL specifies a server named EV1.
The URL for
OfficeMailAppManifest.aspx
can use the HTTP or HTTPS protocol, depending on the protocol that is enabled in IIS on the Enterprise Vault server.
- The Exchange server sends a request to Enterprise Vault server EV1 to configure a manifest file.
- On EV1, the
OfficeMailAppManifest.aspx
page generates a manifest file for MBX1 and sends it to the Exchange server. The manifest file contains the Office Mail App settings for MBX1. The settings include the URL from which the Office Mail App will be loaded, which in this example is on Enterprise Vault server EV2 because the MBX1 archive is stored on EV2. - The manifest file is associated with MBX1 on the Exchange server.
- The New-App cmdlet completes.