Unity Connection 8.5, LDAP and Windows 2000 AD

[gmgarrian]

Are there any known issues configuring LDAP synchronization between UCONN 8.5 and Win2k AD?

This is the last question I need answered prior to a cutover.  From what I can find I don't think there will be an issue, but I always like confirmation.

Thanks!

[Bradford Magnani · Accepted solution]

Hi,

Here are the LDAP requirements, they're not OS specific in our documentation.

http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html#wp360078

Hope that helps,

Brad

[gmgarrian]

Thanks for the info!

I have a couple of general questions regarding LDAP and UCONN.

Once I set this up, what happens to existing UC accounts that have matching yet unsynchronized AD accounts?

What is the proper syntax for the pointing to a specific OU in AD?

If this is setup incorrectly, or if the AD accounts are not formatted properly, could this screw up the existing UC accounts?

Thanks!

[Bradford Magnani]

The only way UC will synchronize users with the LDAP directory is if they've been converted to LDAP users (either via Bulk Edit or the radio button on individual User Basics page) and the criteria specified in the LDAP agreement matches, ie; alias.  An example search base syntax would be something like CN=Users,DC=company,DC=com.  There are many places online that have this AD syntax.  The design guide has more information about the sync behavior and some requirements:

http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg040.html#wp1068361

•  The mapping of LDAP directory attributes to Connection fields

Brad