Summary
Highlights
The video begins with an introduction to Active Directory, highlighting its importance as the cornerstone of a network environment. The presenter outlines the plan to build two virtual machines: a Windows Server 2022 acting as the domain controller for 'corp.acme.com', and a Windows 10 client PC to be joined to the domain.
The first step is to configure the Windows Server 2022 machine. This involves renaming the machine to 'dc01' and assigning a static IP address (192.168.0.1), which is a best practice for domain controllers.
The process of adding the Active Directory Domain Services role begins. The presenter navigates through the server manager, selecting AD DS and agreeing to install its associated management features, including Group Policy Management. It's noted that AD DS integrates with DNS and will offer to install DNS if not already present.
After the role installation, the server is promoted to a domain controller. This involves creating a new forest and a new domain. The chosen domain name is 'int.acme.com', following best practices to prepend an internal domain reference to avoid split-brain DNS issues. A Directory Services Restore Mode (DSRM) password is also set.
The NetBIOS name is customized from 'INT' to 'ACME' for user-friendliness, as this is what users will see when logging into the domain. A prerequisite check is performed, and upon successful completion, the installation proceeds, which includes a mandatory server reboot.
After the reboot, the server is now a domain controller. The presenter logs in using the 'ACME' NetBIOS domain. Verification steps include checking that the server is now a domain-joined machine and that Active Directory and DNS tools are available. The DNS forward lookup zones are confirmed, and a reverse lookup zone is manually created, configured for secure dynamic updates.
To further enhance the environment, the DHCP role is installed. This is done after AD DS so that DHCP can leverage Active Directory credentials for management. A new DHCP scope named 'acme ipv4' is created, assigning IP addresses from 192.168.0.50 to 192.168.0.200, and configuring the default gateway and DNS servers.
A Windows 10 client PC (pc01) is used to test the DHCP assignment and join the domain. The client successfully obtains an IP address from the DHCP server. The PC is then joined to the 'int.acme.com' domain using domain administrator credentials.
Back on the domain controller, Organizational Units (OUs) are created within Active Directory Users and Computers. An 'Acme' OU is created, followed by nested 'IT' and 'Staff' OUs. User accounts 'troy' (tberg) and 'batman' (bman) are created within their respective OUs. Troy is granted 'Domain Admins' privileges.
The video concludes by testing the newly created user accounts on the client PC. Troy (tberg) successfully logs in, demonstrating authentication against the Active Directory domain. Batman (bman) also logs in, and due to a checkbox selected during his account creation, is prompted to change his password on first login, further validating the Active Directory environment's functionality.