I am using windows server 2008. I have a domain with one domain controller (this is a dev environment). I edited the AD schema and created a custom attribute called TestAttribute2 (the LDAP name is testAttribute2) with a syntax of numerical string, single valued, with no minimum or maximum. The attribute's OID was I also created another test attribute with a Microsoft-issued OID of 1.2.840.113556.1.8000.2554.37861.10620.51629.17372.38569.15288078.14709744.1.2. The attribute is nonindexed, active, not replicated to the GC, not copied when duplicating, and not indexed for containerized searches. I then added this attribute to the person class.

Whenever I try to set either of those custom attributes using the attribute editor function of the AD Users and Computers MMC, or ADSI Edit, MMC crashes, and the attribute remains unset. However, other custom attributes with similar OIDs but with other syntaxes (CI string and Unicode string) can be set with no crash. What am I doing wrong?

  • 1
    What are you doing wrong? Simples, you're editing the AD schema! Sorry, could not resist. Jul 13 '12 at 12:40
  • Lol. Well said! :P Sometimes, I am overcome by this awful and demonic urge to edit the AD schema, though. I simply can't help myself. It usually happens when using 3rd party code that binds to AD. Jul 13 '12 at 23:27
  • 4
    What happens if you use a different tool to edit the field? #1 MS LDP support.microsoft.com/kb/260745, #2 Powershell, #3 third party ldap gui such as JXplorer or ldapAdmin?
    – Clayton
    Jun 11 '14 at 13:53
  • That is a good point; maybe I will give it a try someday. I actually haven't been working with the company where I was doing this for over a year now, but it's still interesting. Jun 11 '14 at 23:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.