Lab 01: Domain Controller Foundation

Overview

In this lab, I provisioned DC1, installed Active Directory Domain Services, promoted the server to a domain controller, and created the internal Active Directory forest corp.nietz.co.uk with NetBIOS name CORP.

This lab establishes the identity foundation for later domain join, user administration, file share, Group Policy, hybrid identity, and Intune labs.

Objective

The objective was to build a stable on-premises Active Directory domain controller with integrated DNS and confirm that authentication, directory services, and domain controller discovery were working correctly for future hybrid Microsoft labs.

Environment

Configuration

2. Server Network Configuration

I configured DC1 with a static IP address and set DNS to point to the server itself.

Context: Active Directory relies on DNS. A domain controller needs stable addressing so clients can locate domain services.

3. AD DS Role Installation

I installed the Active Directory Domain Services role from Server Manager and added the required management tools.

Context: Installing AD DS adds the components required for promotion, but the server is not a domain controller until promoted.

4. New Forest Creation

I promoted DC1 and created a new forest using corp.nietz.co.uk as the root domain.

Context: The forest is the top-level Active Directory boundary for the on-premises identity environment.

5. Domain Controller Promotion

I reviewed the promotion settings, kept DNS Server and Global Catalog enabled, confirmed CORP as the NetBIOS name, and completed the promotion.

Context: Promotion creates the directory database, DNS zone, SYSVOL, NETLOGON, and the first domain controller services.

6. ADUC Validation

I opened Active Directory Users and Computers and confirmed that the corp.nietz.co.uk domain tree was visible.

Context: ADUC confirms that the directory exists and can be browsed using a standard administration console.

7. PowerShell Validation

I validated the forest and domain configuration using administrative tools and confirmed that the Active Directory structure was functioning correctly.

Context: PowerShell provides consistent administrative validation of the domain, forest, and Active Directory configuration without relying only on graphical tools.

8. DNS Zone Validation

I opened DNS Manager and confirmed that the corp.nietz.co.uk forward lookup zone existed with the correct domain controller records.

Context: AD DS depends on DNS records so clients can locate domain controllers and services.

9. DNS and Domain Controller Discovery

I validated DNS resolution and domain controller discovery to confirm that clients could locate and communicate with DC1 successfully.

Context: Domain join and authentication depend on DNS and domain controller discovery.

10. Domain Controller Health Check

I validated domain controller health and confirmed that DNS, Active Directory, and Netlogon services were functioning correctly.

Context: DCDIAG provides support-level evidence that DC1 is healthy after promotion.

Validation

The lab was validated when DC1 successfully functioned as a domain controller, Active Directory Users and Computers displayed the corp.nietz.co.uk domain structure, DNS Manager showed the AD-integrated forward lookup zone, and PowerShell confirmed the forest and domain configuration.

DNS resolution and domain controller discovery were successfully validated, confirming that corp.nietz.co.uk resolves to DC1 and that the domain controller can be located for authentication and domain join operations.

Domain controller health checks confirmed that DNS, Active Directory, and core domain services were healthy, leaving the environment ready for the next lab.

Key Technical Outcomes

This lab reinforced how critical DNS is to Active Directory and how authentication, domain join, Group Policy, and user logon all depend on healthy name resolution.