EV 8.0 SP2 - "External Web Application URL"-policy setting not working ?
Hello all,
We have recently implemented EV8.0.2 in an exchange 2007 (with OWA2007) environment.
The OWA2007 is being published through ISA2006.
Internally, everything is working fine.
Externally though, starting the Archive Explorer, I am redirected to the archive explorers web application internal URL.
e.g.
Internally : CAS server = exch.domain.local, EV server = entvault.domain.local
Externally : CAS server = owa.domain.com
Opening OWA2007 from an internet PC (browsing to https://owa.domain.com/) works perfectly. Opening Archive Explorer from there redirects me to server 'entvault.domain.local' (which is not working, obviously).
Fortunately, EV's desktop policy settings contain an entry for OWA that defines the name of the "External Web Application URL".
This should contain the URL that you want to be redirected to, when starting Archive Explorer externally.
In my extensive testing, I can only conclude that this policy setting is not applied. Whatever URL (or anything for that matter) I put in this field, I am always redirected to the internal URL.
Other policy settings are immediately (after synchronisation) applied, and seem to work fine.
What am I missing ?
Thanks a lot for all your assistance
Comments
<add
<add key="EnterpriseVault_ExternalWebAppUrl" value="https://externalURL/Enterprisevault
In the web.config file on the CAS server in c:\Program Files\Microsoft\Exchsrvr\OWA (if I recall correctly) what is the above line set to? This file will overide policy settings and to be honest I use this rather than the policy setting in EV.
Alsoare you using the internal or external URL for OWA internally? This will aslo affect the settings you need to use.
Not sure if you have seent his but you may find it useful. Look specifxally at the example configurations at the end.
ftp://exftpp.symantec.com/pub/support/products/Exchange_Mailbox_Archiving_Unit/308450.pdf
Desktop Policy not being applied properly
Hello Don,
Thanks for this speedy reaction.
I tried to solve the issue by adding the <add key=....> line in the web.config file on the CAS server. But this did not seem to make any difference, so I removed it.
To be absolutely sure, I just gave it another shot, but alas, no result. I am still being redirected to the internal URL.
I had already come across the document you refer to. But now, I will review it with some more care.
Perhaps it is a language issue ? The OWA is shown in Dutch, not in English. I know it's a long shot, but I am nearly at my wits end...
Best regards,
Peter
Should not be language, you
Should not be language, you probably need the external hostname in the web.config. This is shown in the examples so see which one best suites and let me know if you have any questions.
Mistery solved.
Hello Don,
After some more thorough troubleshooting, the answer indeed lies in the Web.config file on the CAS server.
Before Archive Explorer can direct you to the correct (external) URL, the system needs a way to determine that you are actually connecting from an external source.
In order to correctly determine this, the following entry in web.config proves crucial :
<add key="EnterpriseVault_ExternalHostNames" value="owa.company.com"/>
where owa.company.com is the external servername of your OWA server.
By default, this entry is not present. After adding it manually, everything seemed to be working fine.
Thanks a lot for your help.
No problem, glad to be of
No problem, glad to be of help. i thought it would be the the externalhostnames.
Would you like to reply?
Login or Register to post your comment.