What Is a Windows Domain?
A Windows domain is a group of users and computers under the administration of a given business. The main idea behind a domain is to centralise the administration of common components of a Windows computer network in a single repository called Active Directory (AD).
The server that runs the Active Directory services is known as a Domain Controller (DC).
+--------------------------------------------+
| Windows Domain |
| |
| [ Domain Controller (DC) ] |
| Active Directory Database |
| - Users |
| - Computers |
| - Groups |
| - Policies |
| |
| [ Workstations ] [ Servers ] |
| Joined to domain and managed centrally |
+--------------------------------------------+
Main Advantages of a Windows Domain
- Centralised identity management — All users across the network can be configured from Active Directory with minimum effort.
- Managing security policies — Security policies can be configured directly from Active Directory and applied to users and computers across the network as needed.
Active Directory Domain Services (AD DS)
The core of any Windows Domain is the Active Directory Domain Service (AD DS). This service acts as a catalogue that holds the information of all objects that exist on your network.
AD Objects
Users are security principals — they can be authenticated by the domain and assigned privileges over resources like files or printers. Users represent two types of entities:
- People — Employees who need to access the network.
- Services — Accounts used by services like IIS or MSSQL. Service users only have the privileges needed to run their specific service.
Machines — For every computer that joins the Active Directory domain, a machine object is created. Machines are also security principals.
Machine Account passwords are automatically rotated and are generally comprised of 120 random characters.
Security Groups
Security Groups allow you to assign access rights to files or other resources to entire groups instead of individual users. When you add users to an existing group, they automatically inherit all of the group's privileges.
Default Security Groups
| Security Group | Description |
|---|---|
| Domain Admins | Administrative privileges over the entire domain, including all DCs. |
| Server Operators | Can administer Domain Controllers. Cannot change administrative group memberships. |
| Backup Operators | Can access any file, ignoring permissions. Used to perform backups. |
| Account Operators | Can create or modify other accounts in the domain. |
| Domain Users | Includes all existing user accounts in the domain. |
| Domain Computers | Includes all existing computers in the domain. |
| Domain Controllers | Includes all existing DCs in the domain. |
Organizational Units (OUs)
Organizational Units (OUs) are container objects that allow you to classify users and machines. OUs are mainly used to define sets of users with similar policy requirements.
Default Containers Created by Windows
| Container | Contents |
|---|---|
| Builtin | Default groups available to any Windows host. |
| Computers | Any machine joining the network is placed here by default. |
| Domain Controllers | Default OU containing the DCs in your network. |
| Users | Default users and groups in a domain-wide context. |
| Managed Service Accounts | Accounts used by services in your Windows domain. |
OUs vs Security Groups
| Feature | OUs | Security Groups |
|---|---|---|
| Purpose | Apply policies to users/computers | Grant permissions to resources |
| User membership | A user can only be in one OU | A user can be in many groups |
| Example use | Apply password policy to Sales team | Allow access to a shared folder |
Group Policies (GPOs)
Windows manages policies through Group Policy Objects (GPOs). GPOs are collections of settings that can be applied to OUs. They can contain policies aimed at either users or computers, allowing you to set a baseline on specific machines and identities.
Use Group Policy Management to configure GPOs.
Example: Changing Password Policy
Computer Configurations
-> Policies
-> Windows Settings
-> Security Settings
-> Account Policies
-> Password Policy
GPO Distribution
GPOs are distributed to the network via a network share called SYSVOL, stored on the DC. All users in a domain should have access to this share to sync their GPOs periodically.
The SYSVOL share points by default to:
C:\Windows\SYSVOL\sysvol\
Once a change is made to any GPO, it may take up to 2 hours for computers to pick it up. To force an immediate sync:
gpupdate /force
Authentication Methods
When using Windows domains, all credentials are stored in the Domain Controllers. Whenever a user tries to authenticate to a service, the service asks the Domain Controller to verify the credentials. Two protocols are used:
- Kerberos — Default protocol for any recent version of Windows.
- NetNTLM — Legacy authentication protocol kept for compatibility purposes.
Kerberos Authentication
Users who log into a service using Kerberos are assigned tickets — proof of a previous authentication.
[ Client ]
|
| 1. Username + encrypted timestamp -> KDC
v
[ KDC (Domain Controller) ]
|
| 2. Returns TGT + Session Key
v
[ Client holds TGT ]
|
| 3. TGT + SPN -> KDC (requesting TGS)
v
[ KDC ]
|
| 4. Returns TGS
v
[ Client ]
|
| 5. TGS -> Target Service
v
[ Service grants access ]
Key components:
- KDC (Key Distribution Center) — Runs on the Domain Controller. Creates Kerberos tickets.
- TGT (Ticket Granting Ticket) — Allows the user to request service tickets without re-entering credentials.
- TGS (Ticket Granting Service) — Grants access to a specific service.
- SPN (Service Principal Name) — Identifies the service and server the user wants to access.
NetNTLM Authentication
NetNTLM works using a challenge-response mechanism:
1. Client -> Server: Authentication request
2. Server -> Client: Random challenge number
3. Client -> Server: Response = hash(NTLM password + challenge)
4. Server -> DC: Forwards challenge + response
5. DC -> Server: Validates response
6. Server -> Client: Authentication result
The user's password or hash is **never transmitted** through the network for security.
Trees, Forests, and Trusts
As companies grow, so do their networks. Active Directory supports integrating multiple domains to manage large enterprises.
Trees
If two domains share the same namespace, they can be joined into a Tree.
thm.local (root)
/ \
uk.thm.local us.thm.local
Each subdomain has its own AD, computers, and users. IT teams in each branch manage their own resources without interfering with each other.
The Enterprise Admins group grants administrative privileges over all domains in an enterprise.
Forests
A Forest is a union of several Trees with different namespaces joined into the same network.
thm.local (Tree 1) mht.local (Tree 2)
/ \ |
uk.thm.local us.thm.local asia.mht.local
+------------------------------------------+
| Enterprise Forest |
+------------------------------------------+
Trust Relationships
Trust relationships allow users from one domain to access resources in another.
- One-way trust: If Domain AAA trusts Domain BBB, users on BBB can be authorised to access resources on AAA. The trust direction is opposite to the access direction.
- Two-way trust: Both domains mutually authorise users from each other. This is the default when joining domains into a tree or forest.
Having a trust relationship does not automatically grant access to all resources. It creates the *opportunity* to authorise cross-domain access — what is actually permitted is still controlled by administrators.
Summary
Active Directory is the backbone of enterprise Windows environments. AD DS centralises identity and policy management through users, groups, machines, and OUs. GPOs enforce configuration and security baselines. Kerberos and NetNTLM handle authentication. At scale, Trees, Forests, and Trust Relationships allow multi-domain enterprises to maintain controlled, partitioned network administration.