MAPI is a supported connection type to provide connectivity to Exchange 2003. Clients who have upgraded their on-premises Exchange to Exchange 2007 or higher should
switch to using a Riva EWS connection.
Clients can contact the Riva Success Team
to schedule a no-cost support call to make that change to their Riva On-Premise server. You need to complete this activity before
upgrading to Exchange 2013 or migrating to Office 365 Exchange Online.
The purpose of this article is to describe how to prepare for a Riva connection to Exchange using Exchange Messaging API (MAPI) configured for Outlook Profile access.
Riva On-Premise supports connections to hosted and on-premises Exchange systems. If your Riva On-Premise server is not connecting to Exchange on-premises using MAPI, refer to the applicable article to prepare for one of the following messaging environments:
Supported Exchange on-premises systems: Riva Outlook Profile MAPI connections can be used for the following certified Exchange systems:
To prepare to connect to Exchange on-premises:
- Prepare the Windows system hosting the Riva On-Premise server.
- Prepare an Exchange service account for the Riva connection.
- Prepare the user mailboxes that Riva On-Premise will sync.
Step 1: Prepare the Windows System Hosting the Riva Server
DO NOT install Riva on an Exchange server if a MAPI connection will be used to connect Riva to Exchange. For MAPI connections, Riva requires an Outlook client be installed and Microsoft does not recommend installing Outlook on an Exchange server.
Confirm that the following has been completed:
- A 32-bit version of the Outlook must be installed. Because Riva is a 32-bit application, it needs to work with a 32-bit version of Outlook even if it is installed on a 64-bit Windows system. For more information, see MAPI initialization error: System.Runtime.InteropServices.COMException (0x80004005).
- An Outlook profile for the Riva connection account to Exchange is required.
- Ensure that local Windows and corporate firewalls are configured to grant the Riva server RPC over HTTP (Outlook Anywhere) MAPI access to and from the Exchange CAS (ports 80 and 443). See Firewall settings for Riva.
Step 2: Prepare the Riva Connection Account for Exchange
Riva On-Premise uses a single connection to Exchange on-premises to access the user mailboxes. That connection must be configured with the credentials of an Exchange service user account mailbox that has been assigned permissions to impersonate into the user mailboxes that Riva will sync. During each sync cycle, Riva will connect to Exchange and then access each user mailbox that is assigned to an enabled Riva sync policy. The Exchange service user account is referred to as the Riva connection user.
To prepare the Riva connection user:
Select an existing Exchange service user account mailbox, or create an AD/Exchange user (for example, svc_rivasync). For logon credentials, ensure that you know the Active Directory user name in one of the following formats:
Note: If a password change policy forces credentials to expire, ensure that the credentials are updated in Riva at the same time.
the UPN (universal principal name): ADusername@AD_Domain_Name, for example firstname.lastname@example.org, or
the SAM username: AD_Domain_Name\ADusername, for example MYCOMPANY\svc_rivasync, and
the logon password.
Configure this user as a fully enabled Exchange mailbox user that is visible on the Exchange Global Access List (GAL).
Exclude this account from the Domain Admins group.
Assign delegate full access permissions in Exchange from target user mailboxes to the Exchange service user mailbox to enable impersonation access to user mailboxes that Riva will sync. (Note: Exchange "ApplicationImpersonation Role permissions" are not supported.)
Test access to the mailboxes to be synced by the Riva connection user.
Step 3: Prepare the Target User Exchange Accounts
For each target user, Riva requires several key actions to be completed:
First Log on to Exchange: Users for each target Exchange account that will synchronize to the CRM must use Outlook to log in to their Exchange account at least once. This ensures that the required folders are created in the target user mailboxes.
Primary SMTP Email Address: The primary SMTP email address value in Exchange must match the primary email address value for the corresponding CRM account.
Global Access List: The target user mailbox must be visible in the Global Access List (GAL). If Exchange-enabled groups will be used to add mailboxes to the sync policy, the group must also be visible in the GAL.