07-05-2017 01:57 PM
I had a user with Win7/Outlook 2013 working offsite with no problems getting their archived email to come up. Helpdesk sent out a WIn10/Outlook 2016 setup and it doesn't appear to honor the RPC over HTTP Proxy URL anymore or for whatever reason it thinks it is on the local network. EV 12 client/EV12 server. Opening archived email gives errors and the search vaults also yields errors as it is looking for https://servername instead of https://servername.f.q.d.n
Any hints on how to get around this?
07-05-2017 10:49 PM - edited 07-05-2017 10:50 PM
Check on on Exchange Desktop policy - Outlook settings, verify that the Alternate Web Application URL and make sure it is set to the external EV URL. See attached screenshot.
07-06-2017 06:09 AM
I don't appear to have that setting in my desktop policy - on EV 220.127.116.115
Is that a new setting? This thing started with EV10 and has been subsequently upgraded over time.
07-06-2017 06:22 AM
The description for the setting on my setup is "RPC Over HTTP Proxy URL" and the little description at the bottom says [RPCOverHTTPProxyURL] which appears to be the same setting.
Using split-brain DNS and the internal name is the same as the external name. Since the DNS suffix is the same it looks like it is trying to reach it without the suffix. It does resolve to the right IP address but it complains about a certificate mismatch when you hit the "search vaults" within the EV add-in...perhaps this is the issue?
That being said, the OfficeMailApp doesn't work on this setup either although it does for WIn7 machines.
07-06-2017 11:22 PM - edited 07-06-2017 11:24 PM
we observed this as well with Outlook 2016 as OL16 does not set a flag which EV relies on the recognize rpc over http. This should be fixed in 12.1.
Unable to perform EV operations when outlook 2016 connects to Exchange 2010 via RPC over HTTP/S profile
Note that we observed this not only with Exchange 2010. Exchange 2013 was affected as well. It should be enough to use the 12.1 add-in to get this fixed.
07-07-2017 11:40 AM
Seems like I am fighting three issues here - the one you mentioned and two more.
The OfficeMail app has its own issues which I don't need to discuss here...
Even with the 12.1 client it still doesn't work if the proxy URL has the same name as the internal alias. Lucky for me we are using a wildcard certificate and I created an alternate name on our outside DNS servers and used a test policy with the new name and voila it works as expected.
I'm just taking your word (and the article) that the EV client needs to be upgraded to 12.1 for it to work.
07-08-2017 04:21 AM - edited 07-08-2017 04:22 AM
Sorry for delays on this.
The "RPC Over HTTP Proxy URL" has been removed from the Desktop policy starting with EV 12.1.
Can you confirm you set this in the Desktop policy: "RPC Over HTTP Proxy URL=https:/external-ev-url.fqdn/enterprisevault"?
07-10-2017 10:13 AM
I'm still on 12.0.x on the server side - I'm guessing that description will change when I upgrade.
The addition of an alternate DNS name that doesn't match the internal name in combination with the EV12.1 client (though I can't find the LATEST EV client to download under licensing...) has fixed my problem.