This project demonstrates the setup of a virtual Active Directory environment using Oracle VM VirtualBox. This README provides a detailed process, with screenshots, for building and configuring an AD setup including a Domain Controller (DC) and client machines. This setup is valuable for IT Help Desk tasks such as user management, Group Policy configuration, and network troubleshooting.
The goal of this project is to create a fully functional AD environment, simulating a real-world IT environment where users, groups, and policies can be managed. This setup includes:
- A Domain Controller to host the Active Directory and DNS services.
- Client machines joined to the domain, demonstrating communication and policy enforcement.
- Documentation and screenshots throughout the process for learning and future reference.
- Project Setup
- Network Configuration
- Domain Controller Installation and Configuration
- Adding Client Machines
- Testing and Validation
- Screenshots
- Conclusion
- Oracle VM VirtualBox: Installed and configured.
- Windows Server and Windows 10 ISOs: For setting up the Domain Controller and client machines.
- Minimum Requirements:
- 4GB RAM for the DC VM, 2GB RAM for each client.
- 40GB of disk space per VM.
This repository contains:
README.md: Project documentation and setup guide.assets/: Folder for screenshots and other project-related images.
All VMs are configured to communicate within a private Internal Network in VirtualBox. This ensures network isolation and allows the DC to manage DNS and authentication for client machines.
- Set up the Internal Network in VirtualBox.
- Assign static IP addresses to each VM:
- Domain Controller:
192.168.0.69 - Client machines:
192.168.0.11,192.168.0.12
- Domain Controller:
The DC serves as the backbone of this setup, managing Active Directory and DNS.
- Install Windows Server on the VM designated as the Domain Controller.
- Configure the server with a static IP and hostname.
- Install the Active Directory Domain Services role.
- Promote the server to a Domain Controller, creating a new forest (in this case it is
gibdoguts.local). - Configure DNS to handle requests for the domain.
Each client machine is added to the domain to simulate a managed environment.
- Install Windows on each client VM.
- Configure each client with a static IP and set the DC as the primary DNS server.
- Join each client machine to the domain.
- Restart each client to complete the domain join.
With the environment configured, various tests ensure AD and network functionality.
- Connectivity: Verify that clients can communicate with the Domain Controller.
- User and Group Management: Create and test login for domain users.
- Group Policy Application: Apply policies on the DC and confirm they propagate to clients.
The following screenshots demonstrate key steps in the setup process:
The following screenshot shows the Active Directory Domain Services role successfully installed on the Domain Controller.
Server Manager showing Active Directory Domain Services successfully installed and operational on the Domain Controller.
The following screenshot shows the DNS Manager with the forward lookup zone configured for gibdoguts.local. This setup is essential for managing domain name resolution within the Active Directory environment.
DNS Manager with gibdoguts.local forward lookup zone configured on the Domain Controller.
The following screenshots demonstrate the process of joining Client1 to the Active Directory domain gibdoguts.local and logging in with a domain user account.
In the Computer Name/Domain Changes window, we specified the domain gibdoguts.local for Client1 to join.
Setting up Client1 to join the gibdoguts.local domain.
After providing the domain credentials, we received a welcome message indicating Client1 was successfully added to the domain.
Client1 successfully joined to the gibdoguts.local domain.
After restarting, we logged in to Client1 using the domain user account johnsmith, confirming successful authentication to the domain.
Domain user johnsmith logging in on Client1 after joining the domain.
To demonstrate Group Policy, we created a policy to prevent users from accessing the Control Panel on domain-joined machines.
The Disable Control Panel Access GPO was created in Group Policy Management to restrict user access to the Control Panel.
Group Policy Management Console showing the Disable Control Panel Access policy.
After applying the Group Policy, attempts to open the Control Panel on Client1 are blocked.
Client1 showing a message that access to the Control Panel is restricted by Group Policy.
Each screenshot is saved in the assets folder for easy reference.
This Active Directory setup project provides a hands-on demonstration of creating and managing a virtualized AD environment, equipping me with foundational skills essential for an IT Help Desk role. By completing this setup, I gained experience with user and group management, Group Policy enforcement, and network troubleshooting within a domain environment.
For any questions or collaboration requests, feel free to reach out!