Active Directory Schema |
Every Active Directory object can be referenced by a unique and unambiguous name known as the distinguished name (also known as a "DN"). The distinguished name identifies the domain that holds the object as well as the complete path through the container hierarchy by which the object is reached. The distinguished name of the Schema container can be expressed as follows:
cn=schema,cn=configuration,dc=< forest root domainname>
For more information about the distinguished name, see "Active Directory Logical Structure" in this book.
You can view the contents of the Schema container by using the Active Directory Schema console in Microsoft Management Console (MMC). You also can bind to the schema directory partition and view schema objects by using the Active Directory Service Interfaces (ADSI) Edit MMC console or the Ldp tool.
Note
The ADSI Edit snap-in is not one of the default MMC
It is possible to locate the Schema container without knowing the domain name. Installation scripts and other applications that might not know what domain they are to be used in are able to gain access to the schema because they bind to a special entry at the top of the logical namespace called rootDSE, which provides the schema location. The rootDSE (DSA-specific Entry) represents the top of the logical namespace and, therefore, the top of the Lightweight Directory Access Protocol (LDAP) search tree. The attributes of rootDSE identify, among other things, the directory partitions — that is, the domain, schema, and configuration directory partitions — as well as the forest root domain directory partition. One attribute, schemaNamingContext, provides the location of the schema so that applications that are connecting to any domain controller can find and read the schema. (For more information about the rootDSE, see "Name Resolution in Active Directory" in this book.)
To identify the Schema directory partition by using ADSI Edit
The Connection dialog box is displayed.
The RootDSE folder is displayed.
Note
The Schema Management snap-in is not one of the default MMC