The name of the subobject "CN=409" under CN=DisplaySpecifiers,CN=Configuration,<Domainname> is wrong. It should be "CN=407". So Active Directory Users and Computers finally shows user attributes. It's located in the file display_specifiers.ldif under setup/.
As such, I think the correct fix is to determine an automatic way to generate these for any codepage.
(In reply to comment #1)
> Looking at
> As such, I think the correct fix is to determine an automatic way to generate
> these for any codepage.
Yes, you are right. I've used the ADUC MMC on a client with German language, where the language code in the AD must be "407". Hopefully there is a way to fix this nasty issue.
I think, there could be now the right time to add more display specifiers. I see for example, that now also the MMC AD Sites and Services begins to work correct.
For the codepage problems, I would copy the same DS under each important codepage for the moment, until we have found a better solution. But in fact does Microsoft generate them automatically?
Created attachment 2844 [details]
I've enhanced the display specifiers ldif file to support more editing in MMC with classes, that exist in SAMBA4's schema.
Since it's not really a bug, I'll mark it as a feature request.
The problem with the codepages seems to be fixed now. Andrew, but have you checked my enhancement patch here?
I think we fixed now the problem with the display specifiers. So, should I close this bug? What do you think Andrew?
Okay, I'm going to close this.
I reopen this bug since it deals with the display specifiers which still is an issue for us. I'll close this when we have *all* display specifiers integrated in SAMBA 4.
All display specifiers imported - therefore fixed.