Active Directory Lab - Part 1: Server Prep & Domain Setup

In this lab, we’re setting up a Windows Server as a fully functional Domain Controller using Active Directory Domain Services (AD DS). This is the foundation of any enterprise IT infrastructure.
you can do this lab in VirtualBox like I did, or choose to run it on any cloud provider such as Azure, AWS, or Google Cloud.

This is Part 1 of a multi-part Active Directory lab series designed to simulate a real-world environment. We’ll move step-by-step from initial setup to deploying users, policies, and securing a domain.

1. Change Server Name

After the instalation of the Server on VirtualBox. then we can change the Server name for more clarity and easy reference:

• Open Server Manager (it opens by default), Go to Local Server (left-hand menu). Click on the current computer name
• I Changed mine to HC1 for easy reference in the next labs.

then click OK and restart the server

2. Set Static IP Address

We have to set a static IP address for the server in order to make it reliable, reachable, and consistent on the network.

3. Install Active Directory Domain Services

3.1 Add AD DS Role

without the AD DS role, your server is just like any other server, to turn it into a domain controller it needs AD DS role (think of it like installing the engine into the car before you can derive(create users, manage domains, set up group policies…))
Adding the AD DS role is the first and essential step in making your server a Domain Controller. Without it, you cannot create a domain, join machines to it, or manage users centrally
here are the steps to do that: Open Server Manager then Click Manage → Add Roles and Features.

Click Next through the first few steps until you reach Server Roles. Check the box:Active Directory Domain Services

A pop-up will appear → Click Add Features.

Click Next until you reach Install, then click Install. Wait for installation to finish Installation is now finished.

3.2 Promote the Server to Domain Controller

after adding the AD DS Role, our server is ready to become a domain controller but not one yet, that is why we have to promote it to become one,when we promote it we are :

• Creating a new domain or joining an existing one.
• Installing the AD database.
• Setting up the SYSVOL and NTDS folders.
• Activating the server as the controller for the domain.

after the promotion, we have a domain controller that is able to handle :

• Authorization (what they can access)
• Directory Services (users, computers, groups, etc.)
• Group Policies (security and configuration enforcement) and DNS integration.

Here are the steps to do it:

1. Open Server Manager
   Click the yellow ⚠ warning flag and choose: “Promote this server to a domain controller”

1. Deployment Configuration
   • Select: Add a new forest
   • Root domain name: Hlab.local
   • Click Next
2. Domain Controller Options
   • ✅ Domain Name System (DNS)
   • ✅ Global Catalog (GC)
   • ❌ Read-only domain controller (RODC)
   • Set a DSRM password
   • Click Next
3. DNS Options
   • Ignore delegation warnings this is normal for the first DC
   • Click Next
4. NetBIOS Name
   • Accept default
   • Click Next
5. Paths
   Unless you have a specific reason, leave the default paths:
   • Database: C:\Windows\NTDS
   • Logs: C:\Windows\NTDS
   • SYSVOL: C:\Windows\SYSVOL
   • Click Next
6. Review Options
   • Confirm settings
   • Click View script if you want to save the PowerShell equivalent
   • Click Next
7. Prerequisites Check
   • Wait for the check to complete
   • Minor warnings are fine
   • Click Install

The server will automatically reboot after installation.

---

Domain Controller Is Ready

we now have a fully functional Domain Controller!

• Domain: Hlab.local
• Services: AD DS, DNS

Next on Part 2:

• Create OUs (Organizational Units)
• Add users and groups