We just announced a new release of the MAPI Download that’s pretty much mandatory if you want to work with Exchange 2010. You’ll also need to get and apply Rollup 1 (RU1) for Exchange 2010.
Details about the MAPI Download:
The new MAPI Download fixes a number of problems MAPI had with Exchange 2010:
If I identify other issues fixed by the updated MAPI download, I’ll add them in here.
[Update: 12/14/09] Forgot to mention that you'll still need these tweaks for your profile, but you don't have to disable encryption anymore.[Update: 12/21/09] Added information about admin access to PF.
Now that Outlook 2010 supports multiple Exchange (MSEMS) service entries, how do we add them and change the PR_DISPLAY_NAME so that they appear different to the user?
Hi Stephen & All,
I am using Exchange 2010 and having two RDB's in my server. I can able to browse one RDB through MFCMAPI but if i dismount that RDB and mount another one i m not able to browse that RDB. And i am getting the legacy error 0x8004011D error. Is it problem with MFCMAPI? or do i need any configuration changes?
Alan - this is a known (server side) issue with multiple RDBs. I believe we are investigating a fix for this.
Do we have any KB Article which is mentioning about the Multiple RDB Issue. Please provide the link for the same.
I am having 10 Exchange 2010 Servers in my organization and in some exchange servers while i use MFCMAPI i am getting 0x8004011D error when querying "IExchangeManageStore5" interface and in some exchange servers i am getting 0x80040115 when calling function OpenMsgStore. But other Exchange 2010 Servers MFCMAPI is working fine and i can able to browse mailboxes.
It would be very helpful if you provide some thoughts regarding this issues. One thing i observed is most of the problems are coming in DAG Machines. MFCMAPI is working fine in stand-alone machines.
Stephen, would you be able to shed light on what the actual encryption algorithm is (other than the 0xa5 XOR). Is it variable or some common algorithm (variation of 56/128 bit RC4 etc?)
It's RPC encryption: technet.microsoft.com/.../dd277366.aspx