User MAPI connectivity Test

If MAPI connectivity to a user mailbox is unavailable, then that user may not be able to logon to that mailbox to send/receive mails. This is why, it is important that administrators periodically verify whether/not MAPI connectivity to a user mailbox is available. This check is now possible, thanks to the User MAPI Connectivity Test.

This test emulates a user attempting to login to his/her mailbox and retrieving a list of items in the Inbox. In the process, the test reports whether/not MAPI connectivity to that mailbox is available. If the MAPI connectivity is available, then the measure additionally reports how much time it took for the user to connect to that mailbox. This way, the test promptly alerts administrators to the unavailability of MAPI connectivity and latencies in MAPI connection to a configured user mailbox.

Target of the test : Exchange Online

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the Office 365 tenant being monitored

Configurable parameters for the test

Parameters Description

Test period

How often should the test be executed

Host

The host for which the test is to be configured. By default, this is portal.office.com

O365 User Name, O365 Password, and Confirm Password

For execution, this test requires the privileges of an O365 user who is vested with the View-Only Audit Logs, View-Only Recipients, Mail Recipients, and Mail Import Export permissions. Configure the credentials of such a user against O365 User Name and O365 Password text boxes. Confirm the password by retyping it in the Confirm Password text box.

While you can use the credentials of any existing O365 user with the afore-said privileges, it is recommended that you create a special user for monitoring purposes using the Office 365 portal and use the credentials of that user here. To know how to create a new user using the Office 365 portal and assign the required privileges to that user, refer to Creating a New User in the Office 365 Portal.

Domain, Domain User Name, Domain Password, and Confirm Password

These parameters are applicable only if the eG agent needs to communicate with the Office 365 portal via a Proxy server.

In this case, in the Domain text box, specify the name of the Windows domain to which the eG agent host belongs. In the Domain User Name text box, mention the name of a valid domain user with login rights to the eG agent host. Provide the password of that user in the Domain Password text box and confirm that password by retyping it in the Confirm Password text box.

On the other hand, if the eG agent is not behind a Proxy server, then you need not disturb the default setting of these parameters. By default, these parameters are set to none.

Proxy Host, Proxy Port, Proxy User Name, and Proxy Password

These parameters are applicable only if the eG agent needs to communicate with the Office 365 portal via a Proxy server.

In this case, provide the IP/host name and port number of the Proxy server that the eG agent should use in the Proxy Host and Proxy Port parameters, respectively.

If the Proxy server requires authentication, then specify the credentials of a valid Proxy user against the Proxy User Name and Proxy Password text boxes. Confirm that password by retyping it in the Confirm Password text box. If the Proxy server does not require authentication, then specify none against the Proxy User Name, Proxy Password, and Confirm Password text boxes.

On the other hand, if the eG agent is not behind a Proxy server, then you need not disturb the default setting of any of the Proxy-related parameters. By default, these parameters are set to none.

Mailbox User

Specify the name of the user mailbox to which the MAPI connectivity has to be verified by this test.

DD Frequency

Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time the test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enabled/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Status

Indicates whether/not MAPI connectivity is available.

 

The values that this measure can report and their corresponding numeric values are listed in the table below:

Measure Value Numeric Value
Success 1
Failed 0

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the status of the MAPI connectivity. In the graph of this measure however, the same is indicated using the numeric equivalents only.

Use the detailed diagnosis of this measure to know the mailbox that this test logged into, the database that was accessed in the backend, the latency that was experienced, and the errors that may have been encountered.

 

Connection time

Indicates the time it took for the MAPI connection to be established.

Seconds

A high value is a cause for concern as it indicates significant latencies in connectivity.

If the MAPI connectivity fails, then you may want to check the detailed diagnosis of the Status measure to know which mailbox was accessed, which database server was accessed, and latencies experienced in the process. This may point administrators to the probable cause of the delay/failure of MAPI connectivity.