Video Screencast Help

Exchange 2010 and rpc\http evault

Created: 04 Oct 2012 • Updated: 04 Oct 2012 | 7 comments
This issue has been solved. See solution.

I'm using this artice http://www.symantec.com/business/support/index?page=content&id=TECH172662 to configure internet access to evault through rpc\http. Everything with exchange server and outllo are setup correctly with rpc\http and it works fine. I have also successfully published the evault server's name through the internet. I cant however still access evault email through the internet.

If I go to http://evautserver.domain.com/enterprisevault I can access the ev webapp, it doesnt ask me for credentials even!?

In the desktop policy I choose on th eadvanced tab "outlook" and I choose for rpc\http "direct" and synchronize my mailbox and open Outlook and cant open archoved email. If I choose "proxy" and put the url: "evaultserver.domain.local" - still cant get archived email. I can get it though if I use th evpn or if I'm internal.

Comments 7 CommentsJump to latest comment

JesusWept3's picture

So you need to use proxy and specify the full https://mail.yourDomain.com/EnterpriseVault/

Once that is set and synchronized, get a client trace and see what URL it's using and what the http response codes are

tolinrome1's picture

This is what I dont understand. How can I use mail.domain.com/enterprisevault when mail.domain.com poitns to my Exchange Server?

I already have an external URL being published called evaultserver.domain.com to the internal IP address of the evault server and it is accesssible from outside.

Are you saying in the properties of the Exchaneg policy I choose use proxy instead of direct and just type in the url as https://mail.domain.com/EnterpriseVault ?

Why URL would I put if I wanted to use direct?

JesusWept3's picture

Direct means that its not even going to try the RPC over HTTP URL
Meaning that if you have http://evserver.internal.domain/ then EV will always attempt to connect to that URL, so that you have to be connected to the VPN or logged on to your domain.

For external, typically you have something like

http://mail.myCompany.com (an ISA Server)
http://mail.myCompany.com/Exchange/ -> http://exchangeCAS.internal.domain/Exchange/
http://mail.myCompany.com/EnterpriseVault/ -> http://evServer.internal.domain/EnterpriseVault/

So the IIS does the redirect based on the published folders, it acts as a proxy between the Exchange virtual directory and outside the network.
 

if you have published it via something like
http://ev.myCompany.com -> http://evServer.internal.domain/
Then you would specify the RPC over HTTP URL to be http://ev.myCompany.com/EnterpriseVault/ and set the policy to use Proxy

SOLUTION
tolinrome1's picture

I have http://mail.myCompany.com/Exchange/ -> http://exchangeCAS.internal.domain/Exchange/

But I got it working by:

http://ev.myCompany.com -> http://evServer.internal.domain/
Then you would specify the RPC over HTTP URL to be http://ev.myCompany.com/EnterpriseVault/ and set the policy to use Proxy

Why is it http and not https? Through the internet I went to http://evaultserver.domain.com/enterprisevault and it didnt even ask me for a password.

JesusWept3's picture

http and https is purely your preference, if its set up to use both http AND https, you can use both...but you should probably set the urls and the listerns and forwarders etc to use https

As for the password prompt, it is most likely a managed password on your windows machine, so its just passing the credentials it already has cached

tolinrome1's picture

apparently it only works with http, how do I control which it uses?

JesusWept3's picture

here's one way of configuring EV to work with SSL
http://www.symantec.com/business/support/index?page=content&id=TECH128657