trustmebro.reviews

Windows Server 2022

Software Tool · Windows, macOS & other OS · 15 mentions · 1 subreddit · discussed in r/sysadmin

Reddit take

Not enough linked mention summaries yet; the source excerpts below are the evidence.

Pros

  • Honestly as long as you migrate the FSMO roles and have at least 3 total DCs, you can usually do in place upgrades by now. Should something go wrong you still have a safety factor while standing up a new one.
  • I googled the steps and cleanly migrated from 2012 r2 to 2022. I did add a new 2022 dc virtual machine to start the AD upgrade.
  • Create new VM with Server 2022 Standard, do not use 2025 at this time as there are many known issues
  • Frankly though, do not use 2025 for AD at all for the medium term: stick to 2022.
  • 2022 if you want stable.

Cons

  • We had to upgrade to 2022 because 2016 was EOL soon and Teams was not supported, etc. And we ran into similar issues. 2022 performance was worse.
  • we are able to boot the OS but it loade automatic repair and then BSOD with error "**Driver Verifier DMA Violation"** and reboot and bootlooping**.
  • Windows Server 2022 did improve a lot of things, but there’s simply no trust left in the Windows Server team.
  • If you go for 2022 you'll need to follow the upgrade path in steps one at a time.
  • We migrate to 2022 for now, but you have to do it in steps, i.e 2012 > 2016 > 2019 > 2022. I actually had to revert a snapshot for some servers because the in place upgrade broke the services, so please have a backup plan.

Sentiment

8 positive (53%) · 2 mixed (13%) · 5 negative (33%)

Trust + time weighted score: +19% · raw score 20%

What redditors said (10 of 15)

We had to upgrade to 2022 because 2016 was EOL soon and Teams was not supported, etc. And we ran into similar issues. 2022 performance was worse.
negative · u/w****t · r/sysadmin · comment · Dec 17, 2025 · open on Reddit ↗
we are able to boot the OS but it loade automatic repair and then BSOD with error "**Driver Verifier DMA Violation"** and reboot and bootlooping**.
negative · u/C****4 · r/sysadmin · Dec 15, 2025 · open on Reddit ↗
Honestly as long as you migrate the FSMO roles and have at least 3 total DCs, you can usually do in place upgrades by now. Should something go wrong you still have a safety factor while standing up a new one.
positive · u/N****o · r/sysadmin · comment · Dec 1, 2025 · open on Reddit ↗
I googled the steps and cleanly migrated from 2012 r2 to 2022. I did add a new 2022 dc virtual machine to start the AD upgrade.
positive · u/D**v · r/sysadmin · comment · Dec 1, 2025 · open on Reddit ↗
Create new VM with Server 2022 Standard, do not use 2025 at this time as there are many known issues
positive · u/M****l · r/sysadmin · comment · Nov 19, 2025 · open on Reddit ↗
Frankly though, do not use 2025 for AD at all for the medium term: stick to 2022.
positive · u/j****2 · r/sysadmin · comment · Nov 10, 2025 · open on Reddit ↗
Windows Server 2022 did improve a lot of things, but there’s simply no trust left in the Windows Server team.
mixed · u/N****8 · r/sysadmin · comment · Aug 25, 2025 · open on Reddit ↗
2022 if you want stable.
positive · u/d****r · r/sysadmin · comment · Aug 4, 2025 · open on Reddit ↗
If you go for 2022 you'll need to follow the upgrade path in steps one at a time.
negative · u/L****d · r/sysadmin · comment · Aug 4, 2025 · open on Reddit ↗
We migrate to 2022 for now, but you have to do it in steps, i.e 2012 > 2016 > 2019 > 2022. I actually had to revert a snapshot for some servers because the in place upgrade broke the services, so please have a backup plan.
mixed · u/h****e · r/sysadmin · comment · Aug 4, 2025 · open on Reddit ↗

Compare

Related