I'm currently working on a major server migration for a client who has around 18-19 virtual machines running Windows Server 2016. We're upgrading them to Windows Server 2025. The migration has gone smoothly until I tried promoting the domain controller to Server 2025. After I do that, the server fails to allow logins, and the client is unable to print or reset their passwords through Azure SSO. I've managed to get around this issue by tweaking the KDC service, but it feels like a workaround rather than a solution. Interestingly, I can promote a Server 2022 VM without any issues, but the team insists on using Server 2025. Is there a way to resolve these problems or is Server 2025 just as unreliable as Windows 11? I've also faced issues with Active Directory sync since starting with 2025, which I managed to fix, but how can I make Server 2025 stable like 2022?
2 Answers
If you're looking to fix Server 2025, the best advice is to hold off until the first Service Pack is released before deploying it. It's usually a bad idea to use the initial release of a server OS on critical systems. Waiting can save you a lot of headaches later.
A lot of folks here suggest skipping Windows Server 2025 for Active Directory Domain Services for now. There's a general agreement that it’s pretty unstable at the moment and offers little in terms of security or new features for most users. Besides, Windows Server 2022 still has plenty of support left!
Totally get that! Unfortunately, I don't make the budget decisions, so I’m stuck trying to make the best of it.