Well it's finally released. The long awaited MAPI/CDO download that includes the documentation which outlines how to connect to Exchange 2013. As a supplement to that I have created this blog post to walk you through the steps of creating a profile using MFCMAPI to troubleshoot issues. The intention of this article was to provide a quick and simple guide. It outlines the default case, but it is out of the scope of this article to provide an in depth discussion of every scenario. I have provided these steps to many customers and for the most part they ring true.
- Exchange 2013 Wiki
- Mapi Https
- Exchange 2013 Release Date
- Mapi Cdo For Exchange 2013 Mail User
- Enable Mapi Exchange 2013
First things first, please download the latest version of MAPI/CDO found here: https://aka.ms/mapicdo. It is assumed that you are using at least version 6.5.8309. However, these steps do not work with any version of Outlook. This profile will also not work against a legacy version of Exchange even if the target server is Outlook Anywhere enabled. Lastly, make sure you are using the latest version of MFCMAPI.
Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 May 2013 Update Important! Selecting a language below will dynamically change the complete page content to that language. Microsoft Exchange MAPI - Frequently Asked Questions / Solutions. Exchange server 2013. Uninstall the feature 'Microsoft Exchange Server MAPI Client.
It's been some time, but still problem with GLR on Exchange 2013 (CU3) is haunting me. EMC support has finally kicked the ball to the Microsoft part of field. What we have done on the Exchange server since then is: 1. Removed MAPI/CDO tools; 2. Installed MS Outlook and opened it under AvamarBackupUser (worked flawlessly); 3.
- Make sure that you have Exchange 2013 properly configured. The best way to do this is confirm that Outlook can connect successfully.
- Open up MFCMAPI, go to Profile > Show Profiles
- Click Actions > Create Profile
- Give the new profile a name and click OK.
- Select the new profile
- Right-Click and choose Services > Add Service..
- Enter MSEMS for the service name
- Uncheck the box which says 'Display Service UI'
- Click OK
- Double-click the newly created profile
- Double-click the MSEMS service
- Find the Global Profile Section. It's the provider with the PROVIDER_UID that is 13DBB0C8AA05101A9BB000AA002FC45A and single click it.
- Go to Property > Additional Properties
- Click Add and add the following properties PR_CONVERSION_PROHIBITED, PR_PROFILE_UNRESOLVED_NAME, PR_PROFILE_UNRESOLVED_SERVER, PR_PROFILE_RPC_PROXY_SERVER, PR_PROFILE_RPC_PROXY_SERVER_FLAGS, PR_PROFILE_RPC_PROXY_SERVER_AUTH_PACKAGE, PR_PROFILE_AUTH_PACKAGE.
- Click OK
- Configure each property using the guidance below.
Property: PR_CONVERSION_PROHIBITED Value: True Property: PR_PROFILE_UNRESOLVED_NAME Value: mailbox alias The alias for the target mailbox. For example, Administrator Property: PR_PROFILE_UNRESOLVED_SERVER Value: The personalized server id This is the value retrieved from Autodiscover. It will be in the format guid@domain. For example, [email protected] Property: PR_PROFILE_RPC_PROXY_SERVER Value: FQDN of your Client Access Server. You don't need to specify http:// or https://. For example, e2013cas.contoso.com 6.5.8309 requires the use of the ANSI version of this property Property: PR_PROFILE_RPC_PROXY_SERVER_FLAGS Value: PRXF_ENABLED (0x1) Instructs the MAPI subsystem to use RPC over HTTP to connect to the server Property: PR_PROFILE_RPC_PROXY_SERVER_AUTH_PACKAGE Value: RPC_C_HTTP_AUTHN_SCHEME_NTLM (0x2) Describes the authentication scheme to use for RPC over HTTP Property: PR_PROFILE_AUTH_PACKAGE Value: RPC_C_AUTHN_WINNT (0xA) Describes the authentication scheme to use for RPC Property: PR_PROFILE_CONNECT_FLAGS Value: CONNECT_USE_SEPARATE_CONNECTION (0x4) | CONNECT_IGNORE_NO_PF (0x8000) Tells the subsystem to use a separate connection and still connect if no public folders are in the organization - Select Session > Logon and display store, and select the profile is not already selected.
The personalized server id is the server name returned from Autodiscover. You can find this in a variety of ways. If you are using the SOAP based Autodiscover the property you are looking for is InternalRpcClientServer. If you are using the Plain Old XML (POX) based Autodiscover the property you are looking for is of type EXHTTP in the protocol node. The node name is Server. You can use Outlook to make an Autodiscover request on your behalf by right clicking the Outlook icon in the System Tray while holding down the CTRL button and choosing 'Test E-Mail Autoconfiguration'.
For PR_PROFILE_RPC_PROXY_FLAGS your environment may require the flag PRXF_SSL (0x2) to tell MAPI to use SSL. If your certificate is not trusted then add the flag PRXF_SEC_WARNING (0x10).
I will be writing a subsequent article which describes how to use the RPCHttpProxyMap registry key. [Edit: 5/27/2013: That post is completed.]
The version of MAPI/CDO was incorrectly stated on the download page as 8.3.8309 for 6.5.8309. Salamander net decompiler crack.
If you have questions, just add a comment and I will approve them and respond as time permits
[Edit: 7/8/2014] I added screenshots and I wanted to point out that these steps may not work out in all environments. In order to use these steps your environment must support NTLM as the authentication protocol for Outlook Anywhere. For environments that support Basic you will need to alter these settings. The best way to know what your environment requires is to review the Autodiscover response for the target mailbox. You can use the steps documented in this Technet Article in the section entitled Step 3: Check Autodiscover and Exchange Web Services to perform an Autodiscover and see the response using Outlook 2007 and above.
[Edit: 10/14/2015] Updated the link to the latest version of MAPI CDO
In Exchange 2013 SP1 there appeared a new protocol for client connections to a mailbox — MAPI over HTTP (MAPI/HTTP). This protocol is to improve stability and reliability of Outlook connection to the Exchange server due to moving traffic to HTTP level. In this article, we’ll tell about the architecture and peculiarities of this protocol together with a short instruction on how to configure it.
In its previous versions, Outlook could interact with Exchange over RPC. In Exchange 2003 another connection protocol appeared — RPC over HTTP (or Outlook Anywhere). This protocol was used mainly for secure connect external clients to the Exchange server. In Exchange 2013, Outlook Anywhere is used in the interaction with both internal and external clients by default. In general, when using this protocol, MAPI traffic firstly wrapped in RPC, then RPC in HTTP, and then the HTTP packet was sent to the server. The main disadvantage of RPC over HTTP is its instability in unstable connections (in public Wi-Fi networks or in the Internet).
MAPI over HTTP (in fact, HTTPS is used) eliminates RPC from the scheme and is based on HTTP 1.1, so to interact with the server, the clients use POST command. Outlook using MAPI over HTTP works in the same way as EWS, EAS or OWA. https://swagtree217.weebly.com/one-piece-episode-setelah-peperangan-marineford.html. When using it, the scenarios, like switching between networks, recovery after network failures, wake from sleep or hibernation, etc., work better.
Advantages of MAPI over HTTP
- Fast reconnection after link break (only TCP is reconnected, not RPC)
- Independence of the session contents from connections (a user can change the connection network during session)
- Authentication using the HTTP protocol
Firstly, client-side MAPI/HTTP was supported only in Outlook 2013 SP1, but now after the update 2899591 (https://support.microsoft.com/en-us/kb/2899591/en-us) has been installed, it works in Outlook 2010 as well.
To enable MAPI over HTTP support, the system has to meet the following requirements:
Exchange 2013 Wiki
- Exchange 2013 SP1 should be installed on CAS servers
- For optimal MAPI/HTTP performance, .NET framework 4.5.2 should be installed
- Outlook 2013 SP1 or Outlook 2010 with the update KB2899591 should be used as clients
After Exchange 2013 SP1 is installed, MAPI virtual directory appears on a CAS server. However, MapiOverHTTP is disabled.
Make sure that ExternalUrl attribute is empty:
Get-MapiVirtualDirectory | ft server, *url*
As we can see, ExternalUrl is empty, and we have to fill it. (In this example, we’ll specify both ExternalUrl and Internal Url; bear in mind that the Exchange certificate has to correspond to the addresses specified as the external and internal URLs.)
Get-MapiVirtualDirectory | Set-MapiVirtualDirectory -InternalUrl https://mail.contoso.com/mapi –ExternalUrl https://mail.contoso.com/mapi -IISAuthenticationMethods NTLM,Negotiate
Mapi Https
![2013 2013](https://4.bp.blogspot.com/-1CS4Lw39pnI/UROlE7vDqfI/AAAAAAAAAXg/Tz-q71b42M4/s1600/13.png)
Now you only have to activate MAPI over HTTP on the Exchange level. Make sure that the protocol is disabled:
Get-OrganizationConfig | FL *mapi*
Also, make sure that Outlook is using RPC/HTTP to connect to Exchange.
Activate MAPI/HTTP support on the server side:
Set-OrganizationConfig -MapiHttpEnabled $true
After you run the command, wait for about an hour so the changes are applied on the Exchange side. If necessary, it can be done faster by restarting MS Exchange Host Service and Autodiscover pool on Mailbox server.
During autodiscovery (Autodiscover), Outlook requests MAPI over HTTP (X-MapiHttpCapability) support from the server. If the server supports this protocol, the client gets a response containing HTTP data.
When changing a protocol, Outlook shows this warning:
The Microsoft Exchange administrator has made a change that requires you quit and restart Outlook.
After the restart, Outlook has to connect to the mailbox using MAPI over HTTP. This is evidenced by HTTP line in the Protocol column in Outlook connection properties.
You can check if it’s possible to connect over the new protocol by following this link https://mail.contoso.com/mapi/emsmdb. We’ll get the name of the CAS server, on which we have authenticated, and the name of Mailbox server.
Adding ?Showdebug=yes to the URL, we can display some more interesting information.(https://mail.contoso.com/mapi/emsmdb/?showdebug=yes)
Exchange 2013 Release Date
Also you can check if the new protocol works using a PowerShell cmdlet Test-OutlookConnectivity:
Test-OutlookConnectivity -RunFromServerId serv3 -ProbeIdentity OutlookMapiHttpSelfTestProbe
Troubleshooting:
The logs of the new protocol are stored here:
- CAS: %ExchangeInstallPath%LoggingHttpProxyMapi
- Mailbox Server: %ExchangeInstallPath%LoggingMAPI Client Access
- Mailbox Server: %ExchangeInstallPath%LoggingMAPI Address Book Service
If MAPI over HTTP is enabled in the DAG group, all servers have to support it, otherwise clients won’t be able to use their mailboxes.
According to Microsoft estimates, MAPI over HTTP slightly increases the CPU load on CAS servers, but reduces the memory use by 50-60% for each user.
The new protocol of Outlook connection to Exchange mailboxes is better both in its performance and network flexibility. According to Microsoft developers, MAPI over HTTP will become the main connection protocol in Exchange Server 2016, and RPC over HTTP will be abandoned.