Have you ever done an Active Directory machine on TryHackMe, HackTheBox, Pentester Academy, or any other platform and thought, “Huh, that was really fun!”?

Well, I certainly have. One of Penetration Testing’s most interesting topics (to me) is Active Directory. New security flaws are being discovered every day, this makes it incredibly useful to have an environment on-hand already built out. To do this, you’re going to need several things on hand, let’s go over them real quick:

Windows Server/Client ISO

These are relatively easy to acquire, you can do so with the Microsoft Evaluation Center. This can be found at the following URL:


At the time of writing, you can download either Windows 10 or 11, or Server 2019 or 2022. These are completely free to download, and have a trial range between 180 and 90 days. However, it is possible to extend this trial with the slmgr /rearm command. This is a general reminder – these devices are not designed to be used in a production environment. It is highly recommended that you download Server 20XX first. Setting up an Active Directory Environment is generally the same across all Windows Server versions. For the purpose of this post, I will be using Windows 10 and Server 2019.

Virtualization Software

This is another key thing that you should have – It is not required, you can use real metal, but this will take a considerably amount of time. I will personally be using VMWare Workstation, but just about any virtualization software will work as long as you can add VMs into an isolated network.

I have done this by creating a “NAT” network in the Subnet with a Default Gateway of

[Pasted image 20211105204953.png]

I have went ahead and disabled DHCP, this is because DHCP will be handeld by Active Directory Sites and Services. We will go into this in detail a little bit later.


This is arguably the most important thing; having an Active Directory environment is good, but if you can’t remember the credentials for anything, can’t remember the IP Addresses, or don’t remember your chosen naming scheme, you’re gonna have a bad time. I highly recommend keeping credentials for your Lab environment in someplace like a KeyPass vault or a Spreadsheet.

Installing Windows Server

The Windows Server install and setup process is relatively straight forward, because Windows Server is running, it means that the device can run on a lot less hardware resources. In fact, an Enterprise Domain Controller can run on roughly 2 CPU Cores, 8GB of RAM, and 90-120GB of Disk Space for approximately 20,000 users and computers.

After inserting the ISO and powering on the Virtual Machine, you will be presented with 4 or so options, it is very important which one you pick – two are labeled “Desktop Experience” and two are not. If you’re comfortable with managing the device via Powershell, it’s okay to choose this option, however, it’s not for the faint of heart. I highly recommend choose “Standard Evaluation”, depicted below.

[Pasted image 20211105220701.png]

Afterwards, you will be brought to the Microsoft “Terms and Conditions” screen, it’s important to be aware of these terms because it is a trial, generally if you do not use this device for production services, you will be fine.

[Pasted image 20211105220934.png]

Next up, we will be presented with the Installation type, here we want to choose “Custom: Install Windows only (Advanced)”. You will be brought to the Windows Disk Partitioning screen. Here, you should see “Drive 0 Unallocated Space”, if you don’t, click “Delete” on each partition, then click “Next”.

[Pasted image 20211105221012.png]

Lastly, Windows will begin installing. After the installation finishes, Windows will reboot and you will be presented with a screen to enter the Administrator Password. This is where you should start your Password table.

[Pasted image 20211105221453.png]

Username Password
Administrator [email protected]!

After entering the new Password, you will be brought to the login screen. Enter your password and the installation will finally be finished!

[Pasted image 20211105221719.png]

Building out the Server

Naming your Devices

To start, we’re going to reconfigure the Hostname as well as configure the Networking settings on the DC. To start, open the File Explorer, right click on “This PC”, and click “Properties”.

[Pasted image 20211105221925.png]

This will bring you to the “System Settings” panel, here we can update the Hostname of the device by clicking “Change Settings” next to “Computer Name, Domain, and Workgroup settings”. Next, click “Change” next to “To rename this computer or change its domain or workgroup, click Change”.

[Pasted image 20211105222106.png]

Here, you can update the hostname to whatever you please. Note: It’s incredibly important to set a good naming scheme presidence. Here, you want it to be both descriptive and meaningful. Generally, if this is not a lab, you want to create a naming scheme that represents the location of the device type, the device location and the device number.

For example:

This breaks down to the following:

Once again, for the purpose of the lab, we can arbitrarily name devices, but if you’re training to become a System Administrator, it’s immensley important to establish a good naming scheme that works for you. We’re going to follow the K.I.S.S. methodology – Keep It Simple Stupid and name our device SRV-DC01.

Configuring Network Settings

After this is done, we’re going to establish the Network Settings on the VM. To do so, right click on the Network Adapter and click on “Open Network and Internet Settings”, click “Change Adapter Options”, double click on the Ethernet Interface, and click “Internet Protocol version 4”, and the IP configuration settings window should now be open.

[Pasted image 20211105223312.png]

Here, you should configure your IP Settings, in accordance to what was set in your VM Network settings config. For me, I configured the following:

IP Address Range Subnet Default Gateway

After this is configured on your VM, you should then validate your network connectivity by attempting to ping a public server like

[Pasted image 20211105223747.png]

After this is setup, this concludes the basic Server Admin components. Next, we’re going to start to build out the Active Directory components of the Server.

Building the Forest

Installing ADDS

To start, we’re going to open the “Server Manager”, this is where you can perform some basic monitoring of AD and Server services. Additionally, the Server Manager allows us to install packages. To do this, we go to “Manage” and then “Add Roles and Features”. Click “Next” three times and we should be at the “Select Server Roles” tab. Here we want to install “Active Directory Domain Services”, or ADDS for short.

[Pasted image 20211105224251.png]

Next, we will click “Next”, “Next”, and “Install” to finish up the ADDS install. This installation shouldn’t take too long to finish. After it finishes, click Close. You should notice a new yellow informational triangle next to the “Manage” icon, clicking on this, you should see a pending Post-deployment Configuration option called “Promote this server to a Domain Controller”. A new window should pop open as seen below:

