Coexistence Manager for Notes [CMN] and duplicate objects in the Notes and Exchange directories (17056)

When performing a migration with Migrator for Notes to Exchange [MfNE], you may find that duplicate objects exist in either the Notes directory or the Exchange Global Address List. These duplicate entries often confuse the end users who do not know which object to send mail to internally. This solution addresses the conditions under which such duplicate objects are created.

MfNE never creates duplicate objects in the Notes directory or Exchange GAL. These objects are created by the connector in certain conditions, as discussed in the resolution section of this solution.

When a Notes Connector in CMN is present and is set to sync in both directions (import/export containers are both specified in the connector), then you may see duplicate objects under the following conditions:

1. When the connector is set to sync from Exchange, back to Notes, and an AD object (with the same name as in Notes, ie, the notes equivalent object in Exchange) is mailbox enabled by Notes Migrator after an AD object merge process, the Notes connector will create a contact in the source notes directory. This will result in two objects/addresses in notes for that user; one for the notes mailbox, and one for the connector created contact that links back to the exchange mailbox equivalent.

2. When the connector is set to sync from Notes to Exchange, and the admin batch migration process is run, the connector will extract the users from the Notes directory during a sync, and create a new contact in the Exchange GAL for every Notes user that was migrated using Notes Migrator.

To resolve the issue of duplicate objects in Notes and Exchange as per the points above, Notes Migrator contains the following features (listed in order):

1. Setting Notes Visibility: This can be used to hide the mailbox in your Notes Address book, such that only the notes contact referencing the Exchange equivalent mailbox will be present in the Notes directory. When visibility is set to None for that user it will hide their mailbox so that when a user picks the mailbox out of the address book, it will be the correct contact to the Exchange mailbox.

For instructions on how to create the group to be used for visibility options please refer to Solution 13746 on our website that discusses this:
http://support.quest.com/eSupport/solution.asp?WAid=268456715

2. Disable Foreign Directory sync: This tells Note Migrator to prohibit the Microsoft Notes connector from extracting the users from the notes directory during the directory sync process. When this is in place, duplicate objects will not be created in Exchange, and the end user is able to send mail directly to the exchange mailboxes once migrated.

In summary, it is important to realize that Notes Migrator never creates duplicate objects in either the Notes or the Exchange directories. If you see this in your environment, it is most likely due to the notes connector creating these objects.