🛡️ Deploying Active Directory on Windows Server

This project demonstrates the step-by-step process of deploying Active Directory (AD) within a Windows Server environment. The lab includes setting up a domain controller, creating user accounts, and joining a Windows client to the domain. This project highlights my knowledge in Windows Server administration and Active Directory fundamentals — critical skills for IT support and system administration roles.

---

Lab Overview (Screenshots + Descriptions)

1. Installing Active Directory

Here, we begin by installing the Active Directory Domain Services (AD DS) role on the Windows Server using Server Manager. This is the foundational step to promoting a server to a Domain Controller.

---

2. Adding a Domain Controller

After the role installation, we promote the server to a Domain Controller, creating a new forest and domain (e.g., corp.local). This step includes setting a DSRM password and configuring DNS integration.

---

3. Domain Configuration Confirmation

This step confirms the successful setup of our new domain. The system restarts as part of the Domain Controller promotion process.

---

4. Active Directory Users and Computers

Once the server is promoted, we open the Active Directory Users and Computers console. This GUI allows management of users, groups, and organizational units (OUs).

---

5. Creating an Admins Folder

We create a new Organizational Unit (OU) named Admins to logically separate and manage admin-level users. OUs help organize and apply group policies effectively.

---

6. Creating a New User

We create a new user account within the Admins OU. User accounts in AD represent real individuals and their credentials used to authenticate across the network.

---

7. Adding User to Domain Admins

The new user is added to the Domain Admins security group. This grants them elevated permissions across the domain, including full control over all domain controllers.

---

8. Adding a Client to the Domain

We switch to a Windows client machine and initiate the process to join it to our domain (corp.local). This allows centralized authentication and management via AD.

---

9. Successfully Joined Client

The client was successfully joined to the domain. A restart is typically required to complete this process.

---

10. Client Now in Domain

We log in with our domain credentials, confirming the client is now part of the AD domain. This means user policies, network drives, and other domain resources can be accessed securely.

---

🚀 Skills Demonstrated

• Windows Server 2019/2022
• Active Directory Domain Services
• Organizational Units and Group Policies
• Domain Controller configuration
• User & Group Management
• Client machine domain joining

---

💼 Why This Matters

This lab reflects hands-on experience with a foundational infrastructure technology used in nearly every mid-to-large business environment. As a future IT professional, being able to deploy and manage Active Directory proves I’m ready to support real-world enterprise environments.

---