[Pasted image 20211105225102.png]

By default, the “Add a Domain Controller to an existing domain” option will be selected, we need to change this to “Add a new Forest”. Here you will provide a Domain Name – for example contoso.com is a fictional company that Microsoft uses. This should ideally be a valid domain name that you own if this is being deployed in Production. However, in the Lab, unless you’re looking to expand out to Office365, you can use whatever you like. I will be using banana.corp. Clicking Next will bring you to a few technical options that I won’t dive into – however, you will be required to provide a DSRM restore password. This password is normally used to correct any problems or go into a restore mode with Active Directory.

[Pasted image 20211105225522.png]

I personally have never had to use this before, however, that doesn’t mean you shouldn’t arbitrarily set this or forget this. You should add this password to your password list.

Username Password
Administrator [email protected]!
DSRM [email protected]!

Click “Next” on the DNS Options tab, since this is our first device in the Domain Controller in the environment, we can keep the default settings. Under the next “Additional Options” tab, we will be providing the NetBIOS Domain Name. This is normally seen in the DOMAIN\USER format in AD. You typically use this when logging into a device. I am going to set this to BANANA. The last few tabs you can click through “Next” and then finally “Install”. After this finishes installing, this will bring you back to the Windows Login screen.

[Pasted image 20211105230934.png]

Configuring a Conditional Forwarder

After logging in, the ADDS installation is now officially complete. Next up we will be covering how to configure DNS forwarding – This is important, when you configure the DNS server on the client workstation as the Domain Controller, the Domain Controller will not know where to forward appropriate DNS queries. In our case, if a user currently tries to query Google.com, it will not know where to go (as depicted below).

[Pasted image 20211105231405.png]

To remedy this, we have to setup a DNS conditional forwarder. To do so, search for DNS in the Windows Search bar, or open Server Manager, click Tools, then click DNS. Expanding the dropdowns you will see several options:

Expand the Conditional Forwarders tab and right click and click the “New Conditional Forwarder button”.

[Pasted image 20211105231623.png]

This new menu will open – here we are going to give the Domain of choice (for Cloudflare, they use one.one.one.one, and for Google they use dns.google)

[Pasted image 20211105232458.png]

After clicking “Ok”, using nslookup to query the IP address for Google, we should see that we are now able to resolve the DNS record. If you’d like, you can also add several more DNS servers to forward to (ex. Google).

[Pasted image 20211105232646.png]

Configuring Sites and Services

The next portion only applies to those who do not have DHCP enabled within their Network. AD Sites and Services provides a variety of AD heavy features, for example, which server is the Global Catalogue, which servers live in which sites, which SMTP server to choose if you’re in this site, which Subnets belong to these sites, etc. Having basic awareness of this section is incredibly important – here you can configure advanced features such as Site Replication which can allow you to control how often AD-Sites sync.

Let’s say you have 10,000 employees in Albany, New York and things are constantly changing, you may want a lower sync time so consistency is achieved across both sites and at the end of the day there wont be massive levels of data transfering between sites. This can cause link saturation which could potentially lead to issues.

To start, we are going to rename the first site – by default, it is named “Default-First-Site-Name”, I’m going to change this site name to Atlanta-Datacenter. This can be done by right clicking and selecting “Rename”.

[Pasted image 20211105233706.png]

Next up, we’re going to head over to the “Subnets” tab, here we are going to right click and “Add a New Subnet” as seen below.

[Pasted image 20211105233854.png]

Here, we are going to add our IPv4 address range and select our new Site.

[Pasted image 20211105233925.png]

To recap what we have configured:

Configuring DHCP

Next, we are going to move onto configuring DHCP, first we must install the DHCP service through the Server Manager, to do this, we must go to Manage -> Roles and Features -> Server Selection -> Server Roles and select “DHCP Server”.

[Pasted image 20211105234951.png]

After this is installed, we will have another Post Deployment Operation required – this being to configure the DHCP server. We must authorize the deployment of a DHCP server with our Administrator credentials. After this is finished. To configure DHCP, you must go to Tools -> and select DHCP. Expand out the DHCP panel as well as the IPv4 settings.

[Pasted image 20211105235432.png]

I recommend that you provide a relatively verbose description, for example, what Subnet you will be serving via the specific DHCP service.

After clicking “Next”, we will be configuring the scope of our DHCP pool – I’m going to exclude the first ten IP Addresses of the subnet for Servers, Firewalls and any other objects that might be important in the future that should require a static IP Address.

[Pasted image 20211105235550.png]

In the next section, it’s possible to create a reserved IP Address range, we’re going to exclude an extra set of IP Addresses (11-20) just in case.

[Pasted image 20211106000158.png]

Clicking “Next” leads us to the Lease Duration section where we can control how long each DHCP lease is issued for. I recommend lowering the DHCP lease time for the purpose of the lab. However, that is ultimately up to you.

Next, we will be creating a couple of new special DHCP options, like the Default Gateway, DNS server.

In order to add the Default Gateway, you need to type in the IP Address (in my case it will be, then we will click “Add”.

[Pasted image 20211106000530.png]

The DNS server section is already pre-populated for us, so we just need to click “Next”.

[Pasted image 20211106000643.png]

We can skip the WINS server section, lastly we will be presented with the “Activate Scope section”. Click “Activate the Scope now”, then “Next” and we will be finished!

[Pasted image 20211106000721.png]

After the scope is configured, we have some new options we can check out, these being the following:

This concludes the first part of building out an AD Lab. In the next post we will cover User Accounts, Group Policy Objects, Joining PCs to the Domain and much much more!