Migrate MiCollab with MiCollab Audio, Web and Video Conferencing IDS to MiCollab IDS

Migration of MiCollab Audio, Web and Video Conferencing IDS to MiCollab IDS must be performed manually. You must copy the IDS settings from the MiCollab Audio, Web and Video Conferencing AD/LDAP pages to the corresponding fields in the MiCollab IDS Connection and Attribute Mapping pages. Leave any MiCollab IDS fields that don't have corresponding fields at the defaults.

  1. Review the General Guidelines and Limitations for MiCollab IDS.

  2. Log into MiCollab server manager.

  3. Under Applications, click Audio, Web and Video Conferencing.

  4. Under Configuration, click LDAP Configuration.

  5. Display the Lightweight Directory Access Protocol form. Record the current MiCollab Audio, Web and Video Conferencing LDAP Configuration connection values in the third column of the following table. Use the table to match the MiCollab Audio, Web and Video Conferencing LDAP Configuration connection settings to the MiCollab IDS Connection parameters.

MiCollab Audio, Web and Video Conferencing LDAP Configuration Settings

Corresponding MiCollab IDS Connection Parameters

Current MiCollab Audio, Web and Video Conferencing LDAP Configuration Settings

Use LDAP

   

LDAP Port Number

LDAP port

 

LDAP Admin ID

Distinguished name

 

LDAP Uid Field

   

Auto Synchronize

Enable synchronization

 

LDAP Server Name

Primary directory server

 

LDAP Search Base

Search

 

LDAP Admin ID Password

Password

 

Email Domain

   

Sync Interval

Sync schedule

 

  1. Synchronize the MiCollab Audio, Web and Video Conferencing database with the directory server database.

  2. Disable IDS (LDAP Integration) for the MiCollab Audio, Web and Video Conferencing application.

  1. On MiCollab in the Network Element tab of the Users and Services application, disable Single Point Provisioning.

  2. Create a MiCollab synchronization account on the directory service domain. The account must have read access.

  3. If LDAP Authentication is required, ensure that a valid Certificate Authority (CA) has been configured for Active Directory. If LDAP Authentication is not required, you assign users new passwords on MiCollab using roles and associated user templates.

  4. On the directory server, ensure that the user data fields contain entries for the following attributes: samAccountName, givenName, sn, and distinguishedName. Otherwise, failed update errors are generated on MiCollab during the synchronization. If an employeeType field is not specified the entry is sent to the detained queue.

  5. In the MiCollab Users and Services application, create user templates for the various roles in the enterprise. In the templates, assign the phone and application services that you want to apply to the user data that is obtained from the directory server. In the templates, also set a password policy for the user data. You have the option of creating these templates from the UCC default templates.

  6. In the MiCollab Users and Services application, create roles that correspond to the employeeType attribute entries on the directory service. You can create these roles from the UCC default roles. Note that when users are obtained from the directory server, if a user entry has a blank employeeType field, the update is sent to the detained user updates queue.

  7. Create a connection to the directory server:

  1. Configure Active Directory Authentication if required.

  1. If your server is using the default LDAP attributes, you should not need to modify the IDS Attribute Mappings. However, if your server is using non-default LDAP attributes, you must modify the associated attribute mappings.

  2. By default, user service data and Active Directory authentication are synchronized for all users. Specify any user records that you do not want to receive changes from the directory service. To prevent a user record from receiving updates from the directory server:

  1. Schedule synchronizations with the directory server database to occur on a regular basis during off-business hours (for example: daily at 12:00 am). These re-occurring synchronizations keep the MiCollab database up to date with database changes that are entered on the directory server.

  1. Perform a full synchronization from MiCollab with the directory server database.  The user entries are not distributed to the MiVoice Business because SPP is disabled.

  2. Resolve any detained IDS updates on MiCollab. After the full synchronization is complete and you have resolved the detained updates, both the MiCollab and MiVoice Business databases match the directory server database.