2008r2 to 2008r2 domain controller migration: renaming

rG-tom

rG-tom

rG-tom

Soldato
Joined
27 Nov 2004
Posts
10,327
Location
North Beds
Hey,

Folowing this guide i'm up to stage 7:

http://technet.microsoft.com/en-us/library/dd379526(WS.10).aspx

i have renamed the source server and changed its ip, put the destination server onto the correct IP and that has all worked fine. DNS replication and AD replication is all working perfectly.

When i try and rename the destination server using netdom renamecomputer %computername% /newname: <old_name_of_source_server> i get the error:

Code: 
The account already exists.

The command failed to complete successfully.

Any ideas? there is no sign of the old servers name anywhere anymore in AD, the new name is everywhere etc.

please help it's driving me mad!

Thanks,

Tom.
 
I'm no AD expert so this may be of no use but I'll give it a go!

When you say no sign of the old server name, I take it there are no computer objects in AD with the name which you are trying to use now that the old server has been renamed? Check the computer object for the source server has been renamed on all DCs in case it hasn't replicated properly? Are you able to rename it with any other name?
 
Maybe you'll have to do some searching for it in adsiedit if the name of the old domain controller is still around. Although, I'm a little unsure as to what you want to do.
 
nightshadow, i can rename it to any other name, except the one i just changed the old DC from.

Tingle: i want to remove the old DC, and the microsoft guide which I posted in the OP says to rename the new server to the name that the old server had as the final step, which it wont let me do.
 
Hmm, so it does sound like there might be an entry in AD somewhere pointing to the old DC name or maybe the server you are trying to rename still thinks it is connected to the old DC? How many DCs do you currently have online? Have you made sure that the old DC name is not present on each DC from ADUC? run "Set logonserver" from cmd on the PC you are trying to rename and see what DC it is using, from there you can see which DC might still have the old DC's computer object.
 
If you just run DCPROMO on the old domain controller, it should just downgrade it from a domain controller. Then you could rename that DC to OldDC, then rename the new server to the original name of OldDC.
 
in the end i just turned the old DC off, flattened new DC and fresh installed. It was only a home environment with 2 users, so moving the profiles wasnt that much bother

I think it was exchange causing the problems on the original DC, as the exchange server was still referencing itself as the old name.
 
You must log in or register to reply here.
Back
Top Bottom