VMware Workstation & Hyper-V:
Building a Windows Server Domain Lab
Virtualization provides IT professionals with the ability to simulate enterprise-level infrastructure on a single computer. Using VMware Workstation and Hyper-V, I built a lab that replicated a real-world Windows Server environment. This blog post walks through the detailed process of installing servers, configuring Active Directory, linking Group Policy Objects, and setting up essential services like DHCP, DNS, and SMTP.
Installing and Setting Up Windows Server 2016/2019
The lab began with deploying Windows Server 2016 and 2019 virtual machines in VMware Workstation and Hyper-V. Linked clones were used to save time and disk space while still providing unique machines for testing. After the operating systems were installed, I configured Remote Desktop Protocol (RDP) access to allow for easier remote management of the servers.
Once the base servers were set up, I promoted one of the servers to act as a Domain Controller (DC). This step included installing the Active Directory Domain Services (AD DS) role and creating a new forest/domain.
Adding Windows 10 Clients to the Domain
To simulate a workplace environment, I provisioned multiple Windows 10 client machines. These clients were configured to use the Domain Controller as their DNS server, enabling them to locate and join the domain.
After joining the domain, I verified centralized authentication by logging in with Active Directory user accounts. This step demonstrated how IT administrators can easily manage user access and enforce security policies across all domain-joined machines.
Active Directory Template Accounts
To streamline user management, I created template user accounts in Active Directory. These accounts had pre-configured settings such as group memberships, organizational unit (OU) placement, and profile paths.
By copying and modifying template accounts, I was able to rapidly provision new user accounts with consistent configurations. This reduces administrative errors and speeds up the onboarding process in enterprise environments.
Creating and Linking Group Policy Objects (GPO)
Group Policy Objects (GPOs) were created and linked to organizational units (OUs) in Active Directory to enforce company-wide policies. Some of the key GPO configurations included:
- Enforcing password complexity and expiration policies
- Restricting user access to control panel settings
- Configuring desktop backgrounds for organizational branding
- Enabling automatic Windows Updates
By testing these policies on client machines, I confirmed that settings were applied consistently across the domain.
Deploying Network Services: DHCP, DNS, and SMTP
To make the environment fully functional, I deployed additional Windows Server roles:
- DHCP (Dynamic Host Configuration Protocol): Configured to automatically assign IP addresses, gateway, and DNS settings to client machines.
- DNS (Domain Name System): Integrated with Active Directory for name resolution, allowing machines to locate domain controllers and services.
- SMTP (Simple Mail Transfer Protocol): Set up for testing email relay and system notifications within the lab.
These services provided the backbone of the domain, ensuring seamless communication between devices and simulating the functionality of a production network.