# Migrating from OPS Manager IDS to MiVoice Business IDS

Use this procedure to migrate user records from OPS Manager to the MiVoice Business IDS solution.

After completing this procedure, you will be able to synchronize user records from the directory server to the MiVoice Business elements, and you will no longer be required to use OPS Manager for directory management.

NOTES

- Use the standard tabs in the Active Directory Users and Computers (ADUC) management console to configure IDS managed data. Do not use the OPS Manager Active Directory snap-in within ADUC because it is not supported in the MiVoice Business IDS solution.

- Before implementing MiVoice Business IDS, ensure that the user data on directory server and the MiVoice Business elements are synchronized using OPS Manager.

To migrate from OPS Manager IDS to MiVoice Business IDS:

1. Select one MiVoice Business element to connect to the directory server. This element is the MiVoice Business IDS contact point.

2. Ensure that all elements have MCD Release 5.0 or later software.

3. On the MiVoice Business IDS contact point:

License and Option Selection form

- Enable the Integrated Directory Service option.

Network Elements form

- Add the directory server as a network element.

IDS Connection form

- Configure the IDS connection for the directory server.

User Service Data to LDAP Attributes Mapping form

Do the following:

- use the Export function to save the current user service data to LDAP attribute mapping file (Map1.csv)

- use the Import function to import the user service data to OPS IDS attributes mapping file (available from this link or from Mitel Technical Support).

Scheduler form

- Perform an immediate Full IDS Synchronization. This associates the MiVoice Business User ID with the directory server Global Unique ID (GUID) for each user.

IDS Data Management form

- Resolve all failed updates. Do not delete any detained updates.

User Service Data to LDAP Attributes Mapping form

- Import the user service data to LDAP attribute mapping file (Map1.csv) that was saved in the earlier step.

IDS Data Management form

Do the following:

- Click LDIF File Export.

- Define the location where you wish to export the files.

- Click Export to save the following files:

IDSManagedUsersWithDomain_<date_timestamp>.ldf — contains user records that exist on MiVoice Business and AD.

IDSManagedUsersWithNoDomain_<date_timestamp>.ldf — contains IDS-Manageable records that exist on MiVoice Business only.

NonIDSManagedUsers_<date_timestamp>.ldf — contains non-IDS-Manageable records.

4. On the directory server:

- Use the LDIFDE tool (included with Windows Server 2003 and 2008) to transfer the LDIF file onto the directory server. This operation adds the IDS-Manageable user records/mapping from the MiVoice Business element to the directory server. The following is an example of the command used to perform this task:

LDIFDE -i -f exportfile.ldf -k -s domain1.com -j c:\

1. - i = turn ON import mode

   - f filename = input or output filename (ex. exportfile.ldf)

   - k = the import will go on ignoring 'constraint violation' and 'object already exists' errors

   - s servername = the server to bind to (ex. domain1.com)

   - j c:\ = save output to log file

5. (Optional) To add new users from the MiVoice Business systems:

6. Import the IDSManagedUsersWithNoDomain_<date_timestamp>.ldf file to the directory server. This adds new user records using the current attributes mapping. The directory server creates its own object GUIDs for the new users; it does not employ the User IDs provided by the MiVoice Business systems.

7. Go to the Scheduler form ( ) on the MiVoice Business IDS contact point and perform an immediate Full IDS Synchronization. This updates the MiVoice Business User ID with the directory server Global Unique ID (GUID) for each user.

## Data Example

Note that the migration strategy should handle the scenario outlined below. Before migrating to MiVoice Business IDS, make the following user data on the active directory server is in sync with the MiVoice Business data.

Sample User: James Martin

Active Directory attribute values | MiVoice Business attribute values
ObjectGuid = Guid1 | User ID = Guid2 (the user ID and object Guid do not match)
GivenName = James | First Name = James
Sn = Martin | Last Name = Martin
MitelIDSNumber = 1001 | DN = 1001
Mitelidshomeelement = ipbx71 | Home Element = ipbx71
Telephone Number = (blank) | …
PhysicalDeliveryOffice = (blank) | …

Related Topics

- Implementing MiVoice Business IDS on an SDS Network

- Troubleshooting IDS