Enterprise Vault™ Configuring Internal and External WebApp URLs for OWA

Using an Exchange CAS (internal and external)

Although this appears similar to using an Exchange CAS as a proxy server, the Exchange CAS is unable to pass on any information to the OWA 2003 Extensions. This means that if both internal and external clients access the Exchange CAS using the same host name, then there is no way of determining if an internal or external URL should be used.

One possible workaround is to have the internal URL access an Exchange Server 2003 back-end server directly. Even if more than one Exchange Server 2003 is in use, the client will be redirected to the correct server, and the IP address can be used to distinguish internal and external clients. This is described in more detail in Using an Exchange CAS Server (external only).

A second workaround is to introduce a second Exchange CAS, so that internal clients and external clients use different Exchange CAS servers. This is described in Using separate Exchange CAS Servers.

A third workaround is to create an additional virtual directory on the Exchange CAS and back-end servers. The firewall or proxy could then be configured to pass requests to the new virtual directory on the Exchange CAS, which in turn would forward it to the new virtual directory on the back-end server. The new virtual directory could then be specified in the "UseExternalWebAppURL" setting, so that requests using that virtual directory would trigger the external URL for Enterprise Vault, and requests for the exchange virtual directory would trigger the internal URL for Enterprise Vault.