Created attachment 7671 [details]
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.
This is a reasonable request, I'll see what I can do.
I think, this are the most important attributes that should also be migrated:
unixHomeDirectory (this was homeDirectory in s3 LDAP)
mail (we have multiple mail attributes here for most users, not just one)
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)