Solved

Errors After Renaming Domain Controller to Old Domain Controller Name

Posted on 2012-04-13
17
1,506 Views
Last Modified: 2012-04-25
I am replacing an old 2003 DC with new hardware with 2008R2 DC, and keeping the old name for file share, file redirection purposes. I have successfully joined the 2008DC to the domain, let it replicate, and demoted the 2003DC.

I renamed the old DC to 2003DCOLD and changed IP.

I renamed the new 2008 DC to 2008DC changed IP to that of the old one.

I restarted both servers.

Now, I see that Active Directory SItes and Services shows both instances of the 2008 DC, both as the temporary name, and the old name.  And it's trying to replicate from the temporary name, which no longer exists and is now the new name.

Do I delete the temporary name from sites and services?

I'm also getting errors in the event log:

such as in the FIle Server Log - Error DFSR - The DFS Namespace service could not initialize the trusted domain information on this domain controller, but it will periodically retry the operation. The return code is in the record data.

And System - GroupPolicy - 1055 - The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
0
Comment
Question by:fireguy1125
  • 9
  • 7
17 Comments
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 37843444
How did you rename the DC?

Did you go through this process? http://www.petri.co.il/rename-windows-server-2008-domain-controllers.htm
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 37843460
No I did it through system properties and changed name and rebooted - guess that was the wrong way - what are my next steps to get this resolved?
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 37843479
Also, when I ping domain.net from the new domain controller, it has the domain.net associated with the old temporary IP address.  How do I change it so it associates domain.net with the current ip address?
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 37843516
Do you have a back so, you can restore?
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 37843543
I already demoted the old domain controller that has the same name.

Should I rename this domain controller to a different new name using the instructions your provided, let the replication finish. Then rename it back to the old name with your instructions?

I believe the step I missed, was deleting the 2003DC from Active Directory after demoting it and changing the name, then when I went to rename the 2008DC to the old 2003DC name, it caused a conflict. For when I look at the name properties in Active Directory of the name, it shows it is a 2003 server, when it actually should show a 2008.
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 37843558
You can try going through the steps in the link.

Did you demote the 2003 server properly?
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 37843593
Yes, the old 2003 server was successfully demoted.
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 37843607
Alright so, at this point you renamed the DC with the wrong steps you can try to go through the steps in the link I posted to fix the problem.
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 37843625
When I run the command it says:

Unable to add 2008DC.domain.net
as an alternate name for the computer.
The error is:

The network path was not found.

The command failed to complete successfully.
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 37843635
Right since you have already renamed the DC. Now try renaming back the same way you did it to the name it was. Try going through the steps to rename the proper way.

I have to tell you this renaming a DC without going through the proper steps can kill a DC. Do you have others online or a back by chance?
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 37843657
At this point, should I dcpromo out the new 2008DC, removing from domain, deleting entries to OLDNAME in the domain, renaming then DCPROMO back into the domain with the new name? i would have to replicate from another site, but that should be OK, it's a solid connection.
0
 
LVL 59

Accepted Solution

by:
Darius Ghassem earned 500 total points
ID: 37843662
I would remove this DC from AD.

Run metadata cleanup to  make sure no lingering objects are left behind.

Delete all DNS records.

You can then promote the DC again with the proper name. If you are going to demote go a head rename the server when it is not a DC you can then promote and you will be done
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 37843676
i'm still getting those errors even when I try changing back to the old name, yes I have other DCs.
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 37843685
Ok. Can you advise how the correct way to run metadata cleanup to ensure nothing is left behind from any of the names I have used.
0
 
LVL 59

Assisted Solution

by:Darius Ghassem
Darius Ghassem earned 500 total points
ID: 37843696
Go through this link.

http://www.petri.co.il/delete_failed_dcs_from_ad.htm

Remove any objects left before for both server names
0
 
LVL 1

Author Closing Comment

by:fireguy1125
ID: 37858896
Thank you, seems to be OK now!
0
 

Expert Comment

by:pcturnkey
ID: 37892621
I've done the same thing, but I changed the name on the old server and the new server.  I've already transferred operations to the new one (that is now getting all the errors because I didn't change the name following the correct procedures).  I think I need to transfer operations back to the old computer, demote the new one, change the name, then promote it.  Is that right?
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question