Hello @stephdl, first a question: I recognised that in your sample screenshots under Shared Folders the name changed from ‘stephane de labrusse’ to ‘stephane’. Is this relevant here or just any sample?

yes you are right. Same issue here on my installation, but I did not take care so much about it.
Yes, I usually write the full name into this field as ‘surename forname’. So your change in the config is an advantage, I thnik this is the right way to go.

but it assumes that when you create an user in the nethgui interface, you put in the name field, the full name of your user

is it the case ?

Actually, the Nethserver gui interface is lacking. After you create a user with it, and when using AD, you definitely want to change that users properties. (Name, last name, full name, email, homedir, profile path, etc.) Actually, you do not even want to create the user with the Nethserver gui, as you cant set half the needed values. The only thing it saves you from doing, is setting the shell to /bin/bash by enabling you to enable ssh.

This is not a shortcoming imho. Nethserver does not act as the AD. A container running in it acts as the AD. You want to administer the AD with AD tools. You create users in AD with ADUC.

I am very opensource minded, but I also need to employ M$ engineers for the day-to-day stuff I do not want to have to think about beyond design. Having to make them do things in two places sucks. Trying to recreate ADUC is senseless … it works, why replace it. If you run windows clients you better have one yourself.

To get back to the question: the name field in Nethserver translates to a bunch of properties in AD, skewing the displaying of that information. I would re-assess the need by going into ADUC and setting the AD properties like you would expect (fill as much as possible with correct information) and see how much of the issue remains, and then fix what is left. The current way Nethserver creates an AD user, is not realistic compared to real life scenarios. Setting these AD properties, actually has effect.

I think it’s good to change the sogo field because it makes sense to see the full name instead of just the username.

stephdl:

Netgui doesn’t need phpldapadmin to create object in samba4, it does it by specific command relative to samba-tools

I don’t know what’s the better way here:

With phpldapadmin you can change any field, more than with RSAT tools but you have to know what you’re doing. It’s ready to work and nothing has to be done, no reinvention of wheel.

On the other hand as mentioned above, it would be nice to have some more important fields in Nethgui (mail, mobile, photo(nextcloud uses it), etc) so it would be a simple Nethserver approach having the fields one REALLY needs in comparison to RSAT or phpldapadmin where you have fields you may never use.

I know anything could also be done just with RSAT and in 90% of the cases you want to have a Windows PC with RSAT to manage AD but there are also some requests in the forum to manage AD things with NS instead of with RSAT/ADUC, just not to be dependent on M$ tools when configuring the server.

planet_jeroen:

I would re-assess the need by going into ADUC and setting the AD properties like you would expect (fill as much as possible with correct information) and see how much of the issue remains, and then fix what is left. The current way Nethserver creates an AD user, is not realistic compared to real life scenarios. Setting these AD properties, actually has effect.

Yes, I think this is the way to go to find the compromise of what’s really needed in NethGUI to satisfy AD users.