EV, OWA and Archive Explorer/Search Archives
Hello,
I'm having some issues with Archive Explorer and the Search Archive functions in OWA/RPC-HTTP mode.
Environment is Exchange 2007 server running both CAS and Mailbox Role, as well as an EV 2007 SP3 Server.
EV Extensions have been installed on the Exchange Server, and the owauser.wsf script has been run, both successfully.
The problem I'm having, is with running Archive Explorer and Search Archive functionsin OWA and using Outlook Anywhere.
When pressing "Archive Explorer" in OWA, a new browser window opens, and tries to fetch the Archive Explorer UI using "http://server" as the URL. Obviously, this won't work, as "http://server" is not accessible over the internet. I may be gravely confused here (and if so, please feel free to correct me), but I thought EV was supposed to be able to "forward" the requests from the OWA to the EV server, without having to publish the EV web app in the firewall. Viewing archived messages and attachments works just fine using OWA and RPC, so there must be some sort of forwarding going on.
I've gone through the Exchange mailbox policy settings, especially the "client connection" settings, but the docs state that OWA 2007 and Outlook Anywhere only use a direct connection anyhow, and will disregard any proxy settings.
So, I guess my question is this:
Is it necessary to publish the EV web app in order to achieve access to Archive Explorer and Searchi Archives, or is there some config setting I am missing that would allow these utilities to function without publish the EV webapp in the firewall?
Yes
Check out page 219 on the install config guide.
If clients connect through a Microsoft ISA Server, then you will need to publish
to clients the OWA site on the Exchange 2007 CAS server and the Enterprise Vault
Web Access application.
Dear sleddog,
I am facing the same problem now.
If there is only sonicwall firewall using in existing environment, how can I solve this issue?
Please advice. Thanks!
Cheers,
Jason
At present, due to the change in how Exch 2007 works with OWA, you have to have your internal URL publicly contactable. EV now needs a direct connection from the external world, as opposed to Exch 2003 where we would proxy the request.
I think this is being looked at internally, but for now you need to be able to resolve the URL externally.
Would you like to reply?
Login or Register to post your comment.