The Transporter Suite for Lotus Domino on Exchange Server 2010

I wrote this article on help inform everyone of the options they have with the Transporter Suite  for Lotus Domino and Exchange Server 2010.


Installation completes, the configuration fails. Why ? It was never designed for Exchange Server 2010.

What does not function ?

  • Directory Synchronization
  • Free Busy
  • Move-DominoMailbox

What does function ?

  • Move-DominoUser UI/powershell


Solution is to install on an Exchange 2007 Server. Use that as your bridge server to and from Domino for the duration of the coexistence and migration, then retire it when complete.

Two system integrators have products which can help you go directly without this bridge method, Binary Tree and Quest Software

High Level Overview

Configuring the Exchange Server 2007 Bridge

  1. Install a full CAS/HT/MBX with Exchange 2007 Sp2 and rollups as the FIRST SERVER in the NEW EXCHANGE ORGANIZATION.
  2. Install Notes Client
  3. Install Transporter Suite
  4. Install MAPI/CDO Pack
  5. Create Connectors
  6. Set notes ini path (shell) for both
  7. Directory Synchronization
    • Add Machine Account (Exchange server $) to OU for Target Domino users, ensure do all sub containers (this object/all descendant objects)
  8. Free Busy Connector
    • Check Windows firewall on 2k8 (key thing people miss)
    • Disable SSL on VDIR on 2k7 then iisreset
  9. Install the first Exchange Server 2010 in your new Exchange organization
  10. When migration/coexistence is done, retire the Exchange Server 2007 bridge.

User Migration / Data Migration

  • Evaluate the system integrators migration tools to eliminate the double hop migration, to 2007 then 2010.
  • You will have to do a two stage migration if you use the free tools, once to 2007, then move the mailbox to 2010.
  • Don’t forget to follow the directions in the end to end guide on impersonation so you can migrate mail to 2007

Domino to Exchange Server 2010 Summary

  • Transporter Suite does not function on Exchange Server 2010 because it was never designed to do so.
  • Use a Exchange Server 2007 Bridge, using the Transporter Suite for Directory Synchronization and Free Busy query capability.
  • Consider a system integrator for mailbox migration directly to Exchange Server 2010
  • Always read the definitive guide –> Click on the seal of approval