Homelab Chronicles: Setting Up Active Directory and Joining a Windows Client to the Domain

Active Directory (AD)is the backbone of enterprise identity and access management. To prepare for a Tier 1 IT Helpdesk role, I built a virtual sandbox environment to master the core administrative tasks: promoting a domain controller, provisioning user, and binding client machines to a network.

The Prerequisites / Environment (Crucial Step!)

Before diving into the steps, here the specifications i have used:

• Hypervisor: Oracle VirtualBox
• Domain Controller OS: Windows Server 2022 (Evaluation)
• Client OS: Windows 10 Pro
• Network Mode: Host-Only Adapter (to isolate the lab environment while allowing VM-to-VM communication)

(Note: Prior to these steps, the Active Directory Domain Services role was installed on the server, and it was promoted to a Domain Controller for the lab.local forest.)

Section 1: Creating a User Account in Active Directory

• Open Server Manager, click Tools in the top right corner, and launch Active Directory Users and Computers (ADUC).

• Right-click your domain (lab.local), select New, and click Organizational Unit (creating an OU helps keep your users and departments organized). Name it something like "Corporate Users".
• Right-click your new OU (in this case i am using the already provided OU Users), select New -> User.

• Fill in the First Name, Last Name, and User Logon Name (e.g., user1). Click Next.
• Set a secure temporary password. Ensure the box "User must change password at next logon" is checked. Click Next, then Finish.

Section 2: Joining the Client Windows PC to the Domain

• On the Windows 10 client, open File Explorer, right-click This PC, and select Properties.

• Scroll down and click Advanced system settings (or Rename this PC (advanced) depending on your Windows 10 build).
• Navigate to the Computer Name tab and click Change.

• Under "Member of", click Domain and type your domain name. Click OK.
• When prompted, enter the Domain Administrator credentials to authorize the join.
• A dialog box will appear reading, "Welcome to the lab.local domain." Click OK and restart the PC to apply the changes.

🛠️ Troubleshooting a Common Network Error

During my first attempt, the client PC threw a familiar enterprise error:

"An Active Directory Domain Controller for the domain could not be contacted."

How I diagnosed and fixed it:

1. I opened the Command Prompt (cmd) on the Windows 10 client and ran ping lab.local. The packets timed out.
2. I realized the client machine was looking at my local router for DNS instead of the Domain Controller.
3. I opened Network Connections on the client, went to the IPv4 properties of the network adapter, and manually changed the Preferred DNS server to the static IP of my Windows Server (192.168.56.10).
4. After flushing the DNS cache, the ping lab.local command succeeded. I re-attempted the domain join, and the machine connected instantly.

The Takeaway

Creating user accounts and joining workstations to a domain are fundamental daily tasks for any Helpdesk technician. Mastering these basics in a homelab environment provides a massive advantage, ensuring you understand not just how to click through the menus, but how underlying dependencies like DNS make enterprise networking possible.