!!! Overview[1][2] [{$pagename}] are [LDAPSyntaxes] that are specific to [Microsoft Active Directory] !! [{$pagename}] 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. !! [{$applicationname}]'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. %%zebra-table %%sortable %%table-filter ||[NAME] [Microsoft Active Directory]||Syntax [OID]||[oMSyntax]||[RFC 2252]||[ADsType] Name||[oMObjectClass]||Comment |[DistinguishedName] (a.k.a. [Distinguished Name] \\or [DN String] or [Object(DS-DN)] and is a [DN Syntax])|[2.5.5.1]|127|[1.3.6.1.4.1.1466.115.121.1.12] ([DN])|[ADSTYPE_DN_STRING]|[1.3.12.2.1011.28.0.714]|OLE Automation string |[OID Syntax]|[2.5.5.2]|6|[1.3.6.1.4.1.1466.115.121.1.38] ([OID])|[ADSTYPE_CASE_IGNORE_STRING]| |OLE Automation string |[Case-sensitive] [String]|[2.5.5.3]|27|[1.3.6.1.4.1.1466.115.121.1.5] ([Binary])|[ADSTYPE_CASE_EXACT_STRING]| |OLE Automation string |[telex]|[2.5.5.4]|20|[ 1.2.840.113556.1.4.905]|[ADSTYPE_CASE_IGNORE_STRING]| |OLE Automation string |[IA5 String|IA5String]|[2.5.5.5]|22|[1.3.6.1.4.1.1466.115.121.1.26] ([IA5 String])|[ADSTYPE_CASE_IGNORE_STRING]| |OLE Automation string |[Numeric String|NumericString]|[2.5.5.6]|18|[1.3.6.1.4.1.1466.115.121.1.36] ([Numeric String])|[ADSTYPE_NUMERIC_STRING]| |OLE Automation string |[DNWithOctetString] is a [DN Syntax]|[2.5.5.7]|127|[1.2.840.113556.1.4.903]|[ADSTYPE_DN_WITH_BINARY]|[1.2.840.113556.1.1.1.11]|IDispatch |[OR-Name]|[2.5.5.7]|127|[1.2.840.113556.1.4.1221]|[ADSTYPE_CASE_IGNORE_STRING]|[2.6.6.1.2.5.11.29]|OLE Automation string |[Boolean]|[2.5.5.8]|1|[1.3.6.1.4.1.1466.115.121.1.7] ([Boolean])|[ADSTYPE_BOOLEAN]| |True=-1, False=0 |[Enumeration|Enumeration syntax]|[2.5.5.9]|10|[1.3.6.1.4.1.1466.115.121.1.27] ([Integer])|[ADSTYPE_INTEGER]| |4-[byte] [signed int] |[Integer]|[2.5.5.9]|10|[1.3.6.1.4.1.1466.115.121.1.27] ([Integer])|[ADSTYPE_INTEGER]| |4-[byte] [signed int] |[Octet string]|[2.5.5.10]|4|[1.3.6.1.4.1.1466.115.121.1.5] ([Binary])|[ADSTYPE_OCTET_STRING]| |VARIANT| |[Replica Link]|[2.5.5.10]|127|[1.3.6.1.4.1.1466.115.121.1.5] ([Binary])|[ADSTYPE_OCTET_STRING]|[1.2.840.113556.1.1.1.6]|VARIANT| |[GeneralizedTime]|[2.5.5.11]|24|[1.3.6.1.4.1.1466.115.121.1.24] ([Generalized Time])|[ADSTYPE_UTC_TIME]| |[date] |[UTC Time]|[2.5.5.11]|23|[1.3.6.1.4.1.1466.115.121.1.53] ([UTC Time])|[ADSTYPE_UTC_TIME]| |[date] |[Directory String|DirectoryString]|[2.5.5.12]|64|[1.3.6.1.4.1.1466.115.121.1.15] ([Directory String])|[ADSTYPE_CASE_IGNORE_STRING]| |OLE Automation string |[Presentation Address]|[2.5.5.13]|127|[1.3.6.1.4.1.1466.115.121.1.43] ([Presentation Address])|[ADSTYPE_CASE_IGNORE_STRING]|[1.3.12.2.1011.28.0.732]|OLE Automation string |[DNWithString] is a [DN Syntax]|[2.5.5.14]|127|[1.2.840.113556.1.4.904]|[ADSTYPE_DN_WITH_STRING]|[1.2.840.113556.1.1.1.12]|IDispatch |[Access Point]|[2.5.5.14]|127|[1.3.6.1.4.1.1466.115.121.1.2]|[ADSTYPE_CASE_IGNORE_STRING]|[1.3.12.2.1011.28.0.702]|OLE Automation string |[NT-Sec-Desc]|[2.5.5.15]|66|[1.2.840.113556.1.4.907]|[ADSTYPE_NT_SECURITY_DESCRIPTOR]| |IDispatch |[Large integer]|[2.5.5.16]|65|[1.3.6.1.4.1.1466.115.121.1.27] ([Integer])|[ADSTYPE_LARGE_INTEGER]| |IDispatch |[SID string]|[2.5.5.17]|4|[1.3.6.1.4.1.1466.115.121.1.40]|[ADSTYPE_OCTET_STRING]| |VARIANT /% /% /% !! More Information There might be more information for this subject on one of the following: [{ReferringPagesPlugin before='*' after='\n' }] ---- * [#1] - [Syntaxes|https://technet.microsoft.com/en-us/library/cc961740.aspx|target='_blank'] - based on information obtained 2014-04-15- * [#2] - [Attribute Syntaxes|http://www.ldapexplorer.com/en/manual/107070100-attribute-syntaxes.htm|target='_blank'] - based on information obtained 2018-04-15- * [#3] - [3.1.1.2.2.2 LDAP Representations|https://msdn.microsoft.com/en-us/library/cc223177.aspx?f=255&MSPPError=-2147217396|target='_blank'] - based on information obtained 2018-09-27- * [#4] - [Data Type Mapping between Active Directory and LDAP|https://docs.microsoft.com/en-us/windows/desktop/adsi/data-type-mapping-between-active-directory-and-ldap|target='_blank'] - based on information obtained 2018-10-05-