About 51 results
Open links in new tab
  1. Outlook Connectivity with MAPI over HTTP | Microsoft Community Hub

    May 9, 2014 · MAPI/HTTP increases the CPU load in the Exchange Client Access Servers. This is a 50% increase over Exchange 2013 RTM, however it is still lower than Exchange 2010 requirements. …

  2. Understanding how Outlook, CDO, MAPI, and Providers work together

    Apr 8, 2005 · CDO and Outlook are both MAPI applications, meaning that they use MAPI APIs to access their data, and therefore, the underlying providers. CDO and Outlook share a common set of …

  3. Planning considerations for REST-based (aka new model) calendar …

    Aug 12, 2022 · The REST Model The new calendar sharing model based on REST is designed to avoid MAPI issues related to conflicting permissions and multiple editing delegates. This is one of the …

  4. New Outlook: MAPI / Exchange | Microsoft Community Hub

    May 31, 2024 · I don't think microsoft will ever try to add mapi to it because mapi is a "client side" technology that whereas the new outlook is all server side (excluding the html/css rendering).

  5. Recommendation: Enabling Kerberos Authentication for MAPI Clients

    Apr 15, 2011 · MAPI supports Kerberos authentication and the default setting in Outlook 2007 and later is to negotiate the strongest authentication available when not running in Outlook Anywhere mode. In …

  6. REST instead of MAPI | Microsoft Community Hub

    Dec 6, 2018 · REST instead of MAPI At Ignite, the Outlook team said that "coming soon" we'd have the ability (in an Insider version of Outlook) to manually enable the new calendar functionality via a …

  7. Client Connectivity in an Exchange 2016 Coexistence Environment with ...

    Oct 26, 2015 · External Outlook Anywhere & MAPI/HTTP Connectivity In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to …

  8. Outlook clients receive error 0x8004010f when downloading the Offline ...

    Jul 1, 2019 · EDIT 10/01/2008: To read the updated (and more comprehensive) guidance for troubleshooting errors 0x8004010f, please go here. There are a multiple reasons...

  9. Exchange 2013/2019 coexistence and client connectivity to new 2019 ...

    Apr 30, 2023 · Hey all, Some details first: Forest/Domain functional level: 2012 R2 (only one domain) 2 x Exchange 2013 CU 23 Servers in a DAG (both on Server 2012) 1 x Exchange 2019 CU 12 server …

  10. Client Connectivity in an Exchange 2016 Coexistence Environment with ...

    Oct 28, 2015 · For MAPI/HTTP clients, an Exchange 2013 Client Access server will authenticate the user, do a service discovery, and determine that the mailbox version is 2013 and where the mailbox …