Accessing Enterprise vault archived emails through UAG
I recently worked on a case where the issue was that users could not access Enterprise vault archived emails in OWA Published through UAG. Enterprise Vault is an email archiving software from Symantec and is used as an add on with OWA to access archived emails. Since it is used along with OWA, which we publish through UAG, we also need to configure UAG to allow access to the Enterprise Vault URLs.
Scenario: The admin has configured UAG to publish OWA. He was also trying to publish Enterprise Vault through UAG to access archived emails along with OWA. However, archived emails were not showing up properly, the image hyperlinks for it were not showing and archived emails were inaccessible.
Troubleshooting Approach and Resolution
1. In order to troubleshoot this, we reproduced the issue on a client machine, and then looked at the web monitor logs on the UAG server. This is what we found
“ A request from source IP address 18.9.7.2, user test2 on trunk portal; Secure=1 for application Exchange 2010 OWA of type ExchangePub2010 failed. The URL /owa/EnterpriseVault/Exch2010/v9.0.1.1073/scripts/xyz.js contains an illegal path. The rule applied is Default rule. The method is GET.”
2. We checked the Advanced Trunk configuration and the URL set, and found following in the EnterpriseVault rule, which was created by the customer:
i.e. the path /enterprisevault/.* was not correct , as the request in the web monitor log had the path of “ /owa/EnterpriseVault/…” . This means we need to add /owa before /EnterpriseVault/.*
Apart from that we also needed to change the name of the rule. 1st, it needs to be named after the Exchange applications convention (ExchangePub2010_RuleXX), and 2nd, have a high number so that it does not get overwritten by UAG if the default rule-set changes. We changed our rule to ExchangePub2010 _Rule99, and access to Enterprise Vault was successful.
More about Rule name definition
A URL Set rule has two parts:
a. Application: This is to define the application for which this rule is configured. UAG looks for the URL throughout the URL Set rules, and will determine the application type based on that match. If the Rule name does not match any existing application type, UAG will not know what to do. In this case, it is ExchangePub2010_Rule99
b. Rule(number) : Keyword Rule along with number. By default ExchangePub2010 has 42 rules, so in order to make sure this rule is not overwritten with future updates of UAG, I used a large number (i.e. 99) and the resulting rule name is ExchangePub2010_Rule99
Blog post written by Suraj Singh