Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Renamed DC - AD broken

$
0
0

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?


Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>