Forum Discussion

ItsRahulSingh's avatar
12 years ago
Solved

Vault Cache Synchronization failes if using RPC / HTTP in Exchange 2010 with "use proxy" set in the desktop policy

We had setup enterprise vault 10.0.4 CHF2 in our environment. We have different internal and external domain names. We had setup EV external access to https with a wild card certificate and RPC over Http connection to use proxy, proxy URL - https:// webev.domain.in/Enterprisevault. where as our internal default is mapped to server alias - evserver.domain.int. Internal EV access is working fine, while in external access only vault Synchronization is not working. I had analysed the things and found that Vault cache is connecting to http://evserver.domain.int/enterprisevault over the internet, even external wevapp url is set to https:// webev.domain.in/Enterprisevault for rpc connections. It would very appreciable if someone could provide me the solution. Regards Rahul Singh
  • If VC/VV are working well internally, it might be an issue with the firewall configuration. This is how the EV Outlook add-in works:

    The Enterprise Vault client contacts Enterprise Vault as follows:

    • The Enterprise Vault client first attempts to connect to the default Enterprise Vault server that hosts the archive.
    • If the client cannot contact the server, then the client uses the URL that you specify for the Enterprise Vault Exchange Desktop policy setting, RPC over HTTP proxy URL.
    • This logic enables users to connect directly to the Enterprise Vault server that hosts the archive when they are in the office. When they are away from the office, the Enterprise Vault client connects to the Enterprise Vault proxy server.
    • If no URL is specified in the Enterprise Vault policy, then the client uses the Exchange proxy URL configured in the Outlook profile.

    You should see in the client logs that the client is trying to connect to the internal name then to the external. Can you post the client log to take a look? Also, take a look at this TN:

    How to configure Enterprise Vault (EV) integration with Outlook Anywhere using Internet Security and Acceleration (ISA) Server 2006
    http://www.symantec.com/docs/TECH61472

    I hope this helps.

3 Replies

  • Hi,

    Do you have Outlook Anywhere enabled in the Outlook client?

  • If VC/VV are working well internally, it might be an issue with the firewall configuration. This is how the EV Outlook add-in works:

    The Enterprise Vault client contacts Enterprise Vault as follows:

    • The Enterprise Vault client first attempts to connect to the default Enterprise Vault server that hosts the archive.
    • If the client cannot contact the server, then the client uses the URL that you specify for the Enterprise Vault Exchange Desktop policy setting, RPC over HTTP proxy URL.
    • This logic enables users to connect directly to the Enterprise Vault server that hosts the archive when they are in the office. When they are away from the office, the Enterprise Vault client connects to the Enterprise Vault proxy server.
    • If no URL is specified in the Enterprise Vault policy, then the client uses the Exchange proxy URL configured in the Outlook profile.

    You should see in the client logs that the client is trying to connect to the internal name then to the external. Can you post the client log to take a look? Also, take a look at this TN:

    How to configure Enterprise Vault (EV) integration with Outlook Anywhere using Internet Security and Acceleration (ISA) Server 2006
    http://www.symantec.com/docs/TECH61472

    I hope this helps.