I'm testing a custom Active Directory attribute in a single-domain-controller test environment. I have Schema Admin privileges and followed the documented process: obtained a private enterprise number from IANA, enabled schema updates in the registry, created the attribute, created an auxiliary class containing that attribute, added the auxiliary class to the User class, updated the schema through ADSI Edit, and restarted the domain controller. However, the attribute still doesn't appear in the user properties. Is there another step required, or is there a separate way to make custom attributes visible in the management tools?
2 Answers
The procedure you described is essentially the standard approach, and there isn’t much difference between the commonly referenced guides. I’d first verify the attribute’s schema definition, including its syntax, OID, and whether it is marked for use. Then inspect an existing user object directly instead of relying on the normal property-page tabs; the graphical interface does not automatically create a field for every schema attribute.
The schema changes may already be working, but custom attributes usually don’t appear automatically on the standard user-properties tabs. In Active Directory Users and Computers, enable Advanced Features and check the Attribute Editor tab on a user object. You can also verify the attribute and auxiliary class directly in ADSI Edit or with PowerShell. If it still isn’t listed there, confirm that the auxiliary class was added to the actual User class and that the schema cache and replication have finished.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures