Veritas Enterprise Vault™ Setting up the Enterprise Vault Office Mail App
- Setting up the Enterprise Vault Office Mail App
- About Microsoft Office Mail App
- About the Enterprise Vault Office Mail App
- Enterprise Vault Office Mail App policy settings and options
- Initial configuration of HTTPS for use of the Enterprise Vault Office Mail App
- Deploying the Enterprise Vault Office Mail App
- About the PowerShell cmdlets for Office Mail Apps
- About deploying the Office Mail App with the New-App cmdlet
- About New-App command parameters for the Enterprise Vault Office Mail App
- Deploying the Enterprise Vault Office Mail App for an individual user
- Deploying the Enterprise Vault Office Mail App for multiple users
- About the Enterprise Vault Office Mail App after deployment for an individual user
- Deploying the Enterprise Vault Office Mail App for an organization
- About the Enterprise Vault Office Mail App after deployment for an organization
- Mailbox synchronization after upgrade to enable use of the Office Mail App
- Additional requirements on Enterprise Vault Office Mail App users' computers
- Disabling and re-enabling the Enterprise Vault Office Mail App for a device type
- Removing, disabling, and re-enabling the Enterprise Vault Office Mail App for a user or an organization
- Troubleshooting the Enterprise Vault Office Mail App
- Enterprise Vault Office Mail App: client tracing
- Enterprise Vault Office Mail App: server tracing
- Checking deployment of the Enterprise Vault Office Mail App
- The Enterprise Vault Office Mail App manifest file is not created
- Unable to deploy the Enterprise Vault Office Mail App at organization level
- The Enterprise Vault Office Mail App window is blank or contains an error message
- An Enterprise Vault Office Mail App action fails with an error message
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.aspxpage.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.aspxcan 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.aspxpage 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.