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
The Enterprise Vault Office Mail App manifest file is not created
If invalid parameter values are supplied for the OfficeMailAppManifest.aspx
page for use with the PowerShell cmdlet New-App, no manifest file is created. The cmdlet fails and returns 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 typical causes of this error are as follows:
The user is not enabled for Enterprise Vault.
The LegacyExchangeDN value in the -Url parameter includes reserved characters, but the value is not encoded.
The BaseURL value is not valid.
The following example returns a more detailed error message when the manifest file is not created for a specified individual user. This script also shows how you can download the application manifest to a file, then specify the file in the New-App cmdlet instead of the URL.
Add-Type -AssemblyName System.Web $Mbx = get-mailbox "mailbox" $uri = new-object system.uri( "http://EV_server/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" + [System.Web.HttpUtility]::UrlEncode($Mbx.LegacyExchangeDN)) $webclient = New-Object Net.Webclient $webClient.UseDefaultCredentials = $true try { $bytes = $webclient.DownloadData($uri) New-App -mailbox $Mbx.LegacyExchangeDN -FileData $bytes } catch [Net.WebException] { [Net.HttpWebResponse] $webResponse = [Net.HttpWebResponse]$_.Exception.Response; Write-Warning $webResponse.StatusDescription } |
Where:
mailbox is the name of the mailbox you are trying to enable for the Office Mail App.
EV_server is the name of the Enterprise Vault server.