# Implementing MiVoice Business IDS on an SDS Network

Use this procedure to implement the IDS solution on an SDS network where user records are currently hosted on the individual MiVoice Business elements, not on OPS Manager or a directory server domain.

After completing this procedure, you will be able to synchronize user records from the directory server to the MiVoice Business elements.

NOTE: Before implementing MiVoice Business IDS, ensure that the MiVoice Business elements are part of an SDS network and have Release 5.0 or later software.

To program the MiVoice Business IDS on an SDS network:

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

   NOTE: If possible, do not use an AX Controller as the contact point.

2. 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

3. Update the LDAP attributes to match the values employed by the directory server (if necessary).

3. On each MiVoice Business element:

User and Services Configuration form

3. Review the user records, paying special attention to the IDS-Manageable flag. This flag is selected by default for all user records that have been converted to MCD R5.0. Clear the flag for user records that do not require IDS management.

4. On the MiVoice Business IDS contact point:

IDS Data Management form

4. Perform an LDIF file export.

5. Retrieve the IDSManagedUsersWithNoDomain_<date_timestamp>.ldf file.

This file lists IDS-manageable records that do not have domain data and therefore exist only on the MiVoice Business elements, not on the directory server. Note that because the user data is shared at the network scope by default, the LDIF file can contain all user records in the SDS network.

4. Review and edit the LDIF file if necessary.

5. On the directory server:

6. 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 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:\

5. i = turn ON import mode

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

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

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

9. j c:\ = save output to log file

6. On the MiVoice Business IDS contact point:

Scheduler form

6. Perform an immediate Full IDS Synchronization to associate directory server and MiVoice Business user data.

Related Topics

- Migrating from OPS Manager IDS to MiVoice Business IDS

- Troubleshooting IDS