Skip to content
Menu
  • CloudThesis-Home
  • Cloud Management
    • Tanzu
    • VMware Cloud
    • VCF (VMware Cloud Foundation)
    • vRO
    • vRA
    • vRealize Log Insight
    • vCloud Director
    • Hybrid Cloud Extension (HCX)
    • vCloud
    • Cloud on AWS
  • VMware
    • vCenter
    • vSphere
      • Generic vSphere Commands
    • ESXi
    • VMware vRealize Suite Lifecycle Manager –8 Deployment Guide
    • VMware Site Recovery Manager (SRM)
    • vRealize Network Insight
    • VMware Horizon
  • Power CLI
    • PowerCLI Snippets
  • NSX
  • vSAN
    • vSAN 7
  • Nutanix
  • VOIP
  • Microsoft
    • Active Directory Domain Services (AD DS) Training & Lab Guide
    • Azure Cloud
      • Azure AD Seamless Single Sign-On (SSO) – Implementation and Overview
      • Azure RBAC: Fine-Grained Access Control for Secure and Scalable Resource Management
    • Microsoft Windows Server
    • Hypervisor
    • Create Azure VMs (Portal)
      • Create Azure VMs – PowerShell
  • Author
  • Contact

Active Directory Domain Services (AD DS) Training & Lab Guide

Posted on June 1, 2026June 1, 2026

Introduction

Learn about the fundamentals of Active Directory Domain Services (AD DS) in Windows Server, including forests, domains, sites, domain controllers, organizational units (OUs), users, and groups.

Learning objectives

After completing this module, you’ll be able to:

  • Describe AD DS.
  • Describe users, groups, and computers.
  • Identify and describe AD DS forests and domains.
  • Describe OUs.
  • Manage objects and their properties in AD DS.

Prerequisites

To get the best learning experience from this module, you should have knowledge and experience of:

  • Windows Server.
  • Core networking technologies.

Active Directory Domain Services (AD DS) :

A Microsoft directory service that acts as a central repository for enterprise networks, managing identities, resources, and access control. It simplifies administrative tasks by providing a secure, searchable hierarchy for organizing users, computers, and groups.

The logical framework of AD DS is built on a hierarchy of components: Schema: The blueprint. It defines the exact rules, object types, and attributes (e.g., user account fields, passwords) that can be created in the directory.

ComponentDescriptionHierarchical LevelNamespace RelationshipKey Function
DomainA logical, administrative container for grouping resources and security boundaries.Mid-LevelMaps directly to a portion of the database.Groups resources and applies security policies.
Organizational Unit (OU)Sub-containers within a domain are used to organize objects.Lowest-LevelShares the parent domain’s namespace.Organizes objects and delegates administrative control to departments/locations.
Domain TreeA hierarchical grouping of domains.Mid-to-High LevelShares a continuous, contiguous namespace (e.g., company.com and sales.company.com).Connects domains with a trust relationship and shared namespace.
ForestThe highest-level logical container in AD DS.Highest-LevelCan contain multiple trees that do not share a contiguous namespace.Shares a common schema, configuration, and Global Catalog across all domain trees.
PartitionSpecific portions of the AD DS database.Database-LevelN/ABreaks the database into categories (Schema, Configuration, Domain) for replication.

A screenshot of Active Directory Sites and Services. The administrator has selected the Sites node. Displayed are two sites, Seattle and Vancouver. Also displayed are two subnets.

 

The following table describes some of the physical components of AD DS.

Physical ComponentConcise Description
Domain Controller (DC)A server containing a copy of the AD DS database; processes and replicates changes across the domain.
Data StoreThe Ntds.dit file and logs (default: C:\Windows\NTDS) using Microsoft Jet technology to store directory info.
Global Catalog (GC) ServerA DC hosting a partial, read-only copy of all forest objects to speed up cross-domain searches.
Read-Only Domain Controller (RODC)A special AD DS installation for low-security locations or branch offices; does not allow direct database changes.
SiteA container for objects specific to a physical location, used to manage network traffic and replication topology.
SubnetA range of IP addresses assigned to computers within a specific site; a single site can contain multiple subnets.

user objects:

  • In AD DS, you must provide all users that require access to network resources with a user account. With this user account, users can authenticate to the AD DS domain and access network resources.
  • In Windows Server, a user account is an object that contains all the information that defines a user. A user account includes:
  • The username.
  • A user password.
  • Group memberships.
  • A user account also contains settings that you can configure based on your organizational requirements.
  • The username and password of a user account serve as the user’s sign-in credentials. A user object also includes several other attributes that describe and manage the user. You can use the following to create and manage user objects in AD DS:
  • Active Directory Administrative Center.
  • Active Directory Users and Computers.
  • Windows Admin Center.
  • Windows PowerShell.
  • The dsadd command-line tool.

