Bug 40938

Summary:	uid != sAMAccountName after renaming Windows client via Windows
Product:	UCS	Reporter:	Arvid Requate <requate>
Component:	S4 Connector	Assignee:	Connector maintainers <connector-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3
Version:	UCS 4.1
Target Milestone:	---
Hardware:	Other
OS:	Linux
See Also:	https://forge.univention.org/bugzilla/show_bug.cgi?id=39802
What kind of report is it?:	---	What type of bug is this?:	---
Who will be affected by this bug?:	---	How will those affected feel about the bug?:	---
User Pain:		Enterprise Customer affected?:
School Customer affected?:		ISV affected?:
Waiting Support:		Flags outvoted (downgraded) after PO Review:
Ticket number:		Bug group (optional):
Max CVSS v3 score:

Description Arvid Requate

2016-03-23 18:49:27 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"

Comment 1 Arvid Requate

2016-03-23 18:51:36 CET


*** This bug has been marked as a duplicate of bug 37388 ***