Forum Discussion

DanJ71's avatar
DanJ71
Level 3
8 years ago

RPC over HTTP Proxy URL

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?

  • Hi Dan,

    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.

    • DanJ71's avatar
      DanJ71
      Level 3

      I don't appear to have that setting in my desktop policy - on EV 12.0.3.1095

      Is that a new setting?  This thing started with EV10 and has been subsequently upgraded over time.

    • DanJ71's avatar
      DanJ71
      Level 3

      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.

      • Marcde's avatar
        Marcde
        Moderator

        Hi DanJ71,

        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

        https://www.veritas.com/support/en_US/article.000108366 

         

        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.