Veritas Enterprise Vault™ Setting up the Enterprise Vault Office Mail App

Last Published:
Product(s): Enterprise Vault (12.1, 12.0, 11.0.1, 11.0, 10.0.4, 10.0.3)
  1. Setting up the Enterprise Vault Office Mail App
    1.  
      About Microsoft Office Mail App
    2. About the Enterprise Vault Office Mail App
      1.  
        Enterprise Vault Office Mail App features
    3.  
      Enterprise Vault Office Mail App policy settings and options
    4.  
      Initial configuration of HTTPS for use of the Enterprise Vault Office Mail App
    5. Deploying the Enterprise Vault Office Mail App
      1.  
        About the PowerShell cmdlets for Office Mail Apps
      2.  
        About deploying the Office Mail App with the New-App cmdlet
      3.  
        About New-App command parameters for the Enterprise Vault Office Mail App
      4.  
        Deploying the Enterprise Vault Office Mail App for an individual user
      5.  
        Deploying the Enterprise Vault Office Mail App for multiple users
      6.  
        About the Enterprise Vault Office Mail App after deployment for an individual user
      7.  
        Deploying the Enterprise Vault Office Mail App for an organization
      8.  
        About the Enterprise Vault Office Mail App after deployment for an organization
      9.  
        Mailbox synchronization after upgrade to enable use of the Office Mail App
    6.  
      Additional requirements on Enterprise Vault Office Mail App users' computers
    7.  
      Disabling and re-enabling the Enterprise Vault Office Mail App for a device type
    8.  
      Removing, disabling, and re-enabling the Enterprise Vault Office Mail App for a user or an organization
    9. Troubleshooting the Enterprise Vault Office Mail App
      1.  
        Enterprise Vault Office Mail App: client tracing
      2.  
        Enterprise Vault Office Mail App: server tracing
      3.  
        Checking deployment of the Enterprise Vault Office Mail App
      4.  
        The Enterprise Vault Office Mail App manifest file is not created
      5.  
        Unable to deploy the Enterprise Vault Office Mail App at organization level
      6.  
        The Enterprise Vault Office Mail App window is blank or contains an error message
      7.  
        An Enterprise Vault Office Mail App action fails with an error message

About New-App command parameters for the Enterprise Vault Office Mail App

In the New-App command, you must specify the Active Directory attribute LegacyExchangeDN with the OfficeMailAppManifest.aspx page. You can also specify other parameters, if required. The OfficeMailAppManifest.aspx page supports the following query string parameters:

LegacyMbxDN

Mandatory. The Active Directory attribute LegacyExchangeDN for the user.

If the LegacyExchangeDN value includes any URI reserved characters, then the LegacyExchangeDN value in the -Url parameter must be encoded. The following are examples of URI reserved characters:

: / ? # [ ] @ $ & ' / + , ; =

OfficeAppName

Optional. The name of the Office Mail App in the Office Mail App Bar. The name defaults to Enterprise Vault.

BaseURL

Optional. The URL of the EnterpriseVault virtual directory on the server that is to be used to load the Office Mail App. You can set this value for an external URL or a specific Enterprise Vault server if required.

The manifest file is not generated if invalid values are supplied. The typical causes are as follows:

  • The mailbox is not enabled for archiving.

  • The LegacyExchangeDN value in the -Url parameter includes reserved characters, but the value is not encoded.

  • The BaseURL value is not valid.

If the manifest file is not generated, the New-App command may return an error message of the following type:

The app couldn't be downloaded. Error message: The remote server returned an error: (500) Internal Server Error.

The Office Mail App troubleshooting information includes an example script that returns a more detailed error message when the manifest file is not created.

See The Enterprise Vault Office Mail App manifest file is not created.