Home > Articles > Operating Systems, Server > Microsoft Servers

Like this article? We recommend

Namespace and Naming Conventions

The Active Directory's naming conventions serve a number of important purposes. First, all directories are based on the concept of a namespace; that is, a name is used to resolve the location of an object. When name resolution occurs, it converts the namespace locator to the specific object, such as a printer on the third floor. Everything hangs off the Active Directory using the namespace to identify and locate persons, places, and things within an enterprise.

Naming Conventions

In keeping with the namespace concept, the Active Directory uses four name types to recognize every object:

  • The distinguished name (DN) defines the domain and related container(s) in which an object resides. It matches several defined attributes to the description—the basic ones are DomainComponent (DC), OrganizationalUnit (OU), and CommonName (CN). For example, a representation of a printer within the EntCert.com domain and sales organizational unit, physically located on the third floor, would have the distinguished name DC=COM,DC=EntCert, OU=sales,CN=Printer,CN=3rdfloorprinter.

  • The relative distinguished name (RDN) is really an attribute of the object itself. In the above example, CN=3rdfloorprinter is relative to its parent, CN=printer. The RDN is compared to the DN.

  • The Globally Unique Identifier (GUID) avoids duplication of objects, and ensures uniqueness. It is a 128-bit number assigned to an object at the time of creation, and stored with it. This permits applications—for example, a word processor file with embedded graphical objects—to retrieve an updated version of a drawing by use of the GUID that is stored within the document.

  • The user principal name (UPN) is considered a "friendly" naming convention. It combines the user account name with the DNS domain name in which the account exists. The name bob@EntCert.com is the UPN for user account bob within the EntCert.com domain tree.

Additional use of Industry Naming Standards

The Active Directory supports a number of industry standard formats to facilitate greater interoperability with other directory services. Microsoft's own Universal Naming Convention (UNC), which takes the form \\EntCert.com\Administration\budget.doc, is the base naming convention. The Active Directory also incorporates RFC 822, which defines the common Internet e-mail-naming structure of user@domainname.com. It supports the familiar HTTP Uniform Resource Locator (URL), which takes the form http://EntCert.com/specific page, as well. Finally, borrowing from the X.500 communication protocol, the Active Directory incorporates the LDAP URL, as defined in the draft of RFC 1779, which breaks the name into very specific subunits that might look like this:


The initials provide greater object specification. CN is the user's first and last name. The two hierarchical OUs distinguish the branch of the company and the specific product area. Finally, DN defines the work area, such as engineering, accounting, or marketing.

Active Directory Use of LDAP

The Lightweight Directory Access Protocol (LDAP), defined by the Internet Engineering Task Force RFC 2251, is a simplified version of the X.500 DAP. Microsoft's Windows 2000 utilizes LDAP versions 2 and 3. LDAP permits the exchange of directory data between services. For example, because Novell Directory Services data is LDAP-compliant, it can be passed to and from the Active Directory.

LDAP is utilized to access information from compliant directory services such as the Active Directory. LDAP searches the Active Directory for information about stored objects and their attributes. It uses both distinguished and relative distinguished names to locate the object, and works closely with DNS throughout this process. DNS provides resolution to locate the appropriate Active Directory domain controller; LDAP resolves the object itself. The process follows these basic steps:

  1. A client queries DNS for an LDAP server (Active Directory domain controller).

  2. The client queries the domain controller for information about the object.

  3. If the requested object is not in the domain, but the domain controller knows there are child domains or a forest domain, it issues a referral to contact the other domain controllers until object resolution is achieved.

  4. The client is returned the object information.

LDAP's C language API (RFC 1823) permits the development of application enhancements and the building of related applications. Developing interfaces using the LDAP C API is perhaps the easiest way to provide interoperability between LDAP directory-compliant services. Existing LDAP directory service auxiliary applications migrated to communicate with Windows 2000 Active Directory may not need modification. If API code changes are required as well, they are typically for the identification of objects unique to the Active Directory.

In addition to the aforementioned conventions introduced in Windows 2000, the Windows 2000 Active Directory implementation adds a number of additional facilities to its LDAP support:

  • Active Directory now has support for dynamic store entries, as defined by the Internet Engineering Task Force (IETF) standard protocol RFC 2589. Entries in the directory can additionally be assigned Time-To-Live (TTL) values that determine when the entries will be automatically deleted.

  • Transport Layer Security (TLS) connections to Active Directory over LDAP are now protected using the IETF standard TLS security protocol (RFC 2830).

  • The Digest Authentication mechanism (DIGEST-MD5 SASL authentication) over LDAP connection Active Directory is supported (RFC 2829).

  • Virtual List Views (VLV) LDAP extensions, as defined by the Working Group of IETF, are also supported.

  • [lb]Support for Dynamic Auxiliary classes and instances are also supported.


An extension of LDAP is its replication technology protocol LDUP (LDAP Duplication/Update Protocol), an open standards specification that is not embraced by the Active Directory. LDUP does a complete real-time replication of directory elements that requires that compliant directory services adhere to very specific rules and data structures. Violation of any of the rules such that a directory entry is not understood can lead to cascading errors throughout the directory. Rather than LDUP, the Active Directory utilizes a synchronization methodology to populate and update directories.


Microsoft decided not to include major portions of the X.500 protocol in the Active Directory primarily because of its dependence on an OSI networking layer and a general lack of public interest. The excluded elements are the Directory Access Protocol, the Directory System Protocol, the Directory Information Shadowing Protocol, and the Directory Operational Binding Management Protocol. LDAP is the most significant element of X.500 incorporated in Windows 2000 and Windows 2000.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020