How to Build an Active Directory Home Lab (Free, Step by Step)

    Build an Active Directory home lab for free with Microsoft's evaluation downloads: a domain controller, Windows 11 clients and Kali on an isolated network, with a RAM plan, PowerShell build steps and weak spots to plant for practice.

    By Hacker Blueprint··16 min read

    The short answer

    An Active Directory home lab is a small Windows domain that runs on your own computer: one domain controller, one or two Windows 11 clients and a Kali Linux attack machine, all on an isolated virtual network. Microsoft's free evaluation downloads cover the Windows licenses, and 16 GB of RAM runs the whole set.

    The build takes an afternoon. You install Windows Server, promote it to a domain controller with a few PowerShell commands, join the clients, add users and plant a handful of weak settings on purpose. Snapshots let you break it and reset it in minutes.

    This guide is for OSCP® students who want to practice Active Directory (AD) attacks on a network they control, and for defenders who want to watch those attacks from the other side. It uses Windows Server 2025 or 2022 and Windows 11. An AD domain is the core of most cybersecurity home lab builds aimed at pentesting.

    We're Hacker Blueprint. Our instructor holds the OSCP, our academy has more than 600 students, and around 7,000 people have claimed our prep materials.

    Our video "OSCP Practice Lab: Active Directory Attack Chain (Part 1)" works through an AD practice lab from the first scan: network scanning at 0:45, BloodHound setup at 3:40, manual enumeration at 5:41 and BloodHound analysis at 7:26. That's the kind of session you'll run once your own lab is built. It runs 13 minutes 34 seconds.

    What you need: hardware and a RAM plan

    You need a 64-bit Intel or AMD computer with hardware virtualization turned on and room for four virtual machines (VMs). The disks below add up to about 260 GB, though dynamic disks only grow as they fill.

    VM Role RAM on a 16 GB host Disk
    DC01 Windows Server 2025 or 2022, the domain controller 2 to 4 GB 32 GB minimum, 50 GB comfortable
    WS01 Windows 11 Enterprise evaluation, first client 4 GB 64 GB
    WS02 Second Windows 11 client (optional) 4 GB 64 GB
    Kali Your attack machine 2 to 4 GB 80 GB dynamic

    The numbers come from the vendors. Microsoft lists 2 GB of RAM for Server Core or Desktop Experience (4 GB recommended for the latter), warns that a VM with 1,024 MB "results in a failed installation," and sets a 32 GB disk floor. Windows 11 needs 4 GB of RAM, 64 GB of storage and TPM 2.0 (Trusted Platform Module). Kali's VirtualBox guide uses 2,048 MB, 2 CPUs and an 80 GB dynamic disk.

    On an 8 GB host, run DC01 as Server Core with 2 GB, give WS01 and Kali 2 GB each, and keep everything else off. That client sits below Microsoft's 4 GB minimum for Windows 11, so expect it to be slow. Our guide to OSCP lab requirements covers CPUs, disks and weaker laptops.

    Download the free Windows evaluations

    Get every Windows image from Microsoft's Evaluation Center and nowhere else. You register, then download.

    • Windows Server 2025: ISO, VHD or Azure. Microsoft says "This evaluation edition expires in 180 days." The Server 2022 evaluation is still offered on the same 180-day terms.
    • Windows 11 Enterprise: a 90-day evaluation, with version 26H2 as an x64 or Arm64 ISO, or LTSC 2024 as an x64 ISO.
    • Kali Linux: from kali.org.

    Three rules shape how you plan:

    1. Activate within 10 days. Microsoft: "Evaluation versions of Windows Server must be activated over the internet in the first 10 days to avoid automatic shutdown." The network section shows how to give each VM internet access just long enough.
    2. An evaluation domain controller stays an evaluation. Microsoft: "You can't convert an Active Directory domain controller from an evaluation to a retail version." Check your edition with DISM /online /Get-CurrentEdition or slmgr.vbs /dlv.
    3. Plan to rebuild. The rearm trick appears only in an archived community wiki written for Server 2012, which says it works "only once for 180 days." Don't count on it. Keep your build commands in a script instead.

    Pick a hypervisor: VirtualBox, VMware or Hyper-V

    VirtualBox is the default choice for this guide. Version 7.2.22 is free for Windows, Linux and macOS on Intel and Apple Silicon. Since version 7.0 (October 2022) it has virtual TPM 2.0 and Secure Boot, which a Windows 11 VM needs.

    VMware Workstation Pro is free too. Broadcom announced on November 11, 2024 that Workstation Pro and Fusion Pro are free for commercial, educational and personal users, with no license key needed from version 17.5.2. The download needs a Broadcom portal account.

    Hyper-V needs Windows 10 or 11 Pro or Enterprise, since it "can't be installed on Windows 10 Home or Windows 11 Home." Microsoft also warns that VMware and VirtualBox VMs "might not start or might run unreliably" while Hyper-V is on, so pick one hypervisor and stick with it.

    On an Apple Silicon Mac, note that the Windows Server evaluation is x64 only.

    Active Directory lab setup in VirtualBox: an isolated network

    Your lab will hold accounts you made weak on purpose, so it needs its own network.

    Mode Who can reach the VMs Use it for
    Internal Network Only VMs attached to the same named network The domain and Kali
    Host-only The VMs plus your host computer Not needed for this lab
    NAT or NAT Network The VMs can reach the internet Activation and updates, then switch it off
    Bridged Every device on your home network Never use it for this lab

    The VirtualBox manual describes an Internal Network as "visible to selected virtual machines, but not to applications running on the host or to the outside world." That's what you want. The plan:

    1. Install each Windows VM with its adapter on NAT. Let it activate and install updates.
    2. Switch the adapter to Internal Network and give the network a name, such as adlab. Do this before you build the domain.
    3. Give every machine a static address on one subnet. This guide uses 10.10.10.0/24: DC01 on .10, WS01 on .21, WS02 on .22 and Kali on .50.
    4. Point every client's DNS at the domain controller, 10.10.10.10. Active Directory runs on DNS, and most join failures come from skipping this step.

    Name your domain (and skip .local)

    Old tutorials use names like mylab.local. Microsoft says: "Do not use single-label DNS names... Also, we do not recommend using unregistered suffixes, such as .local." It recommends "generic names such as corp or ds" in front of your domain, as in corp.contoso.com. Three good options:

    • A domain you own: corp.yourdomain.com.
    • The private-use .internal suffix: ICANN reserved .internal for private use in July 2024, so corp.internal will never clash with a public site.
    • The testing suffix .test: RFC 2606 reserves .test for testing, so lab.test also works.

    Never use a registered domain that belongs to someone else. This guide uses corp.internal, and its first label becomes the NetBIOS short name, CORP.

    Build the domain controller with PowerShell

    PowerShell is the fastest way to build a domain controller, and it leaves you a script for the next rebuild (the old dcpromo wizard "is deprecated beginning in Windows Server 2012"). These commands work on Server Core and Desktop Experience. Run them in an elevated PowerShell window on DC01, starting with a rename:

    Rename-Computer -NewName DC01 -Restart
    

    After the restart, set the static address (Get-NetAdapter shows your adapter's name), install the AD DS (Active Directory Domain Services) role, check the prerequisites and create the forest:

    New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 10.10.10.10 -PrefixLength 24
    Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 10.10.10.10
    Install-WindowsFeature -Name AD-Domain-Services -IncludeManagementTools
    Test-ADDSForestInstallation -DomainName "corp.internal"
    Install-ADDSForest -DomainName "corp.internal"
    

    -IncludeManagementTools adds admin tools such as Active Directory Users and Computers, which PowerShell otherwise leaves out. Test-ADDSForestInstallation runs only the prerequisite checks, so read its warnings before you go on. Install-ADDSForest asks for a Directory Services Restore Mode (DSRM) password, builds the forest and restarts the server, and "The DNS server is installed by default." Sign in afterwards as CORP\Administrator, and you have a working domain.

    Join your Windows 11 clients

    In VirtualBox, a Windows 11 VM needs EFI with Secure Boot and a TPM 2.0 device, which the VM settings offer from version 7.0. Install Windows 11, activate it over NAT, then move it to the adlab network.

    On WS01, in an elevated PowerShell window, rename the machine first:

    Rename-Computer -NewName WS01 -Restart
    

    Then set its address, point DNS at DC01 and join the domain:

    New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 10.10.10.21 -PrefixLength 24
    Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 10.10.10.10
    Add-Computer -DomainName "corp.internal" -Credential CORP\Administrator -Restart
    

    Add-Computer prompts for the administrator's password and restarts the client into the domain. If the join fails, check DNS first: Resolve-DnsName corp.internal should answer with 10.10.10.10. Repeat the same steps for WS02 on 10.10.10.22.

    Add users and plant weaknesses on purpose

    A fresh domain has almost nothing in it to attack. On DC01, create an organizational unit (OU) to hold your lab accounts and a group for the helpdesk, then add a handful of users:

    New-ADOrganizationalUnit -Name "Staff" -Path "DC=corp,DC=internal"
    New-ADGroup -Name "Helpdesk" -GroupScope Global -Path "OU=Staff,DC=corp,DC=internal"
    New-ADUser -Name "Jane Doe" -SamAccountName jdoe -Path "OU=Staff,DC=corp,DC=internal" -AccountPassword (Read-Host -AsSecureString "Password") -Enabled $true
    

    Run the last line once per user: a few staff, a helpdesk user and a service account such as svc_sql. The prompt keeps passwords out of your command history. Put the helpdesk user in its group with Add-ADGroupMember -Identity Helpdesk -Members <username>.

    Then plant weaknesses that mirror common admin mistakes. Turn on View > Advanced Features in Active Directory Users and Computers so the Attribute Editor and Security tabs show up.

    • A service account with an SPN and a weak password. Give svc_sql a service principal name (SPN) in its servicePrincipalName attribute and a password from a common wordlist. Kerberoasting depends on exactly this.
    • An account that skips Kerberos preauthentication. On one user's Account tab, tick "Do not require Kerberos preauthentication" and give it a weak password. That's the AS-REP roasting setup.
    • A password in a description field, the way a rushed helpdesk tech might leave it.
    • An ACL path. Give the helpdesk user Full Control over another user or a privileged group. BloodHound shows this as GenericAll.
    • Local admin reuse. Make a domain user a local administrator on WS01, and give both clients the same local Administrator password.

    Plant three or four and write them down. Better still, ask a friend to plant them so you go in blind.

    Three GitHub projects turn it into a vulnerable Active Directory lab at scale. vulnerable-AD builds a randomly vulnerable domain on the DC, covering Kerberoasting, AS-REP roasting, ACL abuse, DCSync, pass-the-hash and more. BadBlood "fills a Microsoft Active Directory Domain with a structure and thousands of objects" and "is not designed for a production environment." GOAD (Game of Active Directory) builds a multi-domain lab on free 180-day Windows VMs and asks for at least 24 GB of RAM (20 GB for GOAD-Light) and about 115 GB of disk. Read any script before you run it, and run it only inside the isolated lab, after a snapshot.

    Windows Server 2025 security defaults vs Server 2022

    Server 2025 ships with tighter defaults, and they change what you'll see from Kali. From Microsoft's "What's new" page:

    • "The Kerberos Distribution Center will no longer issue Ticket Granting Tickets using RC4 encryption."
    • "All new Active Directory deployments require LDAP signing (sealing) by default."
    • "SMB signing is now required by default for all SMB outbound connections."
    • New forests need "a functional level of Windows Server 2016 or later."

    Many walkthroughs were written against older defaults, with RC4 tickets and unsigned LDAP and SMB traffic, so some steps behave differently on a 2025 domain controller.

    Both choices are sound. Build on 2025 to learn the modern defaults and see which attacks they block. Or use the 2022 evaluation, still offered for 180 days, whose defaults sit closer to most training material. We can't tell you which Windows version any exam uses, and knowing why an attack works matters more. The build is scripted, so try both.

    Snapshot it and reset after every session

    VirtualBox "can save arbitrary snapshots of the state of the VM," and snapshots are what make a home lab painless.

    1. After the clients join the domain, take a snapshot of every VM called 01-clean-domain.
    2. After you plant weaknesses, take 02-weak-config.
    3. After each attack session, restore 02-weak-config.

    Kerberos is strict about time: its default tolerance between a client clock and the domain controller is 5 minutes. After a restore, check the VM clocks agree before you blame your tools.

    Attack your Active Directory lab from Kali

    Put Kali on the adlab internal network with a static address such as 10.10.10.50, and point its DNS at DC01 so names like dc01.corp.internal resolve. Scan DC01's open ports first (our nmap cheat sheet covers the scans). Then start attacking Active Directory through the weaknesses you planted, starting as an ordinary domain user:

    1. Enumeration with BloodHound. Collect domain data as jdoe and look for the ACL path you created. Our video BLOODHOUND Active Directory Enumeration (FULL GUIDE) covers setting up BloodHound at 1:04 and analyzing attack paths at 2:45.
    2. Kerberoasting. Go after the service account you gave an SPN. Our Kerberoasting guide explains how it works, what defenders see and how to stop it.
    3. AS-REP roasting. Target the account that skips preauthentication, with our AS-REP roasting guide at hand.
    4. The full loop. Chain each find into the next step and enumerate again with every new credential, as our OSCP Active Directory methodology lays out.

    After each attack, open Event Viewer on DC01 and see what it left behind.

    For more to practice, our Hacking Active Directory playlist has AD methodology from the basics to full guides, with BloodHound, AS-REP roasting, Kerberoasting, certificate attacks and lateral movement. If you'd rather skip the build entirely, our roundup of free OSCP labs lists ready-made options.

    FAQ

    Is Active Directory free?

    No. Active Directory Domain Services is a role of Windows Server, which is paid software licensed per core, plus client access licenses for the users and devices that connect. For a home lab, the Windows Server evaluation is free for 180 days and includes the full AD DS role, which is all you need to learn and practice.

    What domain name should I use for a home lab?

    Use a subdomain of a domain you own, like corp.yourdomain.com, or a reserved private name such as corp.internal or lab.test. Microsoft advises against single-label names and unregistered suffixes like .local. Never use a registered domain that belongs to someone else, since your lab's DNS would clash with theirs.

    How much RAM do I need for an Active Directory lab?

    16 GB runs a domain controller, two Windows 11 clients and Kali. 8 GB works if you run the domain controller as Server Core with 2 GB, give one client and Kali 2 GB each, and keep the rest off. That client sits below Microsoft's 4 GB minimum for Windows 11, so it will be slow.

    Do people still use Active Directory, and is Entra ID replacing it?

    Yes, it's still everywhere. Microsoft calls Entra ID "the next evolution of identity and access management solutions for the cloud," and says Active Directory "forms the basis for many infrastructure on-premises components." Most companies run the two side by side in a hybrid setup, and Server 2025 added a new functional level, so AD is still being developed.

    Is Active Directory hard to learn?

    The building blocks fit in a weekend: users, groups, organizational units, Group Policy and DNS. What takes longer is seeing how small admin choices chain into an attack path. A home lab speeds that up, because you set every weak spot yourself and then see how each one looks from the attacker's side.

    Are there free Active Directory labs?

    Yes. Our free Chain_01 and Chain_03 Active Directory labs are three-machine labs (two Windows clients and a domain controller) that you import into VirtualBox and attack offline, built like the OSCP-style AD set. They need 8 GB of RAM minimum, 16 GB recommended, on an Intel or AMD machine.

    Is there an Active Directory simulator?

    Simulators and hosted labs run AD exercises in a browser, which suits quick admin drills. A home lab built from Microsoft's free evaluations runs the actual Windows Server software, so Group Policy, DNS, Kerberos and attack tools behave the way they do at work. For attack practice, build the lab, or import our free AD chains, which are ready-made domains with nothing to build.

    What happens when the evaluation expires?

    Windows 11 Enterprise runs for 90 days. After that, Microsoft says the desktop background turns black and the PC shuts down every hour. The Windows Server evaluation runs for 180 days, and an evaluation domain controller can't be converted to a retail license. Keep your build commands in a script and rebuild the lab when the time runs out.

    Practice AD attacks on a lab you're allowed to attack

    Only attack systems you own or have written permission to test. Your home lab qualifies, as long as it stays on its Internal Network and never touches your home network or the internet in its weak state.

    If you'd rather start today, our free OSCP-style Active Directory chains are three-machine labs you import into VirtualBox and attack offline, with nothing to build.

    One of our students, kb, wrote: "The content is incredibly well-structured, beginner-friendly yet deep enough for advanced learners." (More reviews)

    Try our 30+ hour course for OSCP prep with a free trial, or start with one of our free Active Directory chains.

    Stuck on a DNS error or a failed domain join? Ask in the Hacker Blueprint Discord.

    Sources

    Keep reading

    Want new labs and discount codes first?

    We'll email you when a new lab drops or a sale goes live.

    Your email is safe with us. We don't spam.

    © 2026 Hacker Blueprint. All rights reserved.

    Built for hackers, by hackers.

    OSCP® and OSCP+™ are trademarks of OffSec. Hacker Blueprint is an independent training provider and is not affiliated with, endorsed by, or sponsored by OffSec. All content is our own original material and contains no OffSec course, lab, or exam content. Individual results vary: passing any exam depends on your own study and practice. * Lifetime access and lifetime updates run for as long as Hacker Blueprint operates, with no renewal and no extra charge.