Article ID: 921057 - View products that this article applies to.
Exchange Support Voice Column
Overview of the Microsoft Exchange Server 2003 Connector for Lotus NotesTo customize this column to your needs, we want to invite you to submit your ideas about topics that interest you and issues that you want to see addressed in future Knowledge Base articles and Support Voice columns. You can submit your ideas and feedback using the Ask For It
(http://support.microsoft.com/common/survey.aspx?scid=sw;en;1176&p0=&p1=&p2=&p3=&p4=)form. There's also a link to the form at the bottom of this column.
Welcome to the first edition of the Exchange Support Voice column. We hope that you enjoy it and will return for more. This month we will provide a concise overview of the Microsoft Exchange Server 2003 Connector for Lotus Notes. This article aims to give existing administrators and support individuals more detail about the inner workings of the Connector for Lotus Notes. For details about how to set up the environment for the Connector for Lotus Notes, please review the articles that are referenced throughout this article.
What are Lotus Domino and Lotus Notes?Lotus Domino is the messaging platform that is produced by IBM. Lotus Notes is the client software that allows users to connect to their mailboxes on Domino servers.
Each Notes user exists in a Domino domain. When you send mail from Exchange to a Domino user, you can type the following format.
What is the Connector for Lotus Notes, what is it used for, and what does it require?The Connector for Lotus Notes is included with Exchange Server 2003. This connector enables Exchange administrators to implement messaging coexistence between Exchange Server and Lotus Domino organizations. The connector provides mailflow connectivity and the ability to synchronize the two directories. In this article, we will cover details about both mailflow and directory synchronization.
Periodic updates for the Connector for Lotus Notes, known as Web Releases, are available on the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=d9f3a35e-1046-47b5-b09b-bda9de60cd9dThe most recent version of the connector requires the Exchange Server 2003 connector server to be running the latest service pack for Exchange Server 2003.
The Web Release versions of the Connector for Lotus Notes and the Calendar Connector come with their own installers. This means that you can install the connectors at any time. You are not required to install the Connector for Lotus Notes as part of the Exchange Server 2003 installation. However, the Connector for Lotus Notes requires the Lotus Notes client to be installed before you install the connector. If there is an existing connector, it will be upgraded.
During installation, the new connector creates a log file that is named the Exchange_Lotus_Notes_Connector_Setup_Progress.log file. The account that is being used to install the connector should have at least an Exchange administrator in the local administrative group plus a member of the Administrators group on the local server.
How does the Connector for Lotus Notes work?To interact with Domino, the Connector for Lotus Notes uses Notes API calls. For this reason, a Lotus Notes client must be installed on the connector server. More details about this requirement are provided in the following sections.
Preparing the Lotus Domino environmentFor details about how to prepare the Domino environment, see the "Exchange Server 2003 Coexistence and Migration for Lotus Domino Mail" topic on the following Microsoft Web site:
Preparing the Exchange Server 2003 environmentThe latest version of the Connector for Lotus Notes (Web Release 2.2) was released on December 7, 2005. The Connector for Lotus Notes Web Release 2.7 will be released in June, 2006. Requirements for these versions include:
316035Exchange Server 2003 Service Pack 2 with the Connector for Lotus Notes Web Release 2.2 requires Windows Server 2003. The Notes client should be running Lotus Notes version 6.5.4.
(http://support.microsoft.com/kb/316035/ )Lotus Notes Client versions that are tested with the Exchange Notes Connector
After you install and configure the connector, you need to enable Notes proxy addresses on the recipient policy. This is required for mailflow and directory synchronization. The Recipient Update Service will then automatically generate the proxy addresses for each mailbox-enabled and mail-enabled account in the Exchange organization by using a proxy address generator.
Typically, the Exchange user’s Notes proxy address uses the Notes domain name “Exchange". If you need to change the Notes proxy addresses, you need to modify recipient policies in Exchange System Manager.
For more information, see the "Interoperating with and Migrating from Lotus Notes/Domino Messaging Infrastructures to Exchange Server 2003" topic on the following Microsoft TechNet Web site:
Message flow between Exchange and Domino
Executables used by the connectorThe Connector for Lotus Notes works in conjunction with the Microsoft Exchange Connectivity Controller (MSExchangeCoCo) service.
The executable for the Connectivity Controller service is Lscntrl.exe. The Connector for Lotus Notes, the Connector for Novell GroupWise, and the Calendar Connector are dependent on the Connectivity Controller service, which has the responsibility of managing these services.
The following executables are loaded by the Connector for Lotus Notes:
When the Connector for Lotus Notes service starts, the DISPATCH process is started. This process starts each of the other five processes.
Collapse this imageExpand this image
What message formats are usedNatively, Exchange keeps messages in TNEF (MAPI) format, and Notes uses Composite Data (CD), which is the rich text formatting that is used in Notes. Exchange and Notes can handle formats such as HTML/MIME.
Where do messages in transit reside?A message going over the connector can be in any of the following areas:
A message going over the connector can also be in any of the following areas:
Note The BADMAIL folder is in the store, and it is used when the LSMEXNTS or LSNTSMEX processes encounter problems with MAPI messages.
The EXCHANGE.BAD database is a Notes database. Corrupt messages will be copied to this database when the LSMEXNTS or LSNTSMEX process fails to convert a message.
Message flow from Exchange to DominoMessages are transferred from Outlook on Exchange Server to Lotus Notes on Domino by using the following process:
Message flow from Domino to Exchange
Collapse this imageExpand this image
For each object (contact or Windows user) that is created by directory synchronization in Active Directory, the object's ImportedFrom attribute in Active Directory will be populated with the connector's ObjectGUID.
In the Domino directory, for the users that are created during directory synchronization, the connector will add its ObjectGUID from Active Directory to the $NotesDXAStamp field on the person document in Domino. This is how the connector can identify the objects that it created in each directory.
If you use the Immediate Full Reload option for Exchange to Domino synchronizations, all users that are included for directory synchronization (when the OU containers were selected) will be sent to Domino whether they have been synchronized previously or not.
If you use the Immediate Update option for Exchange to Domino synchronizations, only the objects that were modified since the last synchronization will be resent.
If you use the Immediate Full Reload option for Domino to Exchange synchronizations, all Domino users will be sent to Active Directory even if they were synchronized previously.
If you use the Immediate Update option for Domino to Exchange synchronizations, only the objects that were modified in the Domino directory since the last directory synchronization will be sent to Active Directory.
Lsdxa.exe uses the following DLLs to perform directory synchronization:
Directory synchronization from Exchange and Active Directory to DominoDxamex.dll pulls entries from Active Directory and places the results in the Exchsrvr\Conndata\Temp\Dxanotes.txt file. Then, Dxanotes.dll imports this data into the Domino directory.
If a full directory synchronization is initiated, the following steps take place:
Directory synchronization from Domino to Exchange and Active DirectoryDxanotes.dll pulls entries from the Domino directory, specifically, the NAB, and places the results in the Exchsrvr\Conndata\Temp\Dxamex.txt file. Then, Dxamex.dll imports this data into Active Directory.
If a full directory synchronization is initiated, the following steps will take place:
Factors that affect directory synchronization
Mapping filesYou may have an issue where a full directory synchronization from Active Directory and Exchange works, but an update directory synchronization does not work. This can happen if the Usn.tbl file is out of sync.
For more information about this issue and a resolution, click the following article number to view the article in the Microsoft Knowledge Base:
902459When the connector is installed, it populates the connector properties in Active Directory with the global catalog name that it used. This information is stored in the msExchServer1NetworkAddress attribute. If this domain controller is no longer available, directory synchronization may fail.
(http://support.microsoft.com/kb/902459/ )Active Directory cannot replicate the object to the Lotus Notes directory when you configure the Exchange Connector for Lotus Notes to use the "Immediate update" mode in the Exchange System Manager in Exchange 2000 Server or in Exchange Server 2003
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
321287To keep track of the contacts’ user name changes in Domino, a secondary Notes proxy address is applied to every contact. This proxy address uses the Notes unique identifier (UID) that is obtained from each Notes Person Document. Domino assigns a unique UID to each Person Document, much like GUIDs in Active Directory.
(http://support.microsoft.com/kb/321287/ )Directory synchronization from Exchange 2000 to a foreign mail system fails in Exchange 2000
Customizing directory synchronizationThe default directory synchronization behavior can be changed to fit an organization's requirements. The mapping tables can be modified to provide enough flexibility to meet most needs, such as synchronizing additional attributes or changing the format of an attribute. For more detail about customizing directory synchronization, see the "Connector for Lotus Notes Directory Synchronization- Part 1" blog entry on the following Web site:
Additional readingFor an online comprehensive resource on this subject, see the "Exchange Server 2003 Coexistence and Migration for Lotus Domino Mail" topic on the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/77638d41-52fb-4c3a-ad54-5224878ba540.aspxYou can also download this topic in a help file format, NotesDirAndMailMigrat.chm, from the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=7F40F5FC-59AE-4D72-A1FA-FA2620B0D3A4&displaylang=enTo view the "Interoperating with and Migrating from Lotus Notes/Domino Messaging Infrastructures to Exchange Server 2003" topic, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/2810618b-d2a7-463d-ba93-23b5e0910f9d.aspxYou can find several interesting blogs, including articles about Notes DocLinks and how the connector provides support for them, at the following Web site:
Thanks for joining us on our inaugural Exchange Support Voice column and discussion of the Exchange Server 2003 Connector for Lotus Notes. We also want to thank Shawn Zaravar for this content
A few words from Shawn:
I have been working at Microsoft Customer Service and Support (CSS) for over 12 years and about 8 years of these years with Exchange support. This included supporting the Exchange Connector for Lotus Notes since the Exchange Server 5.5 version. I have been a member of Exchange Escalation Services for the past 5 years.As always, feel free to submit ideas for topics you want addressed in future columns or in the Knowledge Base by using the Ask For It