Installing the Enterprise Vault Office Mail App on Exchange 2013

In previous versions, data consultation of archived items in webmail is performed by using the Enterprise Vault Outlook Web Access (OWA) Extensions.

As of Exchange 2013 this is replaced by the Enterprise Vault Office Mail App. Once installed the OWA webmail interface looks something like this. A full guide of the installation can be found here.

The installation of the Office Mail App components needs to be performed by using some PowerShell command in the Exchange Management Shell. These are regular Exchange commands, so nothing fancy yet ;-).

First of all, there is a list of commands that you need to keep in mind when performing the installation:

  1. Get-App
  2. New-App
  3. Remove-App
  4. Disable-App
  5. Enable-App
  6. Set-App

To activate the app for a single-user:
$Mbx = get-mailbox “mailbox”
New-App -mailbox $Mbx.LegacyExchangeDN -Url (“http://EV_server/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=” + $Mbx.LegacyExchangeDN + “&BaseURL=https://external_access_server/EnterpriseVault”)

the ExternalAccessServerUrl can be left-out if no data access from external is required.

Instead of using the EV_Server-name, use the DNS Alias for the archiving platform. This to make sure the applications will continue to work after migration of the Enterprise Vault server to a new (virtual or hardware) platform.

The following command can be executed to verify of the operation was successful:
[PS] C:\Windows\system32>get-app -mailbox “My User Mailbox Account”
DisplayName Enabled AppVersion
———– ——- ———-
Enterprise Vault True 1.0
Bing Maps True 1.0
Suggested Meetings True 1.0
Unsubscribe True 1.0
Action Items True 1.0

Do note, if you pipe everything to a list (command | fl) you receive a more detailed view of the configured applications.
The applications Bing Maps, Suggested Meetings, Unsubscribe and Action Items are default applications of Exchange 2013. These should be left untouched during this deployment.

If you want to have a list of all users which are activated for the Office Mail App, execute the following PowerShell command:
get-mailbox | ForEach-Object {If(get-app -mailbox $_.LegacyExchangeDN -Identity 0cc6d075-e610-4b8a-90c6-1460e6d4d710 -ErrorAction:Ignore){Write-Host (“Already deployed to: ” + $_.DisplayName)}}
Where “-Identity 0cc6d075-e610-4b8a-90c6-1460e6d4d710″ is the ID of the Office Mail App. This should always be the same!

Tip: Keep in mind that an user to which the app is published, but which is not activated for archival on the Enterprise Vault archiving platform will see the Enterprise Vault Application in webmail and in the Outlook 2013 application. When they try to open it, the app will show an “error” that they cannot use the functionality. If you tend to leave a set of users unactivated on the archiving platform do not continue with the script below!

If you only would like to activate the user which are activated on Enterprise Vault, you can do this by using the Get-ADUser command and filter out the group membership of the Enterprise Vault provisioning groups and use this list as an input of the activation script.

If you do not care about this (for example all users will be activated), the script as listed on page 18 can be executed:
function EVDeploy([string]$evserver, [string]$ou) {
Get-Mailbox -OrganizationalUnit $ou | ForEach-Object {
If (New-App -mailbox $_.LegacyExchangeDN -ErrorAction:Ignore -Url (“http://” + $evserver + “/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=” +
$_.LegacyExchangeDN)) {
Write-host (“Deployed to: ” + $_.DisplayName);
} Else {
If (Get-App -mailbox $_.LegacyExchangeDN -Identity 0cc6d075-e610-4b8a-90c6-1460e6d4d710 -ErrorAction:Ignore) {
Write-host (“Already deployed to: ” + $_.DisplayName);
} Else {
Write-host (“Could not deploy to: ” + $_.DisplayName);
EVDeploy “EV_server” “org_unit”

But in my opinion, this is not recommended in most cases. Generally spoken, the way of the implementation of data consultation by using the Office Mail App appeals better to me. The reason is.. everything is implemented with out-of-the-box functionalities without the need of extra software installations.

Leave a Reply