Forum Discussion

Joe_S's avatar
Joe_S
Level 2
14 years ago

What is the minimum EV Client Version required for EVault 9.0 Proxy Server?

Hello,

My question is a repeat of the title.

I'm trying to determine the minimum EVault Client version to be added as an addin to Outlook (2003, 2007, 2010) to be able to connect to / through Enterprise Vault Server 9.0 Enterprise Vault Proxy Server for Outlook Anywhere (RPC over HTTPS) from the Internet?

I have the system behind TMG 2010 as well but I'm specifically looking to find what the minimum version client is required.

 

EV Client 8.0.3 and above seems to be synchronizing Vault Cache content no problem.

 

EV Client 8.0.1 seems to start trying to synchronize content but then the Content Synchronization goes to a Failded: download failed

but if you leave it alone for a while it will try and keep downloading some items into the cache. The number of items to download doesn't seem to be coming down any and it is definitely reaching a point and hanging its not downloading all the items into cache.

 

Thanks

Joe S.

  • Technically there is no such thing as an Enterprise Vault Proxy Server, there is the /EnterpriseVaultProxy/ virtual directory that sits on the OWA Front end servers, but was replaced with having the /EnterpriseVault virtual directory on the EV server being published directly to the web.

    The EnterpriseVaultProxy just featured a custom 404 page that redirected client requests back to the original EV Server....

    So you would go to something like
    http://mail.yourcompany.com/EnterpriseVaultProxy/search.asp

    This would generate a 404 page not found error (because search.asp does not exist in the proxy directory) and would actually send the request back to the EV server

    So http://mail.yourcompany.com/EnterpriseVaultProxy/search.asp would forward to http://evserver.internaldomain.com/EnterpriseVault/search.asp

    So on the Enterprise Vault policy side of things, you would configure your RPC over HTTP URL in the desktop policy to point at either http://mail.yourcompany.com/EnterpriseVaultProxy/ so that it would do its commands there (such as download.asp etc)....

    Or the preference for just publishing the /EnterpriseVault/ website off of the EV server, means you would configure it to go straight to http://mail.yourcompany.com/EnterpriseVault/ and ISA would redirect all the requests to the back end.

    Now as for your issue with EV 8 SP1 failing to synchronize but EV8 SP3 works fine, then I would just try going with the latest client, especially if you want to use Virtual Vault which does not exist in the EV8 SP1 client and pkus theres been hundreds of fixes (even with EV9 SP2 out there are still fixes coming down the pipe line)

    Also note that even if you have Outlook Anywhere enabled and you have set the proxy up properly and your policy is also configured correctlly, if Enterprise Vault client determines that it has a direct path to the EV server (i.e. its connected to a VPN or its conected to the local network) then EV will just connect directly and bypass the RPC over HTTP url altogether

6 Replies

  • for Outlook 2010 you have to have Enterprise Vault 9 SP1+ HTTP Only client against EV8 SP4 minimum

    For the rest check out
    http://www.symantec.com/business/support/index?page=content&id=TECH38537

    Page 9 for what EV client will work against what version of EV server
    Page 39 for what EV Client will work against what Operating System
    Page 41 for what EV Client will work against what version of Outlook

  • Hi,

     

    Thanks for that. I've actually already looked at it my problem is it does not give detailed information as to which Version 8 evault client works properly with EV Proxy Server for Outlook Anywhere connections with Enterprise Vault Server 9.0

     

    In my testing EV Client 8.0.1 tries and works sometimes but then fails and keeps having problems where EV client 8.0.3 seems to be working fine.

     

    EV client 9.0.1 and 9.0.2 are only http only clients unless something new has come out that is a full client.

    thanks for your reply / assistance.

    Joe S.

  • Every version of EV since as long as i can remember has had both a full client and a lite client

  • oh and all of them support RPC over HTTP or Outlook Anywhere as long as the EV Server policy is configured along with Exchange being properly configured

  • I'm trying to determine the minimum EVault Client version to be added as an addin to Outlook (2003, 2007, 2010) to be able to connect to / through Enterprise Vault Server 9.0 Enterprise Vault Proxy Server. Enterprise Vault Proxy Server is a new feature in enterprise vault server 9.0

     

    I'm not sure if you are understanding my question / scenario.

  • Technically there is no such thing as an Enterprise Vault Proxy Server, there is the /EnterpriseVaultProxy/ virtual directory that sits on the OWA Front end servers, but was replaced with having the /EnterpriseVault virtual directory on the EV server being published directly to the web.

    The EnterpriseVaultProxy just featured a custom 404 page that redirected client requests back to the original EV Server....

    So you would go to something like
    http://mail.yourcompany.com/EnterpriseVaultProxy/search.asp

    This would generate a 404 page not found error (because search.asp does not exist in the proxy directory) and would actually send the request back to the EV server

    So http://mail.yourcompany.com/EnterpriseVaultProxy/search.asp would forward to http://evserver.internaldomain.com/EnterpriseVault/search.asp

    So on the Enterprise Vault policy side of things, you would configure your RPC over HTTP URL in the desktop policy to point at either http://mail.yourcompany.com/EnterpriseVaultProxy/ so that it would do its commands there (such as download.asp etc)....

    Or the preference for just publishing the /EnterpriseVault/ website off of the EV server, means you would configure it to go straight to http://mail.yourcompany.com/EnterpriseVault/ and ISA would redirect all the requests to the back end.

    Now as for your issue with EV 8 SP1 failing to synchronize but EV8 SP3 works fine, then I would just try going with the latest client, especially if you want to use Virtual Vault which does not exist in the EV8 SP1 client and pkus theres been hundreds of fixes (even with EV9 SP2 out there are still fixes coming down the pipe line)

    Also note that even if you have Outlook Anywhere enabled and you have set the proxy up properly and your policy is also configured correctlly, if Enterprise Vault client determines that it has a direct path to the EV server (i.e. its connected to a VPN or its conected to the local network) then EV will just connect directly and bypass the RPC over HTTP url altogether