You can set up to 5 sync OUs, you can just point to individual OUs and then start changing them to the parent OUs to sync more users.
You can also point to the root and get all at once, what you sync depends on what OUs you're pointing to.
The problem here is that unless the sync finds the same userID in the LDAP, users that do not exist within the sync OUs will be deleted.
If Jdoe is not within the OUs you want to start synching he'll be deleted, once you set the OU where Jdoe is, he'll be synched again... but as a new user and all his config will be gone.
About the userIDs not being the same, the one from CUCM will be gone, the new one from LDAP will be added.
For AD deployments, the ObjectGUID is used internally in Unified CM as the key attribute of a user. The attribute in AD that corresponds to the Unified CM User ID may be changed in AD. For example, if sAMAccountname is being used, a user may change their sAMAccountname in AD, and the corresponding user record in Unified CM would be updated.
javalenc, if we migrate from one AD to another and the new userIDs are different, is it correct that the only way to preserve phone to user association is to export BAT users before migration, do the migration, update the CSV file with the new user IDs (manually), and then import the BAT file to update the new end users? Finally, the speed dials and call forward settings can not be recovered, is that correct?
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...