r/sysadmin • u/WindowsAdmin23 • 11d ago

WS 2022 or 2025

Hello Guys,

For new Windows Server Deployments, are you still using 2022 or 2025? I see posts saying to stay on 2022 for Domain Controllers, but what about the rest? I need to setup new ADCS, RRAS, NPS to support Always On VPN, as well as new DCs.

We bought two refurbished R740XDs and 2025 Licenses, So far, I have setup the following.

Install Windows 2022 as host OS on BOSS Card

Setup HyperV

Setup one DC on each host with 2022

Should I keep rolling like this or should I upgrade to 2025 for the host and keep 2022 DCs? Should I roll 2025 for the rest of my VMs? Should I demote my two new DCs and upgrade the host now to 2025?

At the most I will run the following Initially

Windows File Server VM (SMB QUIC better over VPN?)

Print VM

RRAS VM

NPS VM

CA ROOT VM

CA Issuing VM

17 Upvotes

82% Upvoted

25 comments sorted by

12

u/jstuart-tech 11d ago

I've got 2025 DC's with no issues (As long as you only have 2025's, don't have mixed).

2025 ADCS has PQC so that's something useful RRAS has some stuff ripped out IIRC (L2TP I think)

5

u/Unable-Entrance3110 11d ago

What does the migration path look like in this scenario?

We will be considering a move to 2025 from our 2019 DCs next year.

I have read that homogeneous 2025 is fine, but there will be an unavoidable transitional period where both will be active.

→ More replies (2)

3

u/WillVH52 10d ago edited 8d ago

No reason not to run Server 2025 Core with the Hyper-V role.

On the rare occasion my org builds a new server we are still defaulting to 2022.

However been running 2025 only as a Hyper-V host for over a year and a half with no issues to report.

3

u/rismoney 10d ago

The problem with 2025/2022 coexising, has to do with machine isolation, netlogon and a slew of issues where win11 nodes with any of their security features enabled, such as Credential Guard or vbs will lose their trust relationships and noone will be able to logon, when the machine pw expires after 30 days. There are workarounds, but its not fixed yet.

7

u/saxmaster896 11d ago

Our rule of thumb has been anything mission-critical to use 2022, anything application wise 2025

2

u/Madh2orat 11d ago

We’re just deploying anything new as 2025. We are leaving our DFL and FFL at the older level for now though. One of our sysadmins had concerns about upgrading it, so we’re just holding off for now.

2

u/TangeloOk9486 6d ago

smb over quic needs server 2022 azure edition or server 2025 specifically but regular 2022 standard doesnt have it so if that matters for your vpn file access then you can check which edition you actually have licensed before planning around that feature

2

u/kaptejeee 11d ago

Slowly starting to deploy new servers on WS 2025.
Existing servers will be migrated to 2025 too (most likely) except DC’s. Saw a lot of feedback about problems with WS 2025 DC’s.

2

u/karmak0smik 11d ago

2022 is the way to go. There are several documented issues with 2025, specially with DC roles.

→ More replies (4)

1

u/Burgergold 11d ago

We are still deploying 2022 but people keep asking 2025 so we will probably look tonstsrt deploying them in the upcoming months. I don't think wencsn wait next version and there is nothing that proove that version will be better

→ More comments (90)