Description

The following example Power Shell script shows how to deploy the Enterprise Vault Office Mail App with external access for list of mailbox names in a text file.

Note: Log in to the Exchange server, using an account that is assigned the management role User Options. By default, members of the Organization Management role group are assigned this role.

Power Shell script:

function EVDeploy([string]$evserver, [string]$text_file) {
get-content $text_file | foreach {
  $Mbx = get-mailbox $_;
  If (New-App -mailbox $Mbx.LegacyExchangeDN -ErrorAction:Ignore -Url ("https://" + $evserver + "/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" + $Mbx.LegacyExchangeDN + "&BaseURL=https://external_access_server/EnterpriseVault")) 
   { Write-host ("Deployed to: " + $Mbx.DisplayName);
   } 
   Else {
    If (Get-App -mailbox $Mbx.LegacyExchangeDN -Identity 0cc6d075-e610-4b8a-90c6-1460e6d4d710 -ErrorAction:Ignore) 
    { Write-host ("Already deployed to: " + $Mbx.DisplayName);
     } 
    Else 
    { Write-host ("Could not deploy to: " + $Mbx.DisplayName);
    };
   };
  };
};
EVDeploy "EV_server" "Path_filename"

Follow these configuration guidelines:

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 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.

Path_filename is the path and file name for the text file that contains the list of mailbox names to enable the Enterprise Vault Office Mail App.  The file should have one name per line.

external_access_server is the name of the server that provides external access.

The "-Identity" GUID identifies the Enterprise Vault Office Mail App, and does not change.

Deploying the Enterprise Vault Office Mail App with external access for multiple users