Learn Active Directory - Prerequisite Skills & Environment Setup

#Introduction

Welcome to the Learn Active Directory series! This series will take you through mastering Active Directory — Microsoft's directory service for identity management, authentication, and authorization in enterprise Windows networks — from core concepts to production-grade administration. There are 31 sequential episodes in total, so reading each episode in order will build up your mastery layer by layer.

Before creating your first domain controller, you need to prepare two things: foundational skills and a lab environment. Why do prerequisites matter? Imagine you want to become a ship's captain: a certificate alone is not enough without a map, a compass, and a harbor to practice in. Episode 0 is your map, compass, and harbor before you set sail into the Active Directory seas.

#Prerequisite Skills You Should Have

Don't worry if some of these still feel abstract — all of them will be put into practice in later episodes. The key in episode 0 is making sure you are comfortable with the foundations, especially DNS and PowerShell, because both will be used in nearly every episode.

#DNS and Networking

DNS is the network's "phone book". When a computer wants to join a domain, it asks DNS: where is the nearest domain controller? If DNS is wrong, clients will never find a domain controller — even if AD itself is running perfectly. At minimum, understand how forward lookup, A records, and SRV records work; these three concepts will be covered in episode 4.

For networking, master the concepts of IP address, subnet mask, and default gateway. Later in the lab, each VM will be assigned a static IP on the same subnet so they can communicate with each other. Try checking your machine's network configuration with Get-NetIPAddress or ipconfig to get comfortable reading the output.

#Basic PowerShell

Active Directory has a complete GUI, but modern administration almost always uses PowerShell — especially for automation and consistency. You don't need to memorize many commands yet; just understand three things: how to run the console as administrator, the concept of cmdlets with their verb-noun naming pattern, and the habit of reading help via Get-Help. If you have never touched PowerShell before, read the Learn PowerShell series on this blog before diving into AD.

#Software and Tools to Prepare

RSAT deserves a special mention. In production, you won't always be sitting in front of a domain controller; with RSAT, tools like ADUC and GPMC can be installed on a regular Windows 10/11 machine and manage AD remotely. In the lab, these tools can be installed on a separate admin machine.

#Hardware and VM Specifications

Active Directory isn't resource-hungry, but this lab needs several VMs running at the same time. Pay attention to how resources are allocated on the host:

Add up the VM requirements: with one DC, one member server, and one client, total RAM is around 10-12 GB. That's why a host with 16 GB RAM or more is highly recommended. All VMs must be able to reach each other — use an internal network or host-only network so VMs can communicate without being freely exposed to the internet.

#Lab Planning Before Installation

Before creating VMs, settle on three things to keep the whole series consistent: hostname, static IP, and domain name. This planning is like drawing up a blueprint before building a house — cheap up front, expensive if you have to tear it down and redo it.

• Hostname: short and descriptive, e.g. DC01 for the domain controller, FS01 for the file server, WIN11 for the client.
• Static IP: the domain controller must have a static IP. For example, 192.168.10.10/24 for DC01, with gateway 192.168.10.1.
• Domain name: use a subdomain of a public domain you own, e.g. ad.example.com. Avoid .local names because they risk conflicting with mDNS, and avoid public TLDs without a subdomain.

When a server is freshly installed, configure the static IP and hostname right away. Important note: point the DNS server at itself, because this server will later become the AD DNS server.

New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 192.168.10.10 -PrefixLength 24 -DefaultGateway 192.168.10.1
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 192.168.10.10
Rename-Computer -NewName "DC01" -Restart

For reference, here is the lab blueprint that will be used throughout this series:

#Setting Up the Virtual Machine

In this lab we use VirtualBox as an example — similar steps apply to Hyper-V and VMware. Create a new VM with the specifications above, mount the Windows Server ISO, complete the OS installation, then apply the IP and hostname configuration as shown in the earlier example. Once the VM is working, take a snapshot right away: a snapshot is a time machine that will save you whenever a later experiment goes sideways.

#Conclusion

In episode 0 you have set the foundation for the entire series: Windows Server administration basics, DNS, networking, and PowerShell skills; the software and hardware specifications for the lab; and a lab blueprint with hostnames, static IPs, and a domain name.

Key takeaways:

• DNS is a non-negotiable foundation; AD cannot run without correct DNS.
• The lab needs several VMs, so calculate the host's total RAM carefully.
• A static IP for the domain controller and the ad.example.com domain name are safe planning choices.
• Always take a snapshot after a VM is fully configured.

In the next episode, we'll cover history, background, and why the world needs Active Directory — from the flat, fragile Windows NT domains of 1993, the birth of Active Directory in Windows 2000, its evolution through Windows Server 2022 and Azure AD, and the real-world problems AD solves in the enterprise. Make sure your lab is ready, because the Learn Active Directory journey is just beginning!