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
Deploying the Enterprise Vault Office Mail App for an organization
In an Exchange environment where archiving is to a single Enterprise Vault installation, you may decide to deploy the Office Mail App at organization level. The advantage of deployment at organization level is that it is simpler and quicker than deployment to individual mailboxes.
However, if you consider deploying the Enterprise Vault Office Mail App at organization level, note the following:
All users will see the Office Mail App in Outlook 2013 and later, and OWA 2013 and later, including users who are not enabled for Enterprise Vault. If a user is not enabled for Enterprise Vault, a message in the Office Mail App says that it is not available.
The same Enterprise Vault server is used for Office Mail App requests from all users, which could affect the overall performance of that server.
If this Enterprise Vault server becomes unavailable, all requests to load the Office Mail App will fail. You could mitigate this impact and other performance impacts by using a round robin DNS load-balancing solution.
To deploy the Enterprise Vault Office Mail App at organization level, use the PowerShell cmdlet New-App in the Exchange Management Shell.
See About deploying the Office Mail App with the New-App cmdlet.
Note:
You must log in to the Exchange server using an account that is assigned the management roles Org Custom Apps and User Options. By default, members of the "Organization Management" role group are assigned these roles. The mailbox associated with this account must reside on Exchange Server 2013 or later.
The following example shows how to use the New-App cmdlet to enable an organization for the Office Mail App.
The backtick character (') is the PowerShell line-continuation character.
Add-Type -AssemblyName System.Web $Mbx = get-mailbox "mailbox" New-App -OrganizationApp -DefaultStateForUser:enabled -Url ' ("http://EV_server/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" + [System.Web.HttpUtility]::UrlEncode($Mbx.LegacyExchangeDN)) |
Where:
mailbox is the name of a mailbox that is enabled for archiving. 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.
EV_server is the name of any Enterprise Vault server in your site. This Enterprise Vault server is not necessarily the one that is used to load the Office Mail App. The Enterprise Vault server that is used to load the Office Mail App for all users is the server where the archive for the specified mailbox is located. The name of the correct Enterprise Vault server for the specified mailbox is returned within the manifest file.
Users in the organization may access the Enterprise Vault server externally, with no direct access. In this case, the manifest file must point to the URL of the server that provides external access. The same server would also be used for internal access. For example, the server may be a Microsoft Forefront Threat Management Gateway (TMG) server.
The following example shows how to use the BaseURL parameter with the OfficeMailAppManifest.aspx
page to configure the manifest file to point to a server that provides external access.
The backtick character (') is the PowerShell line-continuation character.
Add-Type -AssemblyName System.Web $Mbx = get-mailbox "mailbox" New-App -OrganizationApp -DefaultStateForUser:enabled -Url ' ("http://EV_server/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" + [System.Web.HttpUtility]::UrlEncode($Mbx.LegacyExchangeDN) + "&BaseURL=https://external_access_server/EnterpriseVault") |
Where:
mailbox is the name of any mailbox that is enabled for archiving.
EV_server is the name of any Enterprise Vault server in your site. This Enterprise Vault server is not necessarily the one that is used to load the Office Mail App. The Enterprise Vault server that is used to load the Office Mail App for all users is the server that is specified in the BaseURL parameter.
external_access_server is the name of the server that provides external access.