Forum Discussion
Solved
DCPromo to remove AD DS fails with "Logon Failure: The target account name is incorrect."
Good thing this is just my test network! I have a VM clone of my ancient WS 2008 R2 ("OldDC") running AD DS in a test network along with two spiffy new instances of WS 2022 (NewDC1 and NewDC2), both ...
- Thanks for the reminder. After trying a bunch of different things, I ended up trying an in-place upgrade to Server 2012 R2. After the upgrade finished, not only were the credentials fixed for OldDC, they also were fixed for OldDC2.
I did not try running dcpromo, because I am thinking that I may no longer want to demote them if I can upgrade them (testing applications as we speak!), but I was able to browse from both OldDC and OldDC2 to shares on NewDC1 and to NewDC2, whereas previously I could not, and previously browsing to those shares generated the same error that popped up when attempting to finish dcpromo, so I am guessing they had the same root cause.
Thanks! The roles have been seized already (see last paragraph).
My problem is that I still want to use OldDC on the domain as a non-DC member server. Is there a way to convince this box not to be a DC any more?
My problem is that I still want to use OldDC on the domain as a non-DC member server. Is there a way to convince this box not to be a DC any more?
Yes, just do the mentioned cleanup. I don't think it will remove it from the domain, but worst case you could join it again as a member server.
TheWaterbug just checking if there's any progress or updates? please don't forget to mark helpful replies.
- Thanks for the reminder. After trying a bunch of different things, I ended up trying an in-place upgrade to Server 2012 R2. After the upgrade finished, not only were the credentials fixed for OldDC, they also were fixed for OldDC2.
I did not try running dcpromo, because I am thinking that I may no longer want to demote them if I can upgrade them (testing applications as we speak!), but I was able to browse from both OldDC and OldDC2 to shares on NewDC1 and to NewDC2, whereas previously I could not, and previously browsing to those shares generated the same error that popped up when attempting to finish dcpromo, so I am guessing they had the same root cause.