I’ve set up AD DS more times than I can count—across Server 2008, 2012 R2, 2016, and now 2022. Each version has its quirks, but the core steps haven’t changed much. Still, I figured I’d document my latest setup on Server 2022, just in case someone else hits the same snags I did.
This wasn’t a lab experiment—I ran this on a Hyper-V VM with 32GB RAM, nested inside my dev environment on a ThinkPad P1. Not the fanciest setup, but solid enough for testing domain roles and group policies without frying production.
Why I Went With AD DS on Server 2022
I needed a clean forest for testing some GPO behavior tied to Windows 11 clients. I could’ve gone with Server 2019, but I wanted to see how 2022 handled the newer security defaults and DNS integration. Plus, I was already knee-deep in Admin Center testing, so it made sense to keep the stack current.
Step-by-Step Walkthrough
1. Launch Server Manager
Not gonna lie, I still default to Server Manager out of habit—even though Admin Center is getting better. Hit the Windows key, type “Server Manager,” and you’re in.
Click “Add roles and features.” Easy start.
2. Role-Based Installation
Skip the fluff on the “Before You Begin” screen. Choose “Role-based or feature-based installation.” If you’re doing this on a remote box, make sure it’s listed in the server pool.
3. Select AD DS Role
Check “Active Directory Domain Services.” You’ll get a pop-up asking to add required features—just click “Add Features” and move on.
4. Skip Extra Features
Unless you’re bundling DHCP or Certificate Services, just hit “Next.” I kept it lean for this test.
5. Confirm and Install
Review your selections. I usually double-check the server name here—once, I installed AD DS on the wrong VM and spent an hour wondering why my domain wasn’t resolving.
Click “Install.” The progress bar crawls, then finishes.
6. Promote to Domain Controller
Here’s where things get real. Click “Promote this server to a domain controller.”
I chose “Add a new forest” and used lab.local as my root domain. Functional levels? Went with Windows Server 2022 for both forest and domain—no legacy clients in this setup.
Set your DSRM password. Don’t reuse your admin password here. Trust me.
7. Prerequisites Check
This part always feels like a mini exam. If you’ve got static IP set and DNS configured, it should pass. If not, expect a red warning and some head-scratching.
Click “Install.” The server reboots automatically.
8. Post-Reboot Checks
Log in with your domain credentials. Open Server Manager and check that both AD DS and DNS roles are listed.
9. Verify in ADUC
Go to “Tools” > “Active Directory Users and Computers.” You should see your domain and default containers like Users and Computers.
I usually create a couple of test OUs here just to confirm replication and GPO targeting later.
What Went Wrong (And What I Learned)
- The install screen froze once—just black, silent, almost mocking me. Turned out Hyper-V had throttled disk I/O. A quick restart fixed it.
- DNS didn’t auto-configure properly. I had to manually set the loopback address (
127.0.0.1) as the preferred DNS server before promotion. - I skipped setting a static IP once. Rookie mistake. AD DS needs that stability.
Final Thoughts
Setting up AD DS on Server 2022 isn’t rocket science, but it’s easy to miss small things—like DNS bindings or functional level mismatches. I’ve learned to slow down during the “Promote” phase and triple-check IP settings before hitting “Install.”
Ever had AD DS fail mid-promotion? Or seen a domain controller vanish from the network after a reboot? Drop your war stories below—I’m always curious how others navigate this setup.
