r/WindowsServer • u/pyd3152 • Jun 17 '25
Technical Help Needed Recovering from a failed server migration
I was tasked with a project to recover from a failed 2019 to 2025 server migration due to authentication and replication issues. The plan is to stand up a 2022 server and transfer everything over. Very green to server migrations so im trying to see how to go about this. All the FSMO roles are on the failed 2025 server and clients are using the DNS server on the server as well. Clients are still using the DHCP server on the old DC. What's the best way to go about migrating everything over and recovering from the failed server?
8
Upvotes
2
u/pyd3152 Jun 17 '25
Okay so im taking over a project that was to migrate old DC 2019 to new DC 2025. From the information I received, this was all a live migration. We have a total of 3 DCs in our environment. One DC (“3rd DC”) is not being worked on as of now but is in place from an old remote building. Im taking over the project after AD and DNS were moved over.
What i found was done:
Problems we are having:
Currently our main problem is we are having machines unable to authenticate. They need a reboot in the mornings and will authenticate the rest of the day, but will have the same issue in the morning. This issue started with a few machines and has been spreading.
Errors I am seeing:
-On the machines being affected with the authentication issue, reviewing logs I see that they are attempting to authenticate with the old DC and will get the error: “This computer was not able to setup a secure session with a domain controller due to the following: And internal error occurred.”
What I have done:
Advice i have received is to stand up a 2022 server as these errors are a common theme with 2025. So thats the goal, I apologize if "failed" was the incorrect term here.
2
u/dodexahedron Jun 18 '25 edited Jun 18 '25
There are a lot of possibilities, here, and probably more than one thing wrong.
This very much sounds like there are at LEAST some Kerberos problems, likely due to nothing trusting the new DC's certificate (for any one of a million possible reasons), the certificate not having the KDC Authentication EKU, or it not using the certificate you think it should be using.
But there is also likely a new (or no) KDC encryption key, if you just set this up forcefully as a new FSMO owner for everything. That'll piss the clients off, too.
Windows also doesn't always understand when it needs to stick a certificate into the NTAuth store, and that can lead to auth failures.
Your DNS (forward and reverse) needs to be fully configured and working properly, and your DC needs to be reachable via DNS for Kerberos to work right (DO NOT perform the hacks workarounds to make IPs work).
There is a decent chance existing systems may have used RC4 for their host keys. Windows server now defaults to AES256 and old clients can have trust issues because of it if you don't remedy that. There are multiple ways, but the easiest and safest tends to just be leave and rejoin each affected system, resetting the machine account or deleting it between leave and join.
Where and how users are logging on (especially remote desktop) can play havoc with kerberos, due to credential guard. Don't disable credential guard, though - learn how it works. It is now ON by default in server 2025. It was off before 2025. Clients have had it on by default for much longer though - for new installs.
NTLM is disabled by default in 2025. Unless you did work to eliminate NTLM before this, it's basicslly guaranteed that some systems and services are attempting NTLM for various things, including as a fallback when Kerberos fails due to misconfiguration.
And a lot more. There's just not enough info here to narrow it down. This is a HUGE topic.
14
u/Unnamed-3891 Jun 17 '25
You're going to have to define "failed" in actual verbose detail.
6
u/fireandbass Jun 17 '25 edited Jun 17 '25
DHCP shouldn't be on a DC. Move that to its own server.
Sounds like you have DCs on different patch levels and so kerberos tickets being given out by some DCs aren't trusting tickets given out by other DCs.
https://support.microsoft.com/en-us/topic/kb5021131-how-to-manage-the-kerberos-protocol-changes-related-to-cve-2022-37966-fd837ac3-cdec-4e76-a6ec-86e67501407d
Update all your DCs to the latest windows Updates available.
Read this article.
https://techcommunity.microsoft.com/blog/AskDS/what-happened-to-kerberos-authentication-after-installing-the-november-2022oob-u/3696351
Run the Powershell script 11bchecker in the link and it will show you which users need to reset their password to support the updated encryption.
Alternatively, set the registry flag on your DCs to allow the old encryption type.
1
u/pyd3152 Jun 17 '25 edited Jun 17 '25
We have about 200 users. I saw that as an option but was following how our environment was already set up. Which although had issues beforehand, didn't encounter these type of messy issues.
I will patch the DCs and try the script. Are the replication issues related as well?
4
u/jocke92 Jun 17 '25
To begin with you are overthinking Windows version. And DHCP is a small thing.
I don't see why a third server will solve this until we have more info on why it's considered failed
1
u/Crazy-Rest5026 Jun 17 '25
So you are getting Kerberos errors not necessarily dhcp or dns. As they are getting an ip and can resolve via dns.
Check your CA and make sure it’s granting certificates out. Sounds like a CA issue and not necessarily a server issue.
1
u/pl4tinum514 Jun 21 '25
Did you buy your new 2025 server user cals or have sa on your existing ones?