We just ran into the behavior with some agent username changes last week,
and it was not even LDAP related - the technician was just trying to be
helpful and update some local end user id's for consistency and didn't
think that change needed any pre-testing. When he noticed it, he changed
all the
CUCM doesn't delete the users when they are marked inactive. you can fix
the LDAP agreement, resync and get them back if you get it fixed before the
garbage cycle clears them out.
this is really an issue for the UCCX team, they should handle user changes
in CUCM more gracefully. This is also
This is related to my post I just made on UCCX and LDAP via CUCM.
I also just found out that a CUCM with an already synced user database
behaves in the following two ways:
1. If you modify the filter such that it matches 0 records, the sync
doesn't happen at all. No users are marked as
