Renamed a DC now can't login.

Question

Renamed a DC now can't login.

LukeDin 11

I was adding a new 2022 DC to our domain. Everything went fine but after it was added I noticed the name had a spelling mistake so I used the GUI to change this new DC's name and reset the DC(I now know I should have used netdom). Now I can't login to this new DC because I get the error "The security database on the sever does not have a computer account for this workstation trust relationship".

I get the issue and I would normally fix this by simply removing it from the domain and readding it. However I can't do that because I can't login to any account on this DC anymore. I still have access to other DC's (their running Windows 2012) so I can edit the AD but manually adding the server new name doesn't work.

Is there some way I can still fix this or do I have to fully reinstall the new DC?

Jonathan Mazzetta 70 Reputation points

2023-03-02T00:14:17.28+00:00

Ran into the exact same problem. here's the fix

Reboot and hold f8 to enter boot menu
select 'safe mode with networking'

Login with administrator account

open the Registry Editor
In the left pane navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SchedulingAgent
In the right pane, double click OldName

The Value Data should be the old name of your PC . . .

Control panel -> system -> rename this pc
Enter the old name and restart

Boom!
NarrendranMaleyappan-0057 0 Reputation points

2023-09-08T09:07:23.7766667+00:00

@Jonathan Mazzetta
Hey there,
Your solution is working & truly appreciate for the steps and work through for this. Appreciate it a lot! Thank you & happy weekends!

Regards,

Narrendran
Adam Adel 0 Reputation points

2024-01-22T20:41:29.8533333+00:00

When i try to do this, i get "Microsoft server operating system setup". And i am afraid that this will remove everything from the domain controller. This is an university project and i have come far, i can't risk it
Suhaib Manzoor Hashmi 0 Reputation points

2024-04-02T14:01:48.52+00:00

@Jonathan Mazzetta Thanks a lot, I faced this problem in hyper-v vm, now it has been fixed after doing your mentioned steps.
Sergi Riofrio 0 Reputation points

2026-09-01T12:48:26.42+00:00

@Jonathan Mazzetta Thank you so much, I already was facing the idea of remaking my server. This workss

5 answers

Your answer

Jonathan Mazzetta 70 Reputation points

2023-03-02T00:14:17.28+00:00

Ran into the exact same problem. here's the fix

Reboot and hold f8 to enter boot menu
select 'safe mode with networking'

Login with administrator account

open the Registry Editor
In the left pane navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SchedulingAgent
In the right pane, double click OldName

The Value Data should be the old name of your PC . . .

Control panel -> system -> rename this pc
Enter the old name and restart

Boom!
NarrendranMaleyappan-0057 0 Reputation points

2023-09-08T09:07:23.7766667+00:00

@Jonathan Mazzetta
Hey there,
Your solution is working & truly appreciate for the steps and work through for this. Appreciate it a lot! Thank you & happy weekends!

Regards,

Narrendran
Adam Adel 0 Reputation points

2024-01-22T20:41:29.8533333+00:00

When i try to do this, i get "Microsoft server operating system setup". And i am afraid that this will remove everything from the domain controller. This is an university project and i have come far, i can't risk it
Suhaib Manzoor Hashmi 0 Reputation points

2024-04-02T14:01:48.52+00:00

@Jonathan Mazzetta Thanks a lot, I faced this problem in hyper-v vm, now it has been fixed after doing your mentioned steps.
Sergi Riofrio 0 Reputation points

2026-09-01T12:48:26.42+00:00

@Jonathan Mazzetta Thank you so much, I already was facing the idea of remaking my server. This workss

Answer 1

Kent Leong 0

Thank you so much, Problem solved.

0 comments

Answer 2

Jason Horstman 0

Thank you so much, you saved me so many hours of work!

0 comments

Answer 3

Denis Wahome 0

@Jonathan Mazzetta The solution works, modify with unplugging the network cable after you login in Safe Mode with Networking.

Thanks!

0 comments

Answer 4

Xavier Suárez 0

Jonathan Mazzetta i just made this same error, renaming the server with the oldname will solve the sign in issue??

can you please help me telling how do i change a windows server domain controller hostname?

Wallo67 0 Reputation points

2024-03-13T20:54:28.7166667+00:00

Here are my two cents, hope it helps someone in the future - I also made the same mistake of renaming a DC using the wrong method trying to keep things seamless in the network - almost 40 working hrs later after reading every forum and trying every solution I was able to regain access to the new-to-be DC by doing the following:

I was lucky that still had my old DC online and able to login to it and there in AD I could see my new DC but showing the wrong new name. I kept trying to connect via RD but had no luck - my task was to rename back to the 'old name' and by using regedit I was able to connect to the faulty DC by using the IP address - then I changed the name back to what DNS was seeing and after rebooting the machine - AND A LOT OF PRAYING - my DC came back up and I was able to login again with the network credentials.

Below are the places in the registry that I had to change the name back:

http://www.jsiinc.com/SUBH/tip3900/rh3982.htm

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveCompu

