Bug 9009 - CN attribute on migration
CN attribute on migration
Status: ASSIGNED
Product: Samba 4.0
Classification: Unclassified
Component: Tools
unspecified
All All
: P5 enhancement
: ---
Assigned To: Andrew Bartlett
samba4-qa@samba.org
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-26 20:19 UTC by Marc Muehlfeld
Modified: 2012-06-29 14:26 UTC (History)
0 users

See Also:


Attachments
Screenshot (62.56 KB, image/png)
2012-06-26 20:19 UTC, Marc Muehlfeld
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Muehlfeld 2012-06-26 20:19:14 UTC
Created attachment 7671 [details]
Screenshot

During the migration process (last tested with beta2), for users, the CN and name attribute is filled with the username. One of this two attributes is also the name that is visible in the list of the AD user/computer tool on windows.

But if I add a new user using the AD user/computer tool, then the CN and name attribute is filled with the value of the field "full name" (which is written to "display name" in LDAP).

Then I have the migrated users showing in the list by username in the list, mixed with the later added users showing by the "display name". This makes it confusing if you look for an account

As workaround I can fill "full name" with the username on creation and after saving the new account, edit it and change the "display name" field to the real full name again.

But maybe it's a good idea to migrate the users in a way where the CN and name attribute is filled with the "display name" attribute of the s3 LDAP (if not present you sill can use the username as fallback).

I added a screenshot of ADUC with a migrated and new added account.
Comment 1 Andrew Bartlett 2012-06-27 08:37:12 UTC
This is a reasonable request, I'll see what I can do.
Comment 2 Marc Muehlfeld 2012-06-29 14:26:05 UTC
I think, this are the most important attributes that should also be migrated:

unixHomeDirectory (this was homeDirectory in s3 LDAP)
displayName
homeDrive
mail (we have multiple mail attributes here for most users, not just one)
profilePath
scriptPath (path to logon-script)
userWorkstations (machines from where the account can log in)




But this ones will be helpfull for many users too (like we use this attributes for our internal addressbook)

co (Country)
company
department
description
givenName
l (city)
postalCode
sn (lastname)
streetAddress
telephonNumber
title