Forum Discussion

mayu's avatar
mayu
Level 4
12 years ago
Solved

Outlook RPC over HTTP and Outlook Anywhere configurations

Hi All,

EV 10.0.3/Exchange 2010

I go through the setting up exchange server archiving guide and found the following data

“With Outlook 2003 and later, users can access mailboxes using remote procedure call (RPC) over HTTP. With this protocol, MAPI is used to tunnel Outlook RPC requests inside an HTTP session. Using RPC over HTTP remote Outlook users can connect to Exchange Server mailboxes without the requirement for OWA or a virtual private network (VPN) connection.”

 

So my question is,

If you are not using Search and Archive Explorer externally via Outlook Anywhere then we don't need extra DNS? Just configure the Desktop policy to use the webmail address?

  • You still need to publish the EV Virtual directory for other EV operations to work from Outlook anywhere. Whatever you are saying is applicable to OWA external access, incase of OWA if you dont want AE and Search externally then there is no need to publish EV VD.

    In the same guide, if you look at the Figure shown for Exchange 2010, you will understand that all EV requests are direct to EV Server:

    The Enterprise Vault client contacts Enterprise Vault as follows:


    ■ By default, the client first attempts to contact the default Enterprise Vault
    server that hosts the archive.


    ■ If that is unavailable, the client uses the RPC overHTTPproxyURLconfigured
    in the Enterprise Vault Exchange Desktop policy.


    ■ If no URL is specified in the Enterprise Vault policy, then the client uses the
    Exchange proxy URL configured in the Outlook profile.


    With direct connections, all the Enterprise Vault servers that host the archives
    must be accessible to the internal and external clients. If you do not want to publish
    multiple Enterprise Vault servers to external clients, then you can use an
    Enterprise Vault server as a proxy server. A client connects to the Enterprise
    Vault proxy server, and the proxy server forwards the requests to the Enterprise
    Vault server that hosts the archive. 

3 Replies

  • i believe the answer to your question is yes but just to be certain, can you clarify what you mean by "extra" DNS?

  • Sorry

    I want to say that do we need to publish EV virtual directory If we are not using Search and Archive Explorer externally via Outlook Anywhere

  • You still need to publish the EV Virtual directory for other EV operations to work from Outlook anywhere. Whatever you are saying is applicable to OWA external access, incase of OWA if you dont want AE and Search externally then there is no need to publish EV VD.

    In the same guide, if you look at the Figure shown for Exchange 2010, you will understand that all EV requests are direct to EV Server:

    The Enterprise Vault client contacts Enterprise Vault as follows:


    ■ By default, the client first attempts to contact the default Enterprise Vault
    server that hosts the archive.


    ■ If that is unavailable, the client uses the RPC overHTTPproxyURLconfigured
    in the Enterprise Vault Exchange Desktop policy.


    ■ If no URL is specified in the Enterprise Vault policy, then the client uses the
    Exchange proxy URL configured in the Outlook profile.


    With direct connections, all the Enterprise Vault servers that host the archives
    must be accessible to the internal and external clients. If you do not want to publish
    multiple Enterprise Vault servers to external clients, then you can use an
    Enterprise Vault server as a proxy server. A client connects to the Enterprise
    Vault proxy server, and the proxy server forwards the requests to the Enterprise
    Vault server that hosts the archive.