Renamed DC - AD broken

Hoping that someone might be able to help me sort out this problem.

I've just been trying to complete a server migration from Server 2003 named CURR-SERVER. I've done the following steps:

  1. Setup a new Windows 2012 R2 server named it CURR-SERVER2
  2. Joined the 2012 server to domain and promoted it to a DC
  3. Moved across DHCP, shares and data
  4. Demoted the old 2003 server, the FSMO roles get transferred to the new server
  5. Renamed the old server from CURR-SERVER to CURR-SERVER-OLD
  6. Renamed the new server from CURR-SERVER2 to CURR-SERVER

This was the point where it all went wrong. When I attempted to rename the new server to CURR-SERVER I got an error back saying CURR-SERVER already exists. After rebooting the server it had renamed itself but I am now unable to use any of the AD administrative tools. I get the error "Naming information cannot be located because: The interface is unknown".

Clients cannot logon. I cannot rename the server back to CURR-SERVER2 to try and recover, I get the error that the domain doesn't exist.

Is there any way of recovering from this without having to restore from backup and start again?

Any way of avoiding this in the future? Anything I need to check before renaming a DC?

July 23rd, 2015 8:42am

Hi Simon,

Please perform the below steps on your DC.

1) Restart "netlogon" service.

2) run "nltest /dsregdns"

3) run dcdiag /fix

4) Reboot the server.

Not sure if you have another DC. If you have another dc, try to seize the FSMO role on this Windows 2012 R2 server.

-Umesh.S.K

Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2015 9:17am

As a best practice You have to use Netdom to rename domain controller. Please find below the link.

https://technet.microsoft.com/en-us/library/cc782761%28v=ws.10%29.aspx

As for the current issue which you are facing, can you try IPCONFIG /REGISTERDNS. I see that the AD tool is unable to locate any DC from the DNS. Restart the DNS if required. Please also confirm whether you are able to open the DNS console.

  • Marked as answer by simon-gcc 17 hours 7 minutes ago
July 23rd, 2015 9:32am

Successfully completed the rename using Netdom. Very happy as it has saved me 2-3 days work starting over. Thanks.
Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2015 10:24am

Hi Simon,

Glad that you solve the problem. After renaming successfully, you could also check whether the DNS works well. Ensure the DC point to it self (If its also running DNS and hosting a AD-integrated zone for your Active Directory domain other wise point it to the DNS server hosting the zone).

Best Regards,

Mary Dong

July 23rd, 2015 10:38pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics