I'm dealing with some serious problems after upgrading to Server 2025 while trying to set up a Hyper-V cluster and SCVMM. Our Domain Controllers (DCs) are on Server 2019, and the forest domain is at the 2016 level. After the upgrade, we started experiencing numerous errors, including Event 5719 (NETLOGON) and various Kerberos-related authentication failures. I've been troubleshooting alongside Microsoft, but we even set up a fresh 2025 machine in a different OU only to encounter the same issues.
Has anyone faced similar problems with Server 2025, especially regarding Kerberos? Is there a known fix or should we consider rolling back to Server 2022?
5 Answers
You're not alone! I saw a similar post about 2025 Kerberos issues recently, and the top suggestion was indeed to downgrade to 2022. It seems that's the most common fix these days.
We've been experiencing the 5719 NETLOGON event too on various builds, and while it’s been a nuisance, we think it might just be cosmetic. However, there are definitely some fundamental problems with Server 2025 overall, including reliability issues across the board.
I think the security settings for domain controllers may have changed with Server 2025, especially with LDAPS being enforced by default. There might be similar changes affecting Kerberos as well.
From what I've heard, Server 2025 is pretty buggy, especially concerning the DC role. If you're facing these kinds of problems, I'd recommend downgrading to Server 2022 until they sort out 2025. It’s just not worth the headache right now.
We decided to roll everything back to Server 2022 recently. Server 2025 was giving us such a hard time, and after dealing with Microsoft Support, we just couldn't wait around anymore. It’s not worth touching 2025 for now!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures