The RPC over HTTP(s) Export Tool is designed to pull data from the remote Exchange server. Data exported from the remote server is then imported into Smarsh Hosted Services mailboxes. The process is seamless for end-users.

In order for you to use the tool, we need the following information:

1. FQDN of the back-end Exchange server (the source to pull mailbox data from).

2. RPC HTTP Server URL (typically the Outlook Web Access URL).

Make sure SSL certificate is valid for the period of the migration.

If RPC over HTTP (Outlook Anywhere) is not enabled, the network administrator should adjust firewall settings to allow connections from the Smarsh Hosted Services IP address for ALL ports.

Read the Knowledge Base article on Requirements For Direct MAPI Export Tool for more information.

3. List of UserPrincipalName (UPN's) and sAMAccountName attributes for mailboxes to pull.

Make sure that:

  • Users are not hidden from the Exchange Global Address List.
  • All users have mailboxes enabled for MAPI. Sometimes users will be enabled for OWA but not for MAPI.

Provide the format that is used to log in to Outlook: username, domain/username or email address.

4. Exmerge credentials or a list of passwords with matching mailboxes.

Read the Knowledge Base article on How To Create An Exmerge User for the instructions.

ExMerge users must have: 

  • Exchange View-Only Server Administrator role.
  • Receive As extended rights. You may use the Add-ADPermission command in Exchange Management Shell. Examples:
    • Setting Receive-As permissions at the server level:
      >>Get-MailboxServer -Identity 'server_name' | Add-ADPermission -User 'exmerge_user_UPN' -ExtendedRights Receive-As
    • Setting Receive-As permissions at the Organizational Unit level:
      >>Get-Mailbox -OrganizationalUnit 'OU_name' | Add-ADPermission -User 'exmerge_user_UPN' -ExtendedRights Receive-As
  • Full Access set of permissions for all mailboxes that we need to pull data from (you may use the Set-MailboxPermission command).
    Note: We do not require administrative credentials to log in to a remote Exchange server and cannot use them for this task (for security and liability reasons).

Alternatively, you can provide a list of passwords with matching mailboxes.

5. NTLM or Basic authentication.

To collect FQDN of the back-end Exchange server and RPC HTTP Server URL in the Outlook profile (applies for Outlook 2013 and earlier):

  1. In Outlook, navigate to File (Tools) > Account Settings.
  2. Double-click the Exchange account, then click the More Settings button.
  3. FQDN of the back-end Exchange server is available in Server field.
    FQDN
  4. Click the Connection tab and click the Exchange Proxy Settings button.
  5. RPC HTTP Server URL and Authentication settings are available in Exchange Proxy Settings window.
    Connection settings

To collect FQDN of the back-end Exchange server in the Outlook Web App:

For Exchange 2010 and earlier:

  1. Navigate to Options > About
  2. Find Exchange Client Access server name

For Exchange 2013 and later:

  1. Change the OWA version to light mode.
    Read the Knowledge Base article on How Do I Access OWA Light Version? for instructions.
    Or type in the OWA URL https://YourExchangeServer/owa/?layout=light where YourExchangeServer is your Proxy Exchange Server.
  2. Navigate to Options > About
  3. Find Exchange Client Access server name

OWA