Enterprise Vault™ Configuring Internal and External WebApp URLs for OWA

Last Published:
Product(s): Enterprise Vault (14.1, 14.0, 12.5, 12.4, 12.3, 12.2, 12.1, 12.0, 11.0)

Overview

The Enterprise Vault OWA Extensions for Exchange Server 2007 and 2010 do not implement the EnterpriseVaultProxy mechanism that was used in the OWA 2003 extensions for accessing the Enterprise Vault server through the Exchange Servers. The task of protecting and forwarding requests to the Enterprise Vault server is now left to appropriate applications, such as Microsoft ISA Server. As a result, the OWA 2007 and 2010 extensions are simpler to install and reduce load and attack surfaces on the Exchange Servers.

The initial implementation of the Enterprise Vault OWA 2007 Extensions did not support the configuration of a different URL for Enterprise Vault access from an external network. This meant that the Enterprise Vault server names had to be published by the external DNS servers in order to enable Search Archives or Archive Explorer in external OWA clients. This document describes how to set up your OWA environment so that a different Enterprise Vault server name is published to external OWA users.

If you want to configure the functionality described in this document for an Exchange 2003-only environment, you must set the Enterprise Vault Exchange desktop policy setting "Client Connection" to "Direct", in order to turn off the EnterpriseVaultProxy mechanism. If an Exchange 2003 mailbox is accessed through an Exchange CAS, this happens automatically.

The following terms are used throughout this document:

  • "External URL" is a URL that is used outside the corporate network to access the Enterprise Vault server through a firewall.

  • "Internal URL" is a URL that is used inside the corporate network to access the Enterprise Vault server directly.