·      Define AD DS forests and domains:

  • An AD DS forest is a collection of one or more AD DS trees that contain one or more AD DS domains. Domains in a forest share:
  • A common root.
  • A common schema.
  • A global catalog.
  • An AD DS domain is a logical administrative container for objects such as:
  • Users
  • Groups
  • Computers
  • What is an AD DS forest?
  • A forest is a top-level container in AD DS. Each forest is a collection of one or more domain trees that share a common directory schema and a global catalog. A domain tree is a collection of one or more domains that share a contiguous namespace. The forest root domain is the first domain that you create in the forest.
  • The forest root domain contains objects that don’t exist in other domains in the forest. Because you always create objects on the first domain controller, a forest can consist of as few as one domain with a single domain controller, or it can consist of several domains across multiple domain trees.
  • The following graphic displays Contoso.com as the forest root domain. Beneath are two domains, Adatum.com in a separate tree, and Seattle.Contoso.com as a child of Contoso.com.
  • A graphic that displays a hierarchy of domains as described in the preceding text.
  • The following objects exist in the forest root domain:
  • The schema master role.
  • The domain naming master role.
  • The Enterprise Admins group.
  • The Schema Admins group.

 

Lab Assignments: Day-by-Day Breakdown

Day 1. AD DS Installation & Domain Controller Setup

This section covers end-to-end installation of Active Directory Domain Services and promoting a server to Domain Controller.

  • Login to Windows Server with Administrator credentials
  • Open Server Manager → Click Add Roles and Features
  • Select Role-based installation → Choose local server
  • Select ‘Active Directory Domain Services’ role → Click Next → Install
  • After installation, click ‘Promote this server to a domain controller’
  • Select ‘Add a new forest’ → Enter root domain name (lab.local)
  • Set Directory Services Restore Mode (DSRM) password
  • Proceed with defaults → Click Install
  • Server will reboot automatically
  • Login using domain credentials (lab\Administrator)

Day 2. User, Group & Computer Management

Manage identities and access using ADUC and PowerShell.

  1. Open ‘Active Directory Users and Computers’ (dsa.msc)
  2. Right-click Users → New → User → Create test user
  3. Set password → Enable account
  4. Create a new Security Group → Add user to group
  5. Join client machine: Open System → Change settings → Domain → lab.local
  6. Restart client system
  7. Verify computer in ADUC under Computers OU

Day 3. Forest & Domain Configuration

  • Install AD DS role on second server
  • Promote as Domain Controller (existing domain)
  • Select ‘Add a domain controller to an existing domain’
  • Provide domain admin credentials
  • Verify replication using ‘repadmin /replsummary’
  • Check trust: Active Directory Domains and Trusts

Day 4. Organizational Units (OU) Management

  • Open ADUC
  • Right-click domain → New → Organizational Unit
  • Create OUs: IT, HR, Finance
  • Move users to respective OUs
  • Delegate control: Right-click OU → Delegate Control Wizard

Day 5. Object Management & PowerShell

  • Open ADUC → Select user → Properties
  • Update attributes (department, phone)
  • Reset password and unlock account
  • Run PowerShell as Administrator
  • Execute: Get-ADUser -Filter *
  • Modify user: Set-ADUser -Identity username -Department IT

Thanks

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Search Topic

Categories

  • Active Directory Domain Services
  • Azure Cloud
  • Cloud Management
  • Cloud on AWS
  • Create Azure VMs – PowerShell
  • Create Azure VMs (Portal)
  • ESXi
  • Generic vSphere Commands
  • Hybrid Cloud Extension (HCX)
  • Hypervisor
  • Microsoft
  • Microsoft Azure Cloud and Services
  • Microsoft Windows Server
  • NSX
  • Nutanix
  • Power CLI
  • PowerCLI Snippets
  • Tanzu
  • vCenter
  • VCF (VMware Cloud Foundation)
  • vCloud
  • vCloud Director
  • VMware
  • VMware Cloud
  • VMware Horizon
  • VMware Site Recovery Manager (SRM)
  • VMware vRealize Suite Lifecycle Manager – 8.0
  • vRA
  • vRealize Log Insight
  • vRealize Network Insight
  • vRO
  • vSAN
  • vSAN 7
  • vSphere
  • Windows Servers
©2026 | WordPress Theme by Superbthemes.com