Enable mapi

Question

Server 2016, exchange 2016.

If mapi is changed from disabled to enabled, will there be any configuration changes required on client outlook accounts or anywhere else?

Answer 1

Typically, when you change this, any Outlook client will get prompted to restart, in some cases a new Outlook profile is requried.

Before enabling for the entire org, enable a few test mailboxes so you can see how it looks

Make sure you have already configured the pre reqs before doing that, ( the virtual directory URLs being set correctly )

https://learn.microsoft.com/en-us/exchange/clients/mapi-over-http/configure-mapi-over-http?view=exchserver-2019

Answer 2

Hi @Susan Dodds

According to your description above, do you mean mapi/http rather than mapi?

MAPI: When MAPI is enabled, a user's mailbox can be accessed by Outlook or other MAPI email clients. When MAPI is disabled, it can't be accessed by Outlook or other MAPI clients. However, the mailbox will continue to receive email messages, and, assuming that the mailbox is enabled to support access by those clients, a user can access the mailbox to send and receive email by using Outlook on the web (formerly known as Outlook Web App), a POP email client, or an IMAP client.

For Mapi/http, yes like Andy said, generally we just need to restart the outlook, the protocol will change.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
 

Answer 3

RunspaceId : zzzzz
IISAuthenticationMethods : {Ntlm, OAuth, Negotiate}
MetabasePath : IIS://zzzzz/zzzzz/mapi
Path : install path\mapi
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.1 (Build zzzz)
Server : servername
InternalUrl : https://zzzzz/mapi
InternalAuthenticationMethods : {Ntlm, OAuth, Negotiate}
ExternalUrl : https://zzzzz/mapi
ExternalAuthenticationMethods : {Ntlm, OAuth, Negotiate}
AdminDisplayName :
ExchangeVersion : zzzz
Name : mapi (Default Web Site)
DistinguishedName : zzzzz
Guid : zzzzz
ObjectCategory : zzzzz/Configuration/Schema/ms-Exch-Mapi-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchMapiVirtualDirectory}
WhenChanged : zzzzz
WhenCreated : zzzzz
WhenChangedUTC : zzzzz
WhenCreatedUTC : zzzzz
OrganizationId :
Id : server\mapi (zzzz Site)
OriginatingServer : local DC
IsValid : True
ObjectState : Changed

When running the connectivity tool, it says autodiscover fails but I have no trouble creating outlook profiles and other email client provider profiles inside or outside of the local network and don't have any trouble accessing email.