When a CUCM server performs its scheduled LDAP synchronization (22:00 on 4 Mar), the account that no longer exists in Active Directory is not deleted—CUCM only flags the end-user record as “Inactive LDAP Synchronized User.” A separate maintenance task, Garbage Collection, permanently removes those inactive LDAP-synchronized users only after they have been inactive for at least 24 hours. Garbage Collection runs once a day at its default time of 03:15. Therefore, the first run that meets the “>24 hours inactive” requirement is 03:15 on 6 Mar (24 h after 22:00 on 4 Mar), which is why the administrator must wait until then.

A. 22:00 4 Mar merely marks the user inactive; deletion is not performed during LDAP sync.
B. 22:00 5 Mar is another sync; user is already inactive and still not deleted.
D. 03:15 5 Mar occurs <24 h after inactivation, so Garbage Collection skips the record.

1. Cisco Unified Communications Manager Administration Guide, Release 12.5(1), “Garbage Collection,” p. 91: “…removes inactive LDAP-synchronized end users that have been inactive for more than 24 hours…default run time 03:15.”

2. Cisco Unified Communications Manager Features and Services Guide, Release 12.5(1), Chap. 6 “LDAP Synchronization and Authentication,” p. 6-7: “If a directory user is removed, the next sync sets the CUCM end user to inactive; the record remains until garbage collection purges it.”

3. Cisco Unified Communications Manager System Configuration Guide, Release 14, Sect. 4-5: “Garbage collection permanently deletes inactive users (>24 h) each day at 03:15 by default.”