cancel
Showing results for 
Search instead for 
Did you mean: 

Exchange 2010 OWA - Archive Explorer\Search Archive links not working

Richard_J_Cunni
Level 4

 

 

I have EV reverse proxied through an apache RP, opening vaulted items works fine both internally and externally. But the Archive Explorer\Search Archives buttons aren't working in OWA, it tries to point to the internal URL, even though in the policies in EV the external app is set to the external app.  
 
But if I try to access the below, these are the URLs it tries to point to, searcho2k doesn’t work at all, but AE works internally.
 
res://ieframe.dll/dnserror.htm#http://ukevsrv.uk.companyname.org/EnterpriseVault/ArchiveExplorerUI.asp?mbx=Richard.Cunningham@companyname.co.uk&server=UKBNEX01&OWA2007=1&Owa2007Url=https%3a%2f%2fwebmail.companyname.co.uk%2fowa%2f - works int, doesn't ext. AE
 
http://ukevsrv.uk.companyname.org/EnterpriseVault/Searcho2k.asp?vaultid=1FBAE6FC652319F43AFD4BD4046DD2C151110000ukevsrv&mbx=Richard.Cunningham@companyname.co.uk&server=UKBNEX01&usebrowserview=True&OWA2007=1&OWA2007Url=https%3a%2f%2fwebmail.companyname.co.uk%2fowa%2f - doesn't work int\ext, searcho2k
 
Any ideas on how I’d change these?
 
1 ACCEPTED SOLUTION

Accepted Solutions

ZeRoC00L
Level 6
Partner Accredited

When did you change/add that value ?
Did you run a synchronize mailboxes after changing the value ?

You can also check the web.config. There is also an option to enter the external url (EnterpriseVault_ExternalWebAppUrl).

http://www.symantec.com/business/support/index?page=content&id=TECH60712

View solution in original post

13 REPLIES 13

ZeRoC00L
Level 6
Partner Accredited

Configure the option: "External Web Application URL".

Go to:

Desktop Policy / Advanced Tab Select OWA from the drop down list

Setting you require is called External Web Application URL

Full details can be found here:-

http://www.symantec.com/business/support/index?page=content&id=TECH63250

Richard_J_Cunni
Level 4

Hi, this is set to http://webmail.companyname.co.uk/EnterpriseVault - which is the valid external URL for EV, http://ukevsrv.uk.companyname.org/EnterpriseVault/ is the internal address for EV.

ZeRoC00L
Level 6
Partner Accredited

When did you change/add that value ?
Did you run a synchronize mailboxes after changing the value ?

You can also check the web.config. There is also an option to enter the external url (EnterpriseVault_ExternalWebAppUrl).

http://www.symantec.com/business/support/index?page=content&id=TECH60712

Richard_J_Cunni
Level 4

I've had it in there for well over a week, I've sync'd my mailbox a few times, I even have the value in the web.config and it's still pulling up http://ukevsrv.uk.companyname.org/... instead of http://webmail.companyname.co.uk/...

ZeRoC00L
Level 6
Partner Accredited

Is http://webmail.companyname.co.uk/EnterpriseVault/Searcho2k.asp working from external ipadresses ?

BTW, what is your EV version ?

LCT
Level 6
Accredited Certified

By default, with OWA 2007 and OWA 2010 if you integrate EV and install the EV extensions on the CAS servers, ALL EV funtions should work as per normal, however the Search and Archive Explorer won't because they are now being redirected and connected directly to the EV server. This of course will be using the internal webappurl therefore from external location it won't be able to resolve.

You can configure the web.config and the Desktop Policy to force it to use the external webappurl (if you know what you are doing). I would suugest looking at this link and the install and config guide.

http://www.symantec.com/business/support/index?page=content&id=TECH63250

This will of course force the EV OWA connection to use the external webappurl and therefore will break your EV OWA internal connection, unless you are redirecting the internal connection to your firewall by reconfiguring your DNS etc.

Your best option is to use ISA/TMG to do the link translation i.e. tranlsate the internal webappurl to use external webappurl for only the external EV OWA connections.

LCT
Level 6
Accredited Certified

From external can you access the vault server by just putting using the this?

https://webmail.domain.com/enterprisevault

this shuld take to your vault server. if you can't acess this externally then it will not work. You need to configure your firewall to be able to access this first before doing anything else.

Could post your web.config please so we can check it?

Andrew_G_
Level 5
Employee Accredited

 

Do your users use a different hostname to connect to OWA internally?
 
If so, you should be able to specify the web.config setting "EnterpriseVault_ ExternalHostNames", using your external webmail name, i.e. from your example above "webmail.companyname.co.uk", assuming Apache RP isn't changing things. That way, your external users using "webmail.companyname.co.uk" will use the external EV url, and your internal users accessing OWA with the internal name "ukevsrv.uk.companyname.org"
 
Alternatively, you may be able to use the "EnterpriseVault_ExternalIPAddresses" web.config setting, using the IP address of the Apache RP Server.

Richard_J_Cunni
Level 4

Got it sorted, cheers for the pointers everyone, was a combo of the following commands:

 

EnterpriseVault_ExternalWebAppUrl = <https>/EnterpriseVault

EnterpriseVault_UseExternalWebAppUrl = true

 

Thanks

LCT
Level 6
Accredited Certified

Does it work internally too? just a matter of interest after the changes.

ZeRoC00L
Level 6
Partner Accredited

Glad the issue is resolved.

Sometimes it is hard to understand what exactly to enter in the command boxes/fields.

Andrew_G_
Level 5
Employee Accredited

So if users (internal or external) get to OWA using "https://webmail.company.co.uk/owa", then they will use "https://webmail.company.co.uk/enterprisevault" to get to search/archive explorer.

In other words, your internal users are probably now getting to EV through the Apache RP too.

LCT
Level 6
Accredited Certified

I suspect, the internal users, when they click on Serach or Archive Explorer they will be using the external webappurl, unless you have reconfigured your DNS internally for internal OWA, internal users will have opposite problem of external users now.