Hey folks,
I'm dealing with a bit of a headache here after cloning my Windows Server 2016. Here's what's going on: I have my original server, called `KK2020 - original`, and then there's the clone, `K2025 - clone`. Both servers are on the same Active Directory domain, and I can log into both with domain credentials without any issues. They've got different SIDs, IP addresses, names, and certificates, and their MAC addresses aren't identical either.
While I can connect to the clone via RDP just fine, connecting to the original server is a no-go when both servers are online. All the settings seem fine on the virtual machine, but the event logs on the original server are showing some concerning errors, particularly in the TerminalServices logs, such as Error during transition from CsrConnected,
Session disconnections with various reason codes, and some event IDs related to remote connection management.
I've tried troubleshooting steps like verifying SPNs, purging Kerberos tickets, clearing the DNS cache, restarting the TermService, checking the SSL certificate registry key, and even manually adding the certificate thumbprint, but nothing seems to work. I suspect the issue might stem from the original server not accepting RDP connections because it's terminating sessions.
Any advice or insights would be super helpful! Thanks!
2 Answers
Did you run sysprep on the clone? That's usually a necessary step after cloning a server to ensure everything is configured properly.
If you haven't already, you might want to check this issue that's been discussed before—it might be related to Microsoft’s KB 5065426, which affects RDP sessions after cloning.
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