The same services that MAPI is reliant upon also need to be functioning properly for Exchange Web Services so I don't see their being a tremendous difference in the availability of one over the other. You could alternatively use the POP3 or IMAP User Experience Monitors as they are also fairly simple and straightforward to configure. You can also continue to use the MAPI User Experience Monitor following the steps outlined in the MAPI troubleshooting section of the Administrators Guide. I was only trying to propose simpler options. Also note that the Orion server must be joined to the same Windows Domain as the Exchange server for the MAPI User Experience Monitor to function properly and the user account specified within the MAPI User Experience Monitor must have permissions to log into the Orion server itself. These are the two most common areas where people get hung up.
Troubleshooting MAPI
The following procedures will help you troubleshoot MAPI issues relating to SAM:
Note: Do not use the same mailbox for multiple MAPI UX monitors. Doing so can cause the MAPI monitor to intermittently fail.
MAPI Probe Diagnostic Checklist
Install CDO or Outlook
- CDO can be found here: http://www.microsoft.com/download/en/details.aspx?id=1004. If you would like to install CDO, uninstall your entire MS Office installation. Uninstalling Outlook only is not sufficient.
- The MAPI probe may be unstable when running with Outlook installed. If this is the case, uninstall Office then download and install CDO.
Check the MAPI profile
- The Orion Server is in the same domain as the Exchange server being monitored
- The user account used to monitor the mailbox with SAM has permission to login to the server console and has done so at least once.
- The user account to monitor the mailbox with SAM is in the local administrator user group of the server where SAM is installed
- MAPI component is using the FQDN for the domain account.
- The MAPI profile does not need to exist. The probe should create it and also update the existing profile with the required settings. However, there may be issues with an existing or created profile. The default Outlook profile is called Outlook.
- If this profile does not work, create a profile with the MFCMapi free tool, availabe at: http://mfcmapi.codeplex.com/.
- In the MFCMapi tool, navigate to Profile > Advanced Profile > Launch Profile Wizard, keeping the defaults on the first dialog.
- Set the profile as default.
- Update the profile name of the newly created profile in the MAPI probe.
- Use MFCMapi to find the profile name: Navigate to Profile > Show Profiles for verification.
Check probe settings
- Check that Send Email To: is correctly filled out in the component settings.
- The Mapi Profile Name must match the actual profile name. Use the MFCMapi tool if you are not sure about the name.
- Credentials used for the probe must be eligible to open the mailbox. It is required to add the user to the local Administrators group, otherwise the probe can fail with insufficient privileges.
Mailbox recommendations
- Use a clean mailbox created for monitoring purposes. A mailbox full of email is problematic as it takes a lot more time for the probe to search through all of the emails. The MAPI probe deletes obsolete, undeleted messages sent by the probe in the past to keep the mailbox clean.