Setting up a Enterprise Vault Outlook anywhere configuration
HI all,
I'm trying to get some information on setting up a Http over RPC/Outlook anywhere configuration with Enterprise Vault and i need help verifying some assumptions
As i know it, we have 2 options:
- We can configure a direct connect.
For this we will need to configure our firewall to allow access to our enterprise vault server from outside the network. We'll also need a external ip address and DNS name. Is there any else we'll need to do here? Do we need a TMG or proxy server to make this work? - We can configure a enterprise vault proxy server.
For this we'll need to install another enterprise vault server with a minimal amount of services running. We'll allso need to configure anonymous connections to the mail EV server
Thanks for any guidance on this issue.
The topic of an Enterprise Vault Proxy Server came from an OWA set up guide knocking around, its just a bit confused in terminology unfortunately.
What they really mean is you have a single point of entry
So you may have something like
evServer1.internal.com
evServer2.internal.com
evServer3.internal.com
You have to publish the /EnterpriseVault/ virtual directory, but rather than publishing all three servers directories, you just publish one server, and all requests will be handled through which ever server that you publish.
Typically most people just hijack the DNS and listeners that OWA already uses.
So a lot of companies have an alias such as 'https://mail.myCompany.com/'
They then have the /Exchange/ and /OWA/ directories published pointing at a load balancer.
i.e.
https://mail.myCompany.com/Exchange/ -> ISA/TMGServer -> https://casServer.internal.com/Exchange/and with EV you would publish /EnterpriseVault/ to point to http://evserver1.internal.com/EnterpriseVault/
i.e
https://mail.myCompany.com/EnterpriseVault/ -> ISA -> http://evServer1.internal.com/EnterpriseVault/So again, this is where the "proxy" comes in to play, a users archive maybe located on evServer2 or evServer3, but the published directory is pointing at evServer1 and that will just pass the requests to the other servers and retrieve the contents