Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1607
  • Last Modified:

Problem after rename of a domain controller

I've decommissioned and domain controller (dc5) and then after a day renamed another domain controller to dc5.

Picking up problems on one of the root dc's where it keeps the serverreference attribute as the old dc's name. Thought this would be easy...

dcdiag throwing machine account errors. have already done a dcdiag /fixmachineaccount

* LIB-DC5-JHB Server Reference is incorrect! Should be CN=LIB-DC5-JHB1,OU=Domain Controllers,DC=something,DC=fin-za,DC=net, and is CN=LIB-DC5-JHB,OU=Domain Controllers,DC=something,DC=fin-za,DC=net.

ldap_search_sW failed with 2: The system cannot find the file specified.

......................... LIB-DC5-JHB failed test MachineAccount

When I go into adsiedit on the root dc and try and change the serverreference attribute it defaults back to the old name.
0
Nelesh_N
Asked:
Nelesh_N
  • 6
  • 3
  • 2
  • +1
1 Solution
 
Coast-ITCommented:
Its never as easy as that, although it should be...

here is a great article on achieving what you need ;

http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/72d5eda0-7185-4f97-a1cf-7952c12dc786
0
 
KCTSCommented:
Did you actually demote the old DC5 before it was removed?
If so then a simple DCDIAG /fix may solve the problem
0
 
Nelesh_NAuthor Commented:
Yes I did do a demotion to a member server. Will try.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Nelesh_NAuthor Commented:
nope doesnt work.
0
 
Nelesh_NAuthor Commented:
only one of the three root dc's that I have is picking up this problem.
0
 
Coast-ITCommented:
What if you change the name to something else?

Then possibly change it back?

Strange one this.
0
 
pmaribeiroCommented:
This server had FSMO roles and did you moved them?
0
 
Nelesh_NAuthor Commented:
Yes they were moved...
0
 
pmaribeiroCommented:
You need to go to AD sites and services, enter in the site where DC5 was and remove all entries about him.
Then do the same on the DNS and AD users and computers on the domain controllers container.

I would suggest to give a different name, because sometimes conflicts may ocur with some objects that may have be with the ID of the demoted DC.

So if you can try to change it.
0
 
Nelesh_NAuthor Commented:
So the problem is that there was a lib-dc5-jhb already in the environment, then a lib-dc5-jhb1 was introduced. The second machine is a hardware replacement for lib-dc5-jhb. I then did the dcpromo to remove lib-dc5-jhb - all went successfully. Then I renamed lib-dc5-jhb1 to lib-dc5-jhb. This is where the problem lies, I dont think AD likes the reuse of machine names. If I do a ntdsutil I dont see any refernce to lib-dc5-jhb1 but if I go to sites and services on another dc which happens to hold fsmo roles and is in the root. Go to sites and services, if I go to properties on lib-dc5-jhb I still see the server name as lib-dc5-jhb1. If I try to change the serverreference in adsiedit it defaults back to lib-dc5-jhb1. Why it must be pulling this info from somewhere, I also looked at DNS and cannot find any reference to lib-dc5-jhb1...
0
 
Nelesh_NAuthor Commented:
Ended up removing LIB-DC5-JHB... fixed my problem will reintroduce as another dc.
0
 
pmaribeiroCommented:
Its the best solution because even if you remove all entries as stated there the possibility the remainings of the old SID lying arround and will create enough problems with the same name. If seen this too often and normally the best solution is to rename to a new name. Because the time consuming to solve AD issues sometimes is extremely high.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 6
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now