[cisco-voip] CUCM requirements for AD account import - anything else other than SN=* (non-empty) ?

Anthony Holloway avholloway+cisco-voip at gmail.com
Thu Jan 30 17:07:48 EST 2020


I think you understand it correctly.  Unless we're both wrong.

Are you using the same filter in both CUCM as the LDAP browser (can you
share it?)?  Same search base?  Same user to BIND with?  Same AD or GC
server?  Same Port?  Same TLS setting?

Do you know which user account is the anomaly?

On Thu, Jan 30, 2020 at 3:34 PM Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

>
> OK - I'm trying to reconcile accounts being imported into CUCM before I
> modify the filter we're using.
>
> I've used the base filter suggested, plus I've added the (sn=*) to ensure
> we get only accounts with non-empty last names.
>
> However, my reconciliation is off by 1 (including taking into account
> inactive LDAP accounts).
>
> CUCM: 86,636
> LDAP Browser: 86,637
>
> I could just write it off as an anomaly, but I've sync'ed multiple times
> and ran the LDAP search multiple times, and I'm pretty sure no one is
> making changes.
>
> Anyone aware of any other criteria CUCM puts on to the import process?
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200130/76848e64/attachment.htm>


More information about the cisco-voip mailing list