Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 38 ยท Getting Started

Active Directory Overview

Understand what Active Directory Domain Services provides, its main components (domain controllers, DNS, Kerberos, Group Policy) and how they fit together.

Active Directory Domain Services (AD DS) is the directory service built into Windows Server. It has been the center of Windows networks since Windows 2000. When someone logs into a company laptop with their work name and password, there is a good chance Active Directory is checking those credentials, deciding which file shares they can open and applying the settings that lock the screen after five minutes.

This lesson gives you the map of the whole platform. You will see the pieces (domain controllers, the database, DNS, Kerberos, Group Policy), what each one does and how a single login touches several of them. The later chapters of this track study each piece in depth.

Because Active Directory cannot run on this page, the descriptions below are of the real product and the examples are labelled stand-ins.

What AD DS provides

Directory Users, groups, computers.
Authentication Kerberos and NTLM.
Policy Group Policy for settings.
Replication Many servers stay in sync.

Four services, one product

1 / 2

The main components

Domain controllers

A domain controller (DC) is a Windows Server that runs AD DS. It holds a copy of the directory database and answers authentication and LDAP requests. A domain usually has at least two DCs, so a failure of one does not stop logins. Almost all DCs are writable and accept changes, which they replicate to each other (multi-master replication). A special kind, the read-only domain controller (RODC), keeps a read-only copy for branch offices with weaker physical security.

The database

The directory is stored in a database file named NTDS.dit on every DC (in C:\Windows\NTDS by default). It uses the Extensible Storage Engine (ESE), the same technology Exchange uses. It holds all entries and attributes, including password hashes, which is why a stolen NTDS.dit is one of the worst things that can happen to an organization.

The schema

The schema is the list of allowed object classes and attributes. It is stored inside the directory itself and replicated to every DC for the whole forest. AD ships with a large schema (user, computer, group, organizationalUnit, ...) that you can extend, carefully. See Schema.

DNS

Active Directory relies on DNS to find things. DCs register service records (SRV records) such as _ldap._tcp.dc._msdcs.example.com, so a laptop can ask DNS "which servers handle LDAP for my domain?". If DNS is broken, domain logins break, and a very large share of AD problems turn out to be DNS problems. Most domain controllers run the Microsoft DNS Server role and store their zones in AD itself.

Kerberos and NTLM

AD authenticates users with Kerberos, a ticket-based protocol covered in the Kerberos chapter. Each DC runs a Key Distribution Center (KDC). The older NTLM protocol remains as a fallback and is a frequent target for attackers, so many organizations restrict it.

Group Policy

Group Policy lets administrators define settings (password rules, firewall, software, desktop restrictions) once and apply them to thousands of computers and users. Policies are stored partly in the directory and partly in a shared folder named SYSVOL.

LDAP and the Global Catalog

Applications query AD with LDAP on TCP port 389 (and LDAPS on 636). A subset of DCs also serve the Global Catalog on ports 3268 and 3269, a searchable index of every object in the whole forest.

What happens when a user signs in

Follow one login from a domain-joined PC:

  1. The user types a name and password.
  2. The PC asks DNS which server is a domain controller for the domain.
  3. It sends a Kerberos request to that DC's KDC.
  4. The DC checks the password hash in the directory and returns a ticket-granting ticket.
  5. The PC asks for a service ticket for each resource, such as a file server, and presents it.
  6. At logon the PC downloads and applies Group Policy from the directory and SYSVOL.
  7. Group memberships from the directory decide which resources the user may open.
flowchart TD
    U["User signs in"] --> D["DNS: find a domain controller"]
    D --> K["KDC: Kerberos ticket"]
    K --> G["Group Policy applied"]
    K --> R["Access resources by group membership"]

Figure: a single logon touches DNS, Kerberos, Group Policy and the directory.

Versions and functional levels

Each AD release adds features. Windows Server 2025 introduced a new forest functional level and a larger 32 KB database page size for big environments. Every domain and forest has a functional level, which is the lowest DC version it must support. You raise the level once all DCs are new enough, and it unlocks features. Common ones you will meet in this course include the AD Recycle Bin (forest level 2008 R2 and later) and fine-grained password policies (domain level 2008 and later).

Active Directory flavors

The name "Active Directory" covers several related things, which beginners often mix up:

Product What it is
AD DS The on-premises directory this track is about
AD Certificate Services (AD CS) A certificate authority integrated with AD
AD Federation Services (AD FS) Single sign-on to web apps with SAML or OIDC
AD Lightweight Directory Services (AD LDS) A standalone LDAP directory without the domain features
Microsoft Entra ID The cloud identity service, a different product with the older name Azure AD

Entra ID is not "Active Directory in the cloud". It does not use LDAP or Kerberos in the same way and has no domain controllers or Group Policy. Organizations often keep AD DS on premises and synchronize identities up to Entra ID.

A model of "who may log in" (Python stand-in)

Here is a simplified stand-in for the decision a DC makes. It is only a teaching model, not the real algorithm: it checks the account is enabled, the password hash matches and the account is not locked.

Python Mini login decision (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Real AD never stores plain SHA-256 hashes of passwords: it stores an NT hash, and Kerberos keys derived from the password. The stand-in just demonstrates the order of checks.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the role of a domain controller?

    A DC runs AD DS, holds NTDS.dit and serves authentication and LDAP queries.
  2. 2. Why does Active Directory depend so heavily on DNS?

    Clients ask DNS which servers provide LDAP and Kerberos, so broken DNS breaks logons.
  3. 3. Which file holds the directory database on a domain controller?

    NTDS.dit is the ESE database of the directory. SYSVOL holds policy files and scripts.
  4. 4. Is Microsoft Entra ID the same product as AD DS?

    Entra ID uses OAuth, OIDC and SAML, and has no domain controllers or Group Policy.

Summary

  • AD DS is Microsoft's directory: database, schema, authentication, replication and Group Policy.
  • Domain controllers hold the NTDS.dit database and replicate changes among themselves.
  • DNS, Kerberos and accurate time are hard dependencies. Check them first when something breaks.
  • The Global Catalog gives a forest-wide search on ports 3268 and 3269.
  • Do not confuse AD DS, AD CS, AD FS, AD LDS and Entra ID.

Next: Lab Setup and Tools