Unknown's avatar

About Michel de Rooij

Michel de Rooij, with over 25 years of mixed consulting and automation experience with Exchange and related technologies, is a consultant for Rapid Circle. He assists organizations in their journey to and using Microsoft 365, primarily focusing on Exchange and associated technologies and automating processes using PowerShell or Graph. Michel's authorship of several Exchange books and role in the Office 365 for IT Pros author team are a testament to his knowledge. Besides writing for Practical365.com, he maintains a blog on eightwone.com with supporting scripts on GitHub. Michel has been a Microsoft MVP since 2013.

MAPI Client and Collaboration Data Objects 1.2.1


The MAPI and CDO libraries, still required by some applications or scripts talking to Exchange, have been updated.

The libaries are meant to unwind the application and storage layers, making applications and code using these libraries independent of the underlying Exchange or Outlook version. It also enables certain applications/scripts to run remotely (mostly apps/scripts from the pre-PowerShell era). Only problem you can encounter is when applications/scripts make use of certain functionality only to be found in certain Exchange/Outlook versions, requiring specific MAPI or CDO library versions.

These libraries may be required by certain 3rd party applications, scripts, etc. that need to interface with Exchange, e.g. Blackberry Enterprise Server, the Transporter Suite (for Notes-Exchange co-existence/interoperability), Quest Exchange tools, etc. etc.

Note that MapiCDO release follows Exchange Server 2003’s lifecycle and it is recommended you upgrade your application or port your application/script to and start leveraging new Exchange interfaces, e.g. Exchange Web Services, Outlook Object Model or the Outlook MAPI Client Library.

ExchangeMapiCDO 1.2.1  version 6.5.8165.0 can be download here.

Exchange 2010 Item Recovery


The MS Exchange Team blog had a great informative article yesterday on discovering and recovering items in Exchange 2010 RTM as well as SP1.  I suggest you check the article located here.

For people asking why it’s rather quiet over on my blog, I haven’t had time to blog/tweet a lot due to personal circumstances. But this is behind me now, so I’ll be picking up where I left off ASAP. Thanks for bearing with me.

Rollup time


Besides the Exchange 2007 SP2 RU4 of yesterday and this morning’s Exchange 2010 RTM RU3, Microsoft also released Exchange 2007 SP1 Rollup 10 (KB981407) and a security fix for Exchange 2003 SP2 (KB976702).

Both Exchange 2007 SP1 RU10 and the Exchange 2003 SP2 update fix the issue documented in security bulletin MS10-024, being a vulnerability issue in Microsoft Exchange and the Windows SMTP Service which could lead to a denial of service.

You can download Exchange 2007SP1 RU10 here and the Exchange 2003 SP2 fix here.

And pssst .. there’s even a Exchange 2000 SP3 fix here.

Exchange 2010 RTM Rollup 3


Microsoft released Rollup 3 for Exchange Server 2010 RTM (KB981401). This update raises Exchange 2010 version number to 14.0.694.0.

Not many hotfixes included in this rollup, but important ones, including a security fix. Here’s the list of changes included in this rollup:

  1. 981832 MS10-024: Vulnerabilities in Microsoft Exchange and Windows SMTP Service could allow denial of service
  2. 981664 RPC clients or MAPI on the Middle Tier clients may not receive responses from the mailbox server role on an Exchange 2010 server

To download this rollup, click here. The Exchange versions, builds and dates table has been updated accordingly and can be found here.

Exchange 2007 SP2 Rollup 4


Microsoft released Rollup 4 for Exchange Server 2007 Service Pack 2 (KB989381). This update raises Exchange 2007 version number to 8.2.254.0.

Here’s the list of changes included in this rollup:

  1. 981832 MS10-024: Vulnerabilities in Microsoft Exchange and Windows SMTP Service could allow denial of service
  2. 981706 Exchange 2007 SP2 Rollup 1 or Exchange 2007 SP2 Rollup 2 does not install on a Spanish version of Exchange Server 2007 SP2
  3. 980639 A user can only set the time zone to Bucharest in OWA after you update Exchange Server 2007 Service Pack1 to Exchange Server 2007 Service Pack 2

To download the x64 or x86 version of this rollup, click here. The Exchange versions, builds and dates table has been updated accordingly and can be found here.