I cannot seem to find a straight answer on this subject. The documentation does not clearly spell it out or I'm missing it.
The synchronization agreement specifies a time for synchronizing to begin and a period for re-synchronizing that can be specified in hours, days, weeks, or months (with a minimum value of 6 hours). A synchronization agreement can also be set up to run only once at a specific time.
When synchronization is enabled for the first time on a Unified CM publisher server, user accounts that exist in the corporate directory are imported into the Unified CM database. Then either existing Unified CM end-user accounts are activated and data is updated, or a new end-user account is created according to the following process:
1. If end-user accounts already exist in the Unified CM database and a synchronization agreement is configured, all pre-existing accounts that have been synchronized fromLDAPpreviously are marked inactive in Unified CM. The configuration of the synchronization agreement specifies a mapping of anLDAPdatabase attribute to the Unified CM UserID. During the synchronization, accounts from theLDAPdatabase that match an existing Unified CM account cause that Unified CM account to be marked active again.
2. After the synchronization is completed, anyLDAPsynchronized accounts that were not set to active are permanently deleted from Unified CM when the garbage collection process runs. Garbage collection is a process that runs automatically at the fixed time of 3:15 AM, and it is not configurable.
3. Subsequently when changes are made in the corporate directory, the synchronization from Microsoft Active Directory occurs as a full re-synchronization at the next scheduled synchronization period. On the other hand, the Sun ONE directory products perform an incremental synchronization triggered by a change in the directory. The following sections present examples of each of these two scenarios.
Any locally created user(s) will at next sync be converted to a LDAP synced user if the account information is a match. As such it would be removed from CUCM if it’s deleted from the directory. A local user that doesn’t meet this would not be removed. Although your question is somewhat backwards as user information has to be a match for the directory information to overwrite the local information, if there is no match it’s never even an issue from the start.