Because an LDAP agreement cannot be edited after its initial sync, fixing a wrong filter or attribute mapping in practice means creating a new agreement (or using Bulk Administration) rather than editing the existing one.
inferred · Checked 2026-10-02
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- LDAP directory agreement
- Deployment
- on-premises
- Region
- not restricted
- Release range
- 12.5(1) and 15 and SUs as of 2026-10-02
- Status
- inferred
- Checked
- 2026-10-02
Sources
- System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure LDAP Synchronization — Cisco Systems · tier 2 current vendor documentation · LDAP Synchronization Overview, note on edits after initial sync
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting LDAP directory sync failures in Unified CM: source note cucm-ldap-sync-troubleshooting-change-uid-new-agreement. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-ldap-sync-troubleshooting-change-uid-new-agreement
BibTeX
@misc{warmtransfer-claim-cucm-ldap-sync-troubleshooting-change-uid-new-agreement,
title = {Troubleshooting LDAP directory sync failures in Unified CM: source note cucm-ldap-sync-troubleshooting-change-uid-new-agreement},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-ldap-sync-troubleshooting-change-uid-new-agreement},
note = {Source note cucm-ldap-sync-troubleshooting-change-uid-new-agreement, checked 2026-10-02}
}