Microsoft Active Directory Syntax is a mess.#Way to many different types of references to the same thing. Microsoft appears to refuse to follow the standards for formatting LDAPSyntaxes, AttributeTypes, and ObjectClasses. You must go to many pages on their sites to figure out what how this attribute should be determined.
Ldapwiki's Best Effort#The LDAPSyntaxes supported by Domain Controllers are as shown in the following table. The set of syntaxes supported is NOT extensible by schema modifications. Each syntax is identified by the combination of the attributeSyntax, oMSyntax and, in select cases, oMObjectClass attributes of an attributeSchema object. The cases for which oMObjectClass is not used are indicated by the presence of a hyphen in the oMObjectClass column in the table. The combinations shown in the following table are exhaustive; this table is consistent and identical for Windows Server 2000 operating system and later.
While oMObjectClass conceptually contains an object identifier (OID), it is declared in the schema as String(Octet) syntax, requiring that values read from and written to it be expressed as the Basic Encoding Rules (BER) encoding of the OID. In the table, both the BER-encoded form and the dotted string form of the OID are given.
More Information#There might be more information for this subject on one of the following:
- Access Point
- DN Syntax
- Enumeration syntax
- Forward link
- LDAP Schema
- Replica Link
- [#1] - Syntaxes - based on information obtained 2014-04-15-
- [#2] - Attribute Syntaxes - based on information obtained 2018-04-15-
- [#3] - 18.104.22.168.2.2 LDAP Representations - based on information obtained 2018-09-27-
- [#4] - Data Type Mapping between Active Directory and LDAP - based on information obtained 2018-10-05-