Resolve User ID Conflicts
The system uses the Microsoft Exchange LegacyDN as a unique user identifier when processing mail. When moving users between Administrative Groups or Exchange Organizations, the Exchange LegacyDN may change. To ensure that retained mail remains associated with a user as the LegacyDN changes, the SyncManager checks for multiple instances of the same primary email address on each directory sync.
When SyncManager encounters more than one instance of a primary email address, GFI OneConnect sends out a notification to persons to the fault notifications recipients.
In most cases, the instances of the primary email address refer to the same, single end user, and by resolving the conflict, you ensure that mail collected for the first instance is associated with the second instance.
NOTE
When the same primary email address belongs to two different users, you must assign a new primary email address to either one of the users. For example: user Joe Smith (jsmith@organization.org) left the organization, but his mail was still subject to retention policies. A year later, you hired Jill Smith, and assigned the email address jsmith@organization.org. SyncManager would detect the conflict, but you would not want to resolve it using the methods described here, as that would associate Joe’s retained mail with Jill’s new mail. Instead, you must assign a new primary email address to either Joe or Jill.
User ID conflicts can be resolved automatically or manually. To configure the method to use for resolving user ID conflicts:
- Login to GFI OneConnect with an administrator account.
- From the top-right menu, navigate to Manage > ContinuityA feature provided by GFI OneConnect that queues the emails sent and received in a Data Center and ensures that your organization can keep the mail flow even when the email infrastructure is down..
- From the Continuity Admin ConsoleA web interface for adminsitrators to manage and configure GFI OneConnect., go to System Settings > User ID Resolution.
- In the User Resolution Type drop-down, select the resolution method.
| Method | Description |
|---|---|
| Manual | Each User ID conflict must be addressed manually by an administrator through the Continuity Admin Console. This is the default setting. For more information refer to Resolve User ID Conflicts Manually. |
| Primary Email | All multiple instances of a primary email address are presumed to be the same end user, and all mail is associated with that user automatically without administrator intervention. |
| All Aliases |
If all aliases in the mailbox of the first instance of the primary email address are present in the second, the primary email addresses are presumed to be the same user, and the conflict is resolved automatically. The second may have additional aliases as well, but each of the primary aliases must appear. If only some or most of the primary ones are present, the action fails and an administrator must address the conflict manually in the Continuity Admin Console. |
| Active DirectoryA technology that provides a variety of network services, including LDAP-like directory services. Attribute | Choose a custom or default attribute from the ones synced from Active Directory. If the attribute values match, the primary email addresses are presumed to be the same user, and the conflict is resolved automatically. Some examples might be Employee Number, User ID or phone number. |
- Click Submit.