04-28-2021 04:11 AM
Hello Guys,
We have CUCM 12.5 and LDAP sync is configured with MS AD 2016 server. As 2016 is end of Life we are planning to migrate to 2019 which is exact replica of the 2016 server.
We are using LDAP for Jabber Login for few users.
How this can be done without impacting Jabber users login experience ?
Will there be any configuration changes needed on the end user page after changing LDAP IP on CUCM. For e.g Device Association, Primary Extension, Roles and Groups, Home Cluster Check Box etc ? or these fields will remain as it is ?
Are there any specific steps to be followed ?
04-28-2021 05:59 AM
Since its migration 2019 which is exact replica of the 2016 server, There won't be any issue with your end users configurations.
04-29-2021 08:21 AM
I would advice you to add the new AD sever as a second server to the LDAP sync. Then when it has synced you should be able to remove the old one. As Nithin wrote as the user information are the same it should not be an issue. CM uses a per user unique value for the identification of the user, at the moment I don't recall what it's named, but it's not the actual user name as such.
04-29-2021 11:11 PM
What about CUCM specific user parameters, Which are not coming from AD Server. For e.g, Device Association, Home Cluster Check Box, UC Service Check Box, Roles and Group Assignment, Primary Extension assigned on end user page.
Will these parameters will remain as it is for all end users ?
04-30-2021 12:30 AM
No it won’t remove those configurations.
04-30-2021 02:42 AM - edited 04-30-2021 02:42 AM
This will not be affected.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide