I have implemented EV 12.0.1 to archive email in an Exchange 2013 scenario. Most end users use Outlook 2016. When a user is outside the corporate network the Vault add-in does not detect RPC over HTTP is enabled even though Outlook Anywhere is in use, and so the HTTP connection to the internal alias FQDN fails.
Current config:
Ev client log: RPC over HTTP is not enabled (flags =0)
Add-in Information: HTTP connection failed: http://evserver1.internaldomain.local/EnterpriseVault (Status: 0x12)
Desktop policy settings:
- RPC over HTTP connection: Use proxy
- RPC over HTTP Proxy URL: HTTPS://vault.publicdomain.com/EnterpriseVault
- RPC over HTTP restricitons: Disable PST Import
- Use proxy settings: Ignore proxy settings
Please assist.
In Outlook 2016 i cannot configure RPC over HTTP proxy settings. Is there a way i can force the add-in to assume RPC over HTTP is being used?
