06-26-2015 06:57 AM - edited 03-17-2019 03:29 AM
Hi,
We have a cucm cluster that is not synced with AD. The userid's are the users telephone numbers.
We now want to enable AD sync but we will use the sAMAccountName as a userid attribute. If we enable the ldap sync, the system instead of overwriting the existing users will just create new ones. That is normal since there is no association between the existing ones and the ones from AD;
BAT is giving me a lot of headaches; If I want to avoid reconfiguring the users again (not an option) I will probably need to export the existing users, modify their userid so as to match their sAMAccountName and then import them back.
But I have tested a better and faster solution for me. Just do an update query directly to the sql db and change the userid via AXL. I haven't seen any potential issue apart from the fact that I wil have to reconfigure the agent config in UCCX due to the bug CSCur94251 but I cannot avoid that whatever I do.
Has anyone tried it with success ? Can anybody think any other potential issues?
Thanks!
06-27-2015 10:17 PM
Hi,
I never tryed this, but I recommended that you make an small test before change the UserID of all your users.
My recommendation ... create a new OU, for example LAB, and insert the user TEST into it. Change one of your UserIDs from DN to TEST. Enable AD Sync only with the LAB OU. Check the result.
Hope this helps.
06-28-2015 02:44 AM
Marcelo,
Thanks for the reply. that's exactly what I have tested and I did not see any issue. Just wondering if anyone has done it before and if there is any other caveat that I cannot think of
Regards,
06-28-2015 08:15 AM
Hi,
I didn't find any issue in my researches ... as soon as you already tested that, I think you are good to go.
Best regards.
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