Start at the beginning: turn a standalone Windows Server into a working domain. You'll install the AD DS role, promote the server to a domain controller, confirm the promotion actually succeeded, join a member server to the domain, and move FSMO roles between DCs.
The objects you'll touch every day. You'll create user accounts in Active Directory Users and Computers, put a group-based access model in place instead of assigning permissions one user at a time, and design an OU structure you can safely delegate to other admins.
Group Policy is where most AD questions actually land. You'll build a GPO that maps a network drive, then use the two tools every admin reaches for — gpresult and Resultant Set of Policy — to prove which settings applied, which didn't, and why.
Do the same work again from the console. Using the Active Directory module, you'll create, modify, and disable user accounts with cmdlets — the foundation for onboarding and offboarding scripts you can run against a whole list of users instead of one at a time.
