If the migrated users are from Lotus Notes contacts and if these contacts were members of distribution lists (DLs) before the migration, the DL memberships are not retained when you run the Migration Wizard. To retain the DL memberships, use ADClean to merge the Windows NT user accounts with the Lotus Notes contacts. After you run ADClean, rerun the Mailmig.exe command-line utility. After you do so, mailbox-enabled accounts are created and mail and data are moved from Lotus Notes to Exchange 2000.
You can use the Mailmig.exe command-line utility to script the migration of users of Lotus Notes to Exchange 2000. When you use this method, you can specify the user accounts that will be migrated in a control file. When you do so, you can prevent a bulk migration. However, Microsoft recommends that you use the GUI version of the Migration Wizard. If you must use the Mailmig.exe command-line utility, you can use the following command line to migrate from Lotus Notes to Exchange 2000, where
migrate.txt is the name of the control file:
mailmig.exe /c:migrate.txt /a:user.id /P:abc
The following text is an example of a control file that can be used for Lotus Notes migrations:
Mode,Notes
File,c:\temp
ExchStoreDN,CN=Mailbox Store (Server1),CN=First Storage Group,CN=InformationStore,CN=Server1,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=Sabbath,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=test,DC=com
Container,OU=Migration,DC=test,DC=com
INIFile,f:\lotus\notes\notes.ini
POName,exfor_lab1/lcxfor
SchdStart,19980101000000
EmailStart,19980101000000
DocLinkConversion,OLE
NTAccounts,Random
ExchStore, Mailbox Store (Server1)
Home-Server, Server1
Note: You must make sure that the
ExchStoreDN parameter is used in the control file.
Use ADSI Edit to verify that you are using the correct value for the Mailbox Store distinguished name (also known as DN) in the
ExchStoreDN parameter. This value is required if you have more than one mailbox store on the server.
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, or both Windows and Exchange 2000 Server. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
Verify that the
NTAccounts parameter is set to
RANDOM. See the sample control file that is described earlier in this article for an example. By default, this parameter is included. This parameter creates a new Windows NT user account and it mailbox-activates the account to allow migration to complete successfully.
If the
NT Accounts parameter already exists in Active Directory, if you use the
NO parameter, the migration fails.