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.