Ensuring successful MAPI connections

If you use Exchange Server 2013, use the MAPI Settings property page to verify that the user mailbox is online. You can also view and update the MAPI registry key that enables IBM Storage Protect Snapshot to connect to the Exchange Server.

Ensure that the correct version of Microsoft Exchange Server MAPI Client and Collaboration Data Objects is installed on the Exchange Server. The correct version is identified in the Hardware and Software Requirements technote that is associated with the level of your software. For mailbox restore operations to succeed in Exchange Server 2013 environments, the MAPI client must use Remote Procedure Call over HTTPS (RPC over HTTPS), also known as Outlook Anywhere. You cannot use RPC over TCP.

1. From Microsoft Management Console (MMC), select an Exchange Server instance.
2. On the Protect tab, click Properties in the Action pane.
3. Select MAPI Settings from the list of property pages.
4. Verify that the following information is correct in the Exchange Server environment:
   • The mailbox alias field shows the mailbox that you are logged in to. Verify that you can open the mailbox in Microsoft Outlook or Outlook Web Access (OWA).
   • The Exchange Profile Server field shows the correct mailbox endpoint on the Exchange Server that has the Client Access Server (CAS) role. Verify that you can open the target mailbox in Outlook or OWA.
5. Edit the registry key only if the default value is incorrect. Use one of the following methods.
   • Enter the registry key value in the RpcHttpProxyMap_TSM field.
   • Enter the Domain field value and select or clear the Use HTTPS authentication check box. When you change either of these values, the values of the registry key automatically updates in the RpcHttpProxyMap_TSM field.
   Consider that the values that you enter override the registry key that is in the HKEY_CURRENT_USER\Software\Microsoft\Windows NT\Current Version\Windows Messaging Subsystem directory. If you modify the registry incorrectly, the connection to the Exchange Server might fail.

   RpcHttpProxyMap_TSM

   Change the registry key values to reflect the correct domain, endpoint, and Remote Procedure Call (RPC) authentication methods for your environment. By default, the following format is used.

   Domain=Proxy Server,RpcHttpAuthenticationMethod,
   RpcAuthenticationMethod,IgnoreSslCert

   For example:

   companyname.local=https://exchange.companyname.com,ntlm,ntlm,false

   where:

   • Domain value is the domain suffix of the personalized server ID, for example, companyname.local. Specify any domain or a substring of a domain, or the asterisk (*) and question mark (?) wildcard characters, for example, *.companyname.local.
   • Proxy Server value is the RPC proxy server that has the Client Access Server (CAS) role. Specify the fully qualified domain name (FQDN) of the RPC proxy server. Precede the FQDN by http:// for an HTTP connection, or https:// for an HTTPS connection. For example, https://exchange.companyname.com
   • RpcHttpAuthenticationMethod value is the method that is used to authenticate RPC-over-HTTP connections. Specify NTLM, Basic, Negotiate, or WinNT.
   • RpcAuthenticationMethod value is the method that is used to authenticate RPC-over-TCP connections. Specify NTLM, Negotiate, WinNT, Anonymous, or None.
   • IgnoreSslCert value indicates whether the Exchange Server validates SSL certificates. For the Exchange Server to ignore invalid certificates, specify False.

   Domain

   Change the domain name to reflect the correct domain if for example, you have multiple domains, or the default domain value is incorrect. To match all domains, enter the asterisk (*) wildcard character. When you change this domain value, the Domain value of the registry key automatically updates in the RpcHttpProxyMap_TSM field.

   Use HTTPS authentication

   Select this check box if RPC-over-HTTPS is enabled for the Exchange Server that is hosting the MAPI profile. Otherwise, clear this check box to ensure that HTTP authentication is used for RPC-over-HTTP connections. When you change this authentication value, the RpcAuthenticationMethod value of the registry key automatically updates in the RpcHttpProxyMap_TSM field.