This message was deleted.

Server 2022 has slightly worse performance than 2019 - check out this article (it's from september 2021 so things may have changed since then) https://www.go-euc.com/windows-server-2022-performance-testing/

Thanks, Patrick!

Same goes for 2019 compared to 2016. And the same goes for 2016 compared to 2012 🙂

That said, 2019 looks easier on the CPU compared with 2016 in the above article... the main driver here is OneDrive for FileSync and Storage Sense so I'm leaning towards 2019 as that will do the job without so much tax on the resource...

EOL for 2019 is jan 2024. So less than a year. We run 2019 - no issues. But already planning to move to 2022. Keep good notes on issues/fixes as I will sure ask for them 8-) And If you going to do any performance testing for user density - launch Teams for those test users. Our current 2019 issues: Searhindexer sometimes prevents users sessions from logout. (Doesn’t happen often - we keep checking sessions running over session limit and killing searchndexer there.) RAM cache filling (also not something which is happening often, not often enough to find the root cause) Couple of Windows Update related issues - these were cough during UAT and weren’t released to Prod - (start menu not launching, one drive not signing in) VDA 2203 CU2 - significant increase in ICA Latency + Teams sometimes not turning on optimisation- we are in a proceed to rolling back to 1912 CU6

Nice insights, Vadim... extended support runs until 2029 for reliability/sec patches which is key... I'll need to weigh up the performance hit/cost of infra.. . Azure is on the cards for for the client so I see tis being required for 18 months to 2 years...

for 2019 the extended is 2029. Kind of like Server 2012R2 is for Oct 2023