Univention Bugzilla – Bug 40938
uid != sAMAccountName after renaming Windows client via Windows
Last modified: 2016-03-23 18:51:36 CET
After renaming a Windows client via Windows the new sAMAccountName is not synchronized to the corresponding uid attribute in OpenLDAP. As mentioned in Bug 39802 Comment 8 this causes a smbd coredump whenever the client logs on to samba, e.g. to update its machine GPOs. Basically the renamed account is non-existent as a Posix account. So in the concept of a UCS domain the machine is not properly joined any longer. Workaround (at the time of writing): ## If "$newname" is the new client name without trailing $-sign: udm computers/windows modify --dn "$windowsclient" --set name="$newname"
*** This bug has been marked as a duplicate of bug 37388 ***