terName\ComputerName is the current NetBIOS computer name.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerNam

e\ComputerName is the NetBIOS computer name that will be used when the

computer is restarted.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Hostna

me is the host name of the computer.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\NV

Hostname is the host name that the computer will take when it is restarted.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Domain

is the current DNS domain name. Domain may be empty or not present. The full

computer name is the values of Hostname + Domain.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\NV

Domain is the DNS domain name that the computer will use when it is

restarted. The full computer name after a restart is the values of NV

Hostname + NV Domain.

Answer 5

Anonymous

Simplest solution may be to remove from network, seize roles (if necessary)
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/transfer-or-seize-fsmo-roles-in-ad-ds

do cleanup to remove remnants
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564

and stand up a new one for replacement.

The two prerequisites to introducing the first 2019 or 2022 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new one, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health.

--please don't forget to upvote and Accept as answer if the reply is helpful--

LukeDin 11 Reputation points

2021-12-18T20:18:17.777+00:00

I appreciate the reply however this doesn't really address my issue. I'm not asking how to add a 2022 DC. I already did that without issue. The problem is the names changed and I now have no access to the 2022 DC that I did add.

Or are you just saying, it can't be fixed and I have to wipe the 2022 DC and reinstall from scratch?
Anonymous

2021-12-18T20:21:33.537+00:00

Renaming a domain controller is generally not recommended. Given the issue; standing up a new one for replacement is the simplest / cleanest solution. This can be done in about 30 mins so its not worth troubling over.

--please don't forget to upvote and Accept as answer if the reply is helpful--
LukeDin 11 Reputation points

2021-12-18T20:46:49.553+00:00

If I have to I can do that but it's a lot more than 30 minutes. It's 30 minutes just to do the format and base install. With everything I had setup on it, it's a full days work to redo it. Is there really no way to manually add the new name to the AD?
Anonymous

2021-12-18T20:50:09.91+00:00

Is there really no way to manually add the new name to the AD?

I don't know what this means. I don't know why it would take a day to build a new one. To the first issue you can try via PowerShell to put it back to original name. Beyond this there's not a lot else to do with it.
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/rename-computer?view=powershell-7.2#example-2--rename-a-remote-computer

--please don't forget to upvote and Accept as answer if the reply is helpful--
Anonymous

2021-12-19T13:24:10.69+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--
LukeDin 11 Reputation points

2021-12-19T16:16:39.137+00:00

No, I'm still looking for a solution. If I have to do a full rebuild that will be my Monday.
Anonymous

2021-12-19T16:20:57.503+00:00

Sounds good then,

--please don't forget to upvote and Accept as answer if the reply is helpful--
Anonymous

2021-12-20T12:54:01.343+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--
LukeDin 11 Reputation points

2021-12-21T00:28:17.917+00:00

I wiped the whole thing and am starting over from scratch. Never found a solution beyond just starting over from scratch and losing everything.
Anonymous

2021-12-21T00:37:00.69+00:00

Glad to hear its sorted. Not sure what is meant? New domain? This wasn't necessary. When a domain controller fails the simplest solution is to seize roles (if necessary) to another healthy one
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/transfer-or-seize-fsmo-roles-in-ad-ds

then cleanup to remove remnants of failed one.
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564

then stand up a replacement.

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019 or 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

--please don't forget to upvote and Accept as answer if the reply is helpful--
Anonymous

2021-12-23T14:43:47.313+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--
SW85 6 Reputation points

2022-11-07T22:54:11+00:00

Not that it helps, but maybe this will help someone in the future. I managed to fix my mistake of renaming my DC. I booted into my Windows Server 2022 ISO and selected repair. I went through the steps and selected the option to open the command prompt.

At the command prompt I opened regedit.exe. Selected the HKLM, then went up to File and load hive. I browsed to c:\windows\system32\config\System. Opened that and gave it a name. I selected that hive and went up to edit. Selected FIND, in find I put the new Name for the server. I went through and did Find Next for each entry and replaced them with the previous Computer Name. Once I finished finding all references to the broken name, I unloaded the hive and then reboot the server. I was able to log into the Domain Controller, I have yet to check for any errors, but at least I am now able to log in and access the system. I can fix any errors from there. Even if that means firing up a new DC.
Anonymous

2022-11-07T22:56:41.213+00:00

That's what I would suggest, standing up a new one for replacement. Please don't forget to close up the thread by
Anonymous

2022-11-10T10:28:52.087+00:00

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--
Anonymous

2023-04-25T19:59:37.1866667+00:00

Just ran into this issue after changing the PC name on my all-in-one domain WS2019 controller+client VM and resolved it with a combination of Jonathan Mazzetta's and SW85's answers. Jon's let me get back into the system with the Administrator account I had previous (which I could not log into without safe mode), but it did not allow me to change the computer name because of the "invalid name" or whatever message. The error message is super ambiguous because it doesn't say why the name you enter is invalid. At this point, I could go into the registry and make the about 3 changes needed to revert the computer name.