Exchange 2013 Compatible MAPICDO
As several of you have noted, we recently released an update for the MAPICDO package. This is the update you have all been waiting for, as it is now possible to build an RPC/HTTP enabled profile to connect to Exchange 2013. What several of you have also noticed is that this update did NOT come with any guidance for HOW to build such a profile. Such guidance does exist, but hasn’t been published yet. I had delayed commenting on this new package until the guidance was ready, but it’s taking longer than I thought it would.
I’m working with the team responsible for publishing the guidance to get it out the door. We’ve almost got it ready, so I expect to see it up on the download site (or the Exchange blog) any day now. Once that guidance is published, Dave will most likely publish an updated version of his How to Build a Profile For MFCMAPI guidance. I’ll link to both as soon as they’re public.
Comments
Anonymous
March 07, 2013
In theory, it seems like this version of MAPI could allow a legacy app to connect to Office 365. Any reason why this might not work ?Anonymous
March 07, 2013
Hypothetically speaking, should this MAPICDO package work with Office 365 ? Second comment -- first one did no appear even after several hours.Anonymous
March 24, 2013
Since MS Exchange Server comes only in 64-bit version, since MS Exchange Server 2007, are there any plans to release a 64-bit version of MAPICDO package, or to include a 64-bit versions of MAPI dlls? Thank you, DanAnonymous
March 24, 2013
Dan - your logic is flawed. The server is 64 bit, but clients do not need to be 64 bit. There are no plans nor need to release a 64 bit MAPICDO package.Anonymous
March 26, 2013
upon "What several of you have also noticed is that this update did NOT come with any guidance for HOW to build such a profile. Such guidance does exist, but hasn’t been published yet...' Any news upon this? Because without creating profiles new MAPICDO isn't very usable... :-) Thanks ThomasAnonymous
March 26, 2013
Understood - we're still working on it.Anonymous
March 27, 2013
Hi Stephen, I have posted an update after your response from Mar 25 2013, 6:46 am, but I do not see it here; My response was something along the lines: I might have not made myself clear; I know that MAPICDO package is to be used by client applications, that do not need to be 64 bit, as the server. However, on a resource intensive application, it makes sense to build a 64 bit client and overcome the limitations posed by the 32-bit architecture. Now, you've made it clear that, I would say unfortunately, there are no plans to ship 64-bit MAPICDO packages. On the other side, MS Outlook 2010 (and possible subsequent versions), comes with 64 bit supporting MAPI dll, as far as I know. Is it possible/supported to install such a version of MS Outlook on an Exchange Server (that has Client Access server role at least, but it could have all roles in a standalone deployment), and have a client application use that 64 bit MAPI coming with Outlook? Thank you, DanAnonymous
March 27, 2013
Stephen, thanks so far...
- Is there maybe some info/support within new MFCMAPI?
- upon what Vern already asked 3 weeks before (without any answer yet): Is new MAPICDO-package able to work with Office 365 ?
- Is new MAPICDO-package able to create Unicode-PSTs ? Thanks Thomas
Anonymous
March 27, 2013
This may be a bit off-topic but, with your experience in programming MAPI for Exchange Servers, what is the best solution (performance and stability wise) to develop an application to export data, at item level, from Exchange mailboxes? I would really appreciate your answer. Best regards, DanAnonymous
March 27, 2013
Dan - for new development you should use Exchange Web Services (EWS). Thomas, 1 - MFCMAPI can be used to create profiles for 2013, but you'll need details on the new props you have to set in the profile 2 - Don't know why it shouldn't work. 3 - No.Anonymous
March 28, 2013
Stephen, I still have one question, regarding your recommendation to use EWS for new development: I have read some posts where people were saying that applications using EWS were much slower that using MAPI. For applications dealing with large Exchange databases, where performance is crucial, can you comment on EWS vs MAPI please? Thank you for all your info and help, DanAnonymous
March 28, 2013
It is possible to write slow EWS applications, especially if you're not carefully optimizing your requests to only get the information you absolutely need, and to not request information you already have.Anonymous
April 03, 2013
That response of yours is very political :-). Of course you can write slow EWS applications, but so you can with MAPI; however, assuming a well written application is implemented with EWS, how would perform to extract, let's say, individual mailboxes, vs a well written application using MAPI? Thank you, DanAnonymous
April 03, 2013
Do we have any news about guidance for HOW to build profile for Ex2013? We still waiting. Thank YouAnonymous
April 03, 2013
I look forward to reading about how to create RPC/HTTP enabled profiles for Exchange 2013.Anonymous
April 08, 2013
Hi Steve, do you have any updates when the documentation how to connect MAPICDO to Exchange 2013 will be available? Thank you SvenAnonymous
April 08, 2013
I am also interested in when the guidance for the MAPICDO profiles will be made available as this may be critical for some application migration to E2013.Anonymous
April 09, 2013
The comment has been removedAnonymous
April 09, 2013
Hi Thomas, can you share information on how you created the profile with MAPICDO to access Exchange 2013? Is there already some documentation online? Thanks SvenAnonymous
April 11, 2013
EinmalIM - to have possibility to create MAPI profile with MFCMAPI 15.0.0.1039 we had to restart server after installation MAPICDO 8.3.0.8309 (BTW for some reason the real version of MAPICDO DLLs are 6.5.8309.0). And then standard way - Profile -> Advanced profile -> Launch profile wizard... -> it shows Service: MSEMS and Flag: 2 -> just click OK -> Microsoft Outlook Setup Wizard is started -> select first radio-button 'Use the following information services' (without restarting the 1st radio-button was disabled and if we selected 2nd -> it showed error on some step) -> and then pass through the wizard -> on the finish MAPI profile was created and we can access the selected mailbox. But problem with Public Folders is not resolved until now...Anonymous
April 11, 2013
I'd like to second EinmallM's comment, is there any documentation or a walk through of creating a basic profile that connects to Exchange 2013? We have an application that does not work against mailboxes that have been moved to Exchange 2013 and we believe if we can create the correct MAPI profile we'll be OK. thanks SteveAnonymous
April 14, 2013
The comment has been removedAnonymous
April 15, 2013
Hi Valery, tried that, but that gives me an error dialog "The name could not be resolved. Network problems are preventing connection to the Microsoft Exchange Server computer...". I think that is expected as I cannot set any RPC over HTTP options in the profile wizard of ExchangeMAPICDO. So I guess MAPI tries to directly speak RPC with the Exchange Server. What am I missing that you logon to the mailbox succeeds? Thanks SvenAnonymous
April 15, 2013
Any news on creating a basic MAPI profile for Exchange 2013? Regards ThomasAnonymous
April 24, 2013
"...so I expect to see it up on the download site (or the Exchange blog) any day now..." Almost 2 months seem quite a while for "any day now...". Please, our customers ask for Exchange 2013 support of our MAPI based product.Anonymous
May 12, 2013
Can we get any confirmation that this even works? Regards ThomasAnonymous
May 13, 2013
@Claus: I guess it does. At least for BlackBerry Servers there is a documentation how to configure their Server with the latest ExchangeMAPICDO package using RPC over HTTP: btsc.webapps.blackberry.com/.../viewdocument.do Maybe any BlackBerry admin who has this up an running could share information about the profile details in the registry? This would be the starting Point to search for a BESAdmin profile: HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWindows Messaging SubsystemProfiles -- SvenAnonymous
May 13, 2013
Still no docs on how to create a profile for Exchange 2013 (RPC over HTTP) ? - it's been over 2 months now folks ... .. KenAnonymous
May 14, 2013
The delay in releasing this documentation is causing problems for us. We could get it working with a bit of trial and error, but would rather have definitive documentation to ensure that we get it right.Anonymous
May 19, 2013
I also need the doco on how to create an exchange 2013 profile for RPC over Http. This is really urgent for sites that are now using exchange 2013. Thanks.