HP 1x1x16 - IP Console Switch KVM, Руководство пользователя

Страница: 332 / 339

Glossary 332
organizational unit
Each OU created in active directory is a container that is an active directory administrative boundary,
controlled by group policy. OUs can contain users, groups, resources, and other OUs. An OU can be
thought of as providing the administrative functionality found in Windows NT® 4.0 domains. In other
words, the administrative control provided by Windows NT® 4.0 domains has been incorporated into
active directory organizational units.
Peer Master Domain Controller
A domain controller is called a Peer Master Domain Controller if it a controller for a domain that has
more than one domain controller. It is called a "peer master" for the domain because it can be modified
(unlike BDC under the older Windows NT® 4.0 network architecture). Each peer master for a domain
replicated data modifications it receives to communicate the changes to all the other peer masters in the
same domain. Under the older Windows NT® 4.0 network architecture, only the PDC can be written to
and the BDCs are read-only. Under active directory, every domain controller for a given domain can be
written to and is responsible for replicating changes to the other Peer Master Domain Controllers for the
same domain.
referral
The LDAP searchResult returned by an LDAP server when it does not hold the base Object of a search
Request. A referral is specific in the sense that it always points to a server that holds the desired
baseObject (this is in contrast to Continuation Reference, which are non-specific in the sense that the
Continuation References returned in a searchResult always list all of the immediate child domains below
the domain that is generating the searchResult. Therefore, some of the domains listed in a response
containing Continuation References might not hold any of the target objects).
Relative Distinguished Name
This is a term used extensively in the X.500 standards to denote the name used to uniquely reference an
object relative to its parent container and the domain that holds the object. In Microsoft active directory,
the term "RDN" is rarely used explicitly, but the concept is frequently used. It is instantiated by the
rDNAttID attribute. For the object classes person, computer, and group, the value of rDNAttID is set to cn.
Similarly, for the object class organizationalUnit, the value of rDNAttID is set to OU. For example, if a
person distinguishedName of an object is: cn=John Smith,cn=users,dc=widget,dc=com, then that RDN is:
cn=John Smith.
Note that in this example, the RDN appears to be the concatenation of two attribute values: the user's
givenName and his surname (sn). However, in the default Microsoft® active directory schema, an object
of class person uses the displayName attribute value as the value of the RDN of the object. In the example
of John Smith, when the administrator created the user account, the Logon Name was set to JohnSmith.
The Logon Name gets stored in the attribute named sAMAccountName. Note that "Logon Name" is what
the field is called in the ADUC interface. Similarly, the fields in the ADUC interface labeled "First Name"
and "Last Name" are stored in the attributes names givenName and sn, respectively, as well as in
displayName. In Microsoft active directory, for objects of class person, Common-Name (cn) and Display-
Name (displayName) get assigned the same value.
root domain
A domain that is not a child domain of any domain in the forest. A root domain can have child domains.
Each root domain might be a forest root. Each forest has only one root domain. See also domain tree root
and forest root.