What do we do with Windows Server 2019 heading to 2029?
Mainstream support has ended, extended support continues. Start mapping now which roles move to 2022, 2025 or cloud.
support/servers-on-premise/windows-server-2019-end-of-support-2029steps: 4
Try this first
- List every 2019 server and its role
- Per role decide: replace with 2022 or 2025, or move to cloud
- AD, file and print last, easy roles first
- Budget replacements spread over multiple years
When to bring us in
Anything older than 2019 still running (2012 R2, 2016 out of support): set a hard cutoff instead of endless delay.
See also
- One DC or two DCs for an SMB office?Two is almost always the right answer; one DC is a single point of failure for logon, DNS and GPOs.
- Should I split FSMO roles across two DCs?For a small domain all on one DC is fine; with two DCs splitting is tidier but not required.
- How do I know my AD replication is healthy?Replication errors creep in silently; they only surface when logins or GPOs misbehave.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.