Beruflich Dokumente
Kultur Dokumente
Version 3.0
May 2000
Paul Bowden
(pbowden@microsoft.com)
Exchange Server Product Unit
Greg Dodge
(gregdod@microsoft.com)
EC3 Enterprise Directory Team
The information contained in this document represents the current view of Microsoft Corporation on the issues
discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should
not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of
any information presented after the date of publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR
IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under
copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for
any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights
covering subject matter in this document. Except as expressly provided in any written license agreement from
Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights,
or other intellectual property.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses,
logos, people, places and events depicted herein are fictitious, and no association with any real company,
organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.
Microsoft, the BackOffice logo, Outlook, Visual Basic, Windows, and Windows NT are either registered trademarks
or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective
owners.
Abstract
This document provides an in-depth discussion of Microsoft® Exchange 2000 Server Connector for
Lotus cc:Mail and the migration tools supplied with Microsoft® Exchange 2000 Server. This paper also
discusses the process of converting Lotus cc:Mail users to Exchange 2000 Server. The intended
audience for this document is consultants and systems integrators who are considering linking a Lotus
cc:Mail environment with Exchange 2000 Server or who must migrate from Lotus cc:Mail to
Exchange 2000 Server. Correct configuration and implementation is important in mail system
coexistence and migration.
Special thanks goes to Neil Koorland from the Exchange development team and Andy Moss, Brian
Thompson, and Jeff Grewal (PSS) for their clarification of points presented in this paper. Thanks
also goes to Matt Fender, Steve Kelly, Wilson Sinclair, and Scott Anderson for discovering
practical problems at the coal-face and contributing materials; this experience has been incorporated
into the paper.
CONTENTS
Abstract........................................................................... .............3
INTRODUCTIONS.................................................................... .......4
Guide to Coexistence and Migration.......................................4
ASSUMPTIONS................................................ ..............................5
Microsoft Exchange 2000 Server...................................... .......5
Lotus cc:Mail....................................................... ....................5
WHAT YOU SHOULD KNOW BEFORE MOVING FORWARD...............6
Lotus cc:Mail....................................................... ....................6
How do I find out the database version number?..............8
Telltale signs............................................................... .......8
What is Analyze(32).EXE?............................................ ....10
What are all the files in the \ccdata directory?................10
How does this affect Exchange 2000 Server?..................12
BEFORE YOU START....................................... .............................13
Exchange 2000 Connector for Lotus CC:MAIL ARCHITECTURE....14
Is Exchange 2000 Connector for Lotus cc:Mail Connector
similar to the Microsoft Mail Connector?...............................15
The Exchange 2000 Connector for Lotus cc:Mail directory
structure........................................................ .......................16
The Exchange 2000 Server Connector for Lotus cc:Mail
Registry entries........................................................... ..........17
Message routing from Exchange 2000 to Lotus cc:Mail.........17
Message routing from Lotus cc:Mail to Exchange 2000.........18
CONFIGURING THE Exchange 2000 Connector for Lotus CC:MAIL
.................................................................................. .................20
Before you start.............................................. ......................20
The connection point............................................................20
Improving robustness.......................................................... ..24
Improving performance.................................................... .....24
If you are going to set up a test connector...........................25
Lotus cc:Mail Connector configuration and Import/Export.....25
Configuring Exchange 2000 Server Connector for Lotus
cc:Mail property pages................................................. .........27
Post Office configuration tab..................................... ............28
Post office name and path..................................... ..........29
Post office password.............................................. ..........29
Post office language..................................... ...................29
Other options..................................... .............................30
General configuration tab.....................................................32
Address Space tab..................................... ...........................32
Configuring the Lotus cc:Mail post office...............................34
Starting Exchange Connector for Lotus cc:Mail.....................34
Testing message connectivity...............................................37
What level of interoperability can I expect?..........................37
Using Exchange Server as a gateway...................................39
Implementing directory synchronization...............................41
How directory synchronization really works..........................44
Preparing to synchronize Exchange and Lotus cc:Mail..........46
SMTP Proxy Addresses............................................ .........46
The Import Container tab........................................... ...........49
The Export Containers tab....................................................51
The Dirsync Schedule tab.....................................................52
After Dir Synch has occurred............................................ .....54
Looking at the Lotus cc:Mail post office................................56
Looking at the Exchange server................................ ............56
The second synchronization cycle.................................. .......58
Bulletin boards and mailing lists...........................................58
Maintaining mailing and distribution lists..............................59
Maintaining bulletin boards and public folders......................62
Option 1: Lotus cc:Mail is primary, replicate to Exchange.....63
Option 2: Exchange is primary, replicate to Lotus cc:Mail.....64
Localization issues........................................ ........................65
MIGRATION FROM LOTUS CC:MAIL TO EXCHANGE 2000 SERVER 66
Exchange design.......................................................... .........67
Methods for migrating mailing lists.......................................67
Move the mailing lists to Exchange before user data is
migrated........................................................................ ..68
Move the mailing lists to Exchange after the users are
migrated........................................................................ ..68
The MLCONVERT utility............................................. .......68
Methods for migrating Lotus cc:Mail archives.......................68
Importing the archives back into users’ mailboxes
approach.................................................... .....................70
Harvesting to central location approach..........................72
The local migration with tools approach..........................73
Automating the Lotus cc:Mail Archive Converter ............73
Tools available for data migration.........................................77
Procedures to follow before the migration............................. 79
Private mailing lists.................................... .....................80
Seconds before the migration...............................................80
How Exchange Server Migration Wizard works......................80
Converting Lotus Organizer information...............................83
Converting Privdir.ini information................................ ..........84
Migrating a cc:Mobile user to Exchange................................84
Using Outlook against a Lotus cc:Mail post office.................85
Exchange 2000 Server Connector for LOTUS CC:MAIL REGISTRY
ENTRIES.............................................................................. ........85
Exchange 2000 Server Connector for LOTUS CC:MAIL QUICK LIST
.................................................................................. .................93
INTRODUCTIONS
Guide to Coexistence and Migration
This white paper helps consultants and system integrators perform a “marriage”
between the Lotus cc:Mail environment and Microsoft® Exchange 2000 Server.
The main aim of this document is to explain the process of connecting the two
mail systems and also guide when necessary configuration changes have to be
made to achieve the “perfect marriage”.
You must consider many issues before installing Exchange 2000 Server and
Microsoft® Exchange 2000 Connector for Lotus cc:Mail, including the following:
• What do I want to achieve: coexistence or migration?
• What are the business requirements?
• What are the technical requirements?
This paper concentrates on technical aspects of the product and is based on
Lotus cc:Mail Version 6.x or 8.x using a DB6 or DB8 database migrating to
Exchange 2000 Server
Lotus cc:Mail
This paper assumes you have some experience with Lotus cc:Mail. If you have
access to the Lotus cc:Mail manuals, they provide a good background to some
advanced topics in this paper, especially the subjects of Lotus cc:Mail Automatic
Directory Exchange (ADE) relationships and the utilities you need to prepare your
system for migration.
Telltale signs
• DB5
1. The customer tells you that they haven’t upgraded for eight or more years.
2. You can’t find Analyze.exe in the \ccadmin directory (Analyze.exe wasn’t
shipped with DB5).
3. The customer uses a program called Gateway, which was the name for the
router message transfer agent (MTA) program before Lotus renamed it.
Note The Exchange 2000 Connector for Lotus cc:Mail Connector in
Exchange 2000 cannot communicate with DB5 post offices.
• DB6
1. There are files in the \ccdata directory with the following names:
MLANDATA
CLANDATA
NFTERROR.LOG
USRxxxxx
2. The Lotus cc:Mail for Windows 2.x or 6.x client is being used on the desktop.
3. Analyze.exe reports database version 6.
• DB7
• DB8 (8.x)
7. There are files in the \ccdata directory with the following names:
CCPOMS.xx
8 MIGRATION FROM LOTUS CC:MAIL TO EXCHANGE 2000 SERVER
CCPODS.xx
8. The Lotus cc:Mail for Windows 6.x or 8.x client is being used on the desktop.
9. Analyze(32).exe reports database version 8.x.
Note Because DB6 is not year 2000 compliant, Microsoft does not support
date-related issues when trying to migrate from this database version.
Fortunately, the tools and procedures in this paper successfully migrate the
data from this database version.
In addition to these basic directories, the Dirsync directory might appear after
you configure Exchange 2000 Connector for Lotus cc:Mail.
Value: UseNtCaching
Type: REG_DWORD
Value: 0
Note that you might notice some system performance degradation as a result of
changing these Registry values. For maximum Exchange 2000 Server
performance, run the Exchange 2000 Server Connector for Lotus cc:Mail on a
dedicated computer, which will mitigate the performance hit of this setting.
The CCREGMOD program is available on newer releases of the Lotus cc:Mail
software CD, or from the Lotus Web site at http://www.lotus.com/ccmail.
Improving performance
Because the Import and Export programs are used to facilitate message flow
between the two environments, an NTVDM is created to execute these DOS-
based utilities (every 15 seconds by default). Whenever a VDM is spawned under
Windows NT, the contents of CONFIG.NT and AUTOEXEC.NT are processed. You
can increase performance by removing unnecessary commands from these files.
Examples are the virtual CD-ROM driver and virtual network protocol drivers (if
you use a local Isolation post office). You might also increase the time period to
prevent Import and Export from running too frequently. This decreases the load
on the server.
There is a bug in version 5.12 of the Lotus cc:Mail Admin.exe program (which is
used to set up a DB6 post office). With this bug, the post office is created
successfully and new entries can be entered, but the post office name and
password are automatically corrupted. This means that if you try to get the
Exchange 2000 Server Connector for Lotus cc:Mail running, it won’t work. Also,
when you log out of the Lotus cc:Mail Administrator program and try to log in
again, you can’t.
Therefore, always create post offices interactively by running Admin.exe on its
own, and then specifying the name, password, and directory when prompted.
2. On the Exchange 2000 Server Connector for Lotus cc:Mail Post Office tab is
a check box for “Permit ADE to propagate entries synched to Lotus cc:Mail to
downstream post offices”. By default, this is selected. This is fine if ADE is
enabled on the test post office with the “/DIRPROP/Y” switch, but otherwise
an error results.
Joe l EXSITE1
cc:Mail
Joe l EXSITE1
cc:Mail
[export2]
CMD = “/EXSITE1” /D\\cpq-msg1\ccdata /END/16 /ITEMSIZE /FORMAT/FAN
/BATCH /FILES/MACBIN2 /DATE/1 /CODEPAGE/850
You can see that the Export program is told to pull messages from the queue
name that relates to the Exchange Site.
When you send mail messages from Lotus cc:Mail to Microsoft Exchange,
generally, all the information is preserved in the way that you expect. The Lotus
cc:Mail client is not as functional or as rich as the Exchange Client and the
Microsoft® Outlook® Messaging and Collaboration client, so many features are
not supported on message sending.
You should also notice that there are some new files in subdirectories beneath
\exchsrvr\ccmcdata\dirsync. The following table lists the purposes of these files:
Move the mailing lists to Exchange after the users are migrated
Another method is to convert all the mailing lists to distribution lists after all the
users in a list are migrated. This way, when users are migrated to Exchange,
their Lotus cc:Mail directory entries are changed from a big “L” entry to a little “l”
entry pointing to the Exchange post office, which in turn preserves the mailing
list membership. An additional benefit is that as long as the post office the user
was migrated from has not been reclaimed, you can easily restore the original
Lotus cc:Mail mailbox by changing the entry back to a big “L” entry.
Due to Lotus cc:Mail restrictions, you must make sure that messages do not have
more than 200 recipients and that the headers do not exceed 4 KB in size.
Because you have probably already addressed these limitations in your existing
Lotus cc:Mail mailing list setup, you should replicate that configuration in
Exchange. Newer versions of the Lotus cc:Mail router that come with version 8.5
have implemented solutions to address this issue, but many customers have not
turned on this feature or do not plan to because of possible issues with other
gateways. For more details about the issues involved in this problem, see the
Lotus support Web site.
In summary, you should take some time during your migration planning to
determine how to handle the migration of Lotus cc:Mail archives for the users.
The effort put forth to migrate this data must be backed by solid business needs
and business value. As an alternative to any of these three approaches for
migrating this data, you can use a mixture of methods. The best method is to
keep the archived data from touching the Lotus cc:Mail or Exchange message
database by converting directly to a .pst file. This ensures the least impact on
the storage requirements of either the old or new messaging system.
[X400]
EntryCount=1
Entry1=c=gb;a=attmail;p=lotus;s=Honer;g=Mike
The file above indicates that the pseudo-post office used to access the Internet is
called “Internet”.
Migrated users can run the Lotus cc:Mail archive importer tool to migrate their
Privdir.ini information across to Outlook Contacts. This utility is available in
Exchange 5.5 Service Pack 4 which is available to download on the Exchange
Web site at http://www.microsoft.com/exchange/downloads/55/sp4.asp.
Parameters
Note Exchange 2000 Server Connector for Lotus cc:Mail service must be
shut down and restarted after you make a change to any of these
parameters.