CMT for Exchange


Exchange, How To

Brief Description:

Group Migration (Distribution List) from Notes to Exchange


Group Migration (Distribution List) process for Notes to Exchange


How do you migrate Notes Groups (Distribution List) to Exchange?


Please read the Name Resolution Process continuing (please click the link below for further explanation)

How to configure LDAP

CMT Universal – Group Migration

This process will migrate groups from Lotus Notes into Microsoft Exchange. The following will be preformed during the Group Migration Process.

1.) All users must be in the ‘Resolved’ or in the ‘Ready for Migration’ status in order for the user to be added to the distribution list during the group migration process

2.) As selected Lotus Notes Groups are migrated into the Active Directory, they’re membership will be removed and re-created with all members, including nested Groups.

3.) Any member of a Lotus Notes Group, which is not present in the Domino Directory, will be logged as an error and will not be migrated.

4.) Any member of a Lotus Notes Group, which is not present in the Active Directory, will be logged as an error and will not be migrated.

5.) Group migration status will be reported as follows: error - no group members were migrated; warning - some group members could not be migrated; success - all group members were migrated.

To configure CMT Universal for the Group Migration please do the following:

1.) Open CMT Universal and click on the Migrate Tab

2.) Click on Settings and walk through the settings screen
* Make sure you fill in the settings for LDAP directory to ensure connectivity to the LDAP server when importing groups (Process described in more detailed LDAP Name Resolution.doc)

3.) Click on the Users button and click on the Migrate Groups button

4.) Click on Settings and fill in the appropriate settings per your environment

* Select which Notes Name and Address Book you want to pull groups from

* Fill in the settings to resolve users, specify where groups will be created and the domain name to append to the user’s targetAddress attribute

* Note: When migrating the groups, we are matching each member in the Notes Group against the targetAddress attribute in LDAP, which should contain the Notes distinguished name of users created by dir sync with the Domino NAB. This attribute looks like:
targetAddress: NOTES:Joe Admin/BinaryTree@BinaryTree; where the first item is the platform, then the user's Notes distinguished name, then the @domain that indicates the Notes domain

5.) Click on Refresh Group List
* During this ‘import’ we are resolving the users in your $User (hidden view in Notes) against the users in the groups you have selected to migrate. If we cannot find the user in this view they will be marked as unresolved users and will not migrate as part of the group. (Note: You can easily tell which groups have members that have not resolved by the red X notifying you that you have unresolved members in your groups)

* Note: You can review the log file located in your install/logs directory to see which members did not resolve within your group. (e.g. C:\Program Files\CMT Universal\Logs)

* If you click on Refresh Group List again (having groups already imported) will be prompted with a message box stating ‘You already have group information imported. Would you like to replace this information (reset all groups), or updated the information (e.g. last modified date and member list?) Choose Yes to replace, No to update:

* Note: If you choose 'Yes', all of the current group info will be discarded and replaced by the current info from the NAB (use this to reset all your groups to 'ready for migration'). If you choose 'No', only the 'last updated' time and member list will be updated.

5.) Click on Migrate Groups
* All members are then migrated into the groups within LDAP

6.) Migration Complete