The following table summarizes the corrective actions that you must take to resolve conflicts that the wizard could not resolve automatically
| Failed or Unresolved Operations | Description | Corrective Action |
|---|---|---|
| Conflicting DNs | More than one MiCollabUser has a DN that matches one of the DNs for a single MiVoice Business User |
In this scenario, there are two or more MiCollab users that each have one or more DNs that match up with the DNs on a common MiVoice user. For example, on the MiCollab there is User ‘X’ with DN ‘1000’ and User ‘Y’ with DN ‘2000’. On the MiVoice Business there is User ‘Z’ with DNs ‘1000’ and ‘2000’. You need to determine which users should own each DN. If MiCollab User “X” should own DN ‘1000’ and User “Y” should own DN ‘2000’, reach through to the MiVoice Business system administration tool and disassociated one of the DNs from User “Z”. On a subsequent reconcile, the result would be that User “Z” is merged with one of the MiCollab users and DN ‘1000’ remains associated with User “X” and DN ‘2000’ remains associated with User “Y”. If you want all three of these users merged into one user, then DN ‘1000’ and DN ‘2000’ on the MiCollab have to both be associated with either User “X” or User “Y”. Then, when the reconciliation is repeated, there will be one user that owns both phones (in both the MiCollab and in the sharing network). |
| Accented characters in Department or Location | MiCollabDepartment or Location names cannot contain accented characters |
Remove accented characters:
|
| MiCollabusers or templates refer to departments or locations that contain accented characters | If a user or template in MiCollab refers to a department or location that contains accented characters, then the wizard cannot automatically resolve those users and templates. |
Remove accented characters:
|
| MiCollab users or templates refer to a role that contains accented characters | If a user or template in MiCollab refers to a role that contains accented characters, then the wizard cannot automatically resolve those users and templates. |
Remove accented characters:
|
|
Unresolvable User Operation Users from this MiCollab that cannot be resolved because they have a login ID conflict with a user in the sharing network: |
Example: * John Rae -> John R Teleworker, John Rae MiCollab has two entries:
But MiVB has three entries:
|
Pair users on login ID (providing that the first name and last name are identical and that the DN pairing is also identical). |
| User entry cannot be aligned due to configuration issue |
A MiCollab user and a MiVoice Business user are matched based on DN, but the hosting network element for each user is different. For example: MiCollab user Johnny has DN 1000 that is hosted on MiVoice Business A. The matching MiVoice Business user John has DN 1000 BUT the phone is hosted on MiVoice Business B. |
Change the hosting element of one of the user entries to match the other. |
| User entry cannot be aligned due to configuration issue | A MiCollab user is paired with multiple MiVoice Business users, but one of the MiVoice Business users has a phone with a secondary network element, which is a MiVoice Business that is NOT sharing. | Change the secondary element to that of one in the sharing network. |
| MiVoice Business users are unresolvable. | The MiVoice Business users are sharing a phone. | MiCollab does not support the sharing of phones. On the MiVoice Business , assign the users with different phones. |