Enterprise Vault™ Configuring Internal and External WebApp URLs for OWA
- Configuring Internal and External WebApp URLs for OWA
- Overview
- How to define the external URL for Enterprise Vault
- Determining when to use the external URL for Enterprise Vault
- Load balancing
- Fault tolerance
- Customized shortcut links
- OWA configuration examples
Customized shortcut links
In the Enterprise Vault OWA 2003 Extensions, the links in customized shortcuts are translated by the OWA extensions to refer back to the Exchange Server. In the OWA 2007 and 2010 extensions, the links are not translated by the extensions. They are, however, translated by OWA to refer back to the Exchange Server, and the original link is added as a parameter. For this reason, normal link translation by a firewall or proxy may not work. However, Microsoft ISA 2006 is capable of translating the links as described in the following article:
http://technet.microsoft.com/library/bb794742.aspx
To ensure this works correctly:
There must be a "Computer" Network Object for the Enterprise Vault server that is being published.
The "This rule applies to this published site" value on the "To" page of the Enterprise Vault web publishing rule properties dialog must be the host value in the customized shortcut link.
Other firewall or proxy solutions may also be able to handle this translation.
Translating customized shortcut links is not discussed further in this document, as the links are intended for clients that are not integrated with Enterprise Vault, such as Outlook Express. In OWA clients, double-clicking the item will open the item, even if the customized shortcut link has not been translated correctly.