You are integrating an existing Cisco Unity Connection user with an existing LDAP user. However, the user’s Unity Connection Alias field does not match the LDAP user ID.
Which of the following will most likely occur if you attempt to use the BAT to import the Unity Connection user without updating the Alias field? (Select the best answer.)
- A new Unity Connection user account will be created from the LDAP account.
- A failed objects report will be created that contains information about the update attempt.
- The Unity Connection user’s alias will be updated to match the LDAP user’s alias.
- The LDAP user’s alias will be updated to match the Unity Connection user’s alias.
Most likely, a failed objects report will be created that contains information about the update attempt. The Bulk Administration Tool (BAT) can be used to add, update, or remove users from Cisco Unified Communications platforms. When you integrate an existing Cisco Unity Connection account with an existing Lightweight Directory Access Protocol (LDAP) user, you must first export the LDAP user information to a comma-separated values (CSV) file. Next, you must import the CSV file into Unity Connection by using the BAT. The LDAP user ID field that is specified in the CSV is what the BAT will use to search the Unity Connection database. If the BAT finds no matching Unity Connection user alias, the action will fail and a failed objects report will be created.
If you want to integrate an existing Cisco Unity Connection user with an existing LDAP user, you should first ensure that the Alias field in Unity Connection matches the user ID in the LDAP directory. If the values do not match, you should modify the user’s Alias field in Cisco Unity Connection.
No new Unity Connection account will be created from the LDAP account. In order to create a new Unity Connection user from a CSV import, you must specify that you want to add the users instead of update existing records.
The Unity Connection user’s alias will not be updated to match the LDAP user’s alias. Because the Unity Connection user alias does not match the LDAP user ID, the BAT will not be able to locate a user to update.
The LDAP user’s alias will not be updated to match the Unity Connection user’s alias. The BAT import process updates records in the Unity Connection user database, not the data from the CSV, which was exported from LDAP.