Migration of MiVoice Business IDS to MiCollab IDS must be performed manually. You must copy the IDS settings from the MiVoice Business IDS forms to the corresponding fields in the MiCollab IDS Connection and Attribute Mapping pages.
Review the General Guidelines and Limitations.
Log into MiVoice Business System Administration Tool.
Display the MiVoice Business IDS Connection form. The following table maps the MiVoice Business IDS settings to the corresponding MiCollab IDS connection parameters..
MiVoice Business IDS Connection Settings |
MiCollab IDS Connection Parameters |
Directory Server Type |
Directory server type |
Client Network Element |
|
Directory Server |
Primary directory server |
|
Secondary directory server |
Domain |
Domain |
User |
Distinguished name |
User Password |
Password |
LDAP Port |
LDAP port |
GC LDAP Port |
Global catalogue port |
Connection Method |
Connection method |
Default Query String |
Default Query string |
Search Scope |
Search context |
Maximum Query Time |
|
Query Page Size |
Query page size |
Chase Referral |
Chase LDAP referrals |
Search Context |
Search context |
Default Container to Add New Users on DS |
|
Last Sync Time |
Last synchronization |
Display the MiVoice Business "User Service to LDAP" form. The following table maps the MiVoice Business and MiCollab IDS attributes to the corresponding directory service attributes.
MiVoice Business IDS Attribute |
Directory Server Default Attributes |
MiCollab Attribute |
|
COMMON ATTRIBUTES |
|||
Company |
company |
Company |
|
|
(unmapped) |
Direct Inward Dial |
|
Department |
department |
Department |
|
Distinguished Name |
distinguishedName |
Distinguished Name |
|
|
|
|
|
First Name |
givenName |
First Name |
|
Home Element |
ipPhone |
Home Element |
|
Language |
preferredLanguage |
Language |
|
Last Name |
sn |
Last Name |
|
Location |
physicalDeliveryOfficeName |
Location |
|
Login |
samAccount Name |
Login |
|
Directory Number |
telephoneNumber |
Primary Phone Directory Number |
|
Role |
employeeType |
Role |
|
User ID |
objectGUID |
User ID |
|
|
|
MiCollab ONLY |
|
|
|
otherTelephone |
Secondary Phone Directory Number |
|
|
mobile |
Mobile Phone Directory Number |
|
|
objectClass |
Object Class |
MiVoice Business ONLY |
|||
Secondary Element |
otheripPhone |
Note: The MiVoice Business Directory Number field may include the Primary Node ID in the directory number (PNI + DN). MiCollab does not accept the PNI. Either remove the PNI from the directory number or create a new field that only has the directory number and map to MiCollab.
Ensure that the Login field in the MiVoice Business is mapped to the samAccount Name field.
If IDS is enabled on any MiVoice Business platforms or applications, run a synchronization operation with the directory server to ensure that the MiVoice Business platforms, applications, or both have the latest updates from the directory server. Refer to Integrated Directory Services in the MiVoice Business System Administration Tool online help for instructions.
Note: You must resolve the detained updates from the MiVoice Business on the associated MiCollab. If there are multiple MiCollab systems on site, ensure that you make the required updates on the correct MiCollab.
Disable MiVoice Business IDS:
Log into the MiVoice Business System Administration Tool.
Access the Network Element Assignment form and delete the directory server.
In the USP Network Element tab, disable Single Point Provisioning.
Create a MiCollab synchronization account on the directory service domain. The account must have read access.
If Active Directory Authentication is required, ensure that a valid Certificate Authority (CA) has been configured for Active Directory. If authentication is not required, you assign users new passwords on MiCollab using roles and associated user templates.
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.
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.
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.
Create a connection to the directory server:
Under Configuration, click Integrated Directory Service.
Click Add connection. The Add Integrated Directory Service connection page opens.
Complete the fields to create a connection. When you configure the IDS Connection Parameters Current MiVoice Business-IDS Connection Values" that you recorded in the table above into the MiCollab IDS Connection page. See Manage IDS Connections for field descriptions.
If Active Directory Authentication is required, the Synchronization option must be enabled. Also, set the Connection Method to either TLS or TSL/SSL. The Connection Method cannot be Unsecured.
Note: To use SSL/TLS for IDS, LDAP over SSL must enabled on the active directory server. See the following links for more information:
Click Save. MiCollab verifies the connection parameters and indicates if any errors are present.
Configure Active Directory Authentication if required.
Check the Enable authentication box below the domain. You can only enable authentication on a single domain. So, if you want to select a different domain, you must first disable the currently selected domain.
Note: You can connect the Active Direcory Authentication to a Global Catalogue on the domain controller. If multiple connections are used, and if those connections point to domains which are under the same forest, you can configure one connection to use the global catalogue. With global catalogue enabled, all users from all connections under the same forest should be able to authenticate. Note that using global catalogue limits the fields that can be used for synchronization.
Secure authentication requests are required as part of the IDS connection.
Click Save.
Configure the IDS Attribute Mappings. Transfer any custom Directory Server Attributes into the MiCollab IDS Attributes Mapping page.
lf 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:
Under Applications, click Users and Services.
Locate the user using the Search function.
On the User tab in the Personal Information section, clear the IDS Manageable box.
Click Save.
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.
Under Configuration, click Integrated Directory Service.
Click Edit next to the directory service connection. The Manage IDS connections page opens.
Ensure the Re-initialize on next cycle box is clear.
In the Schedule field, set the schedule using the drop-down menus.
Click Save.
Perform a full synchronization from MiCollab with the directory server database..
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.