• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 807
  • Last Modified:

Renamed 2008 DC - Now can't login to DC

We have to rename the DC in a small single DC network. Its a Windows 2008 R2 server that is up to date on updates.

Following the rename, we can't login to the server locally. When we try we get the error "The security database on the server does not have a computer account for this workstation"

I've seen this before on workstations but not sure how to deal with it on the only DC on the network as I can't login to do anything.

Thanks for any help
0
willp2
Asked:
willp2
  • 5
  • 3
2 Solutions
 
KCTSCommented:
It could just be that DNS has not updated yet - try logging on the the DC and running DCDIAG /fix
0
 
willp2Author Commented:
Thanks, but this is the DC and I can't login to it to do anything. Its acting like the name change didn't fully take. Wonder if there is anyway to roll back.
0
 
KCTSCommented:
OK in that case I can only think of two options

a) Try booting from the Server DVD and use WINRE  (Windows Recovery Environment) and use NETDOM from the commmand line to revert to the previous name - see http://technet.microsoft.com/en-us/library/cc835082(WS.10).aspx

b) Re-install
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

 
Darius GhassemCommented:
To rename a Domain Controller you need to follow these instructions.

http://www.petri.co.il/rename-windows-server-2008-domain-controllers.htm

I would get the DC back to the orginal name like KCTS said then reset secure channel password.

If you have other DCs I recommend you demote this DC then you can run metadata cleanup to remove any lingering objects
0
 
willp2Author Commented:
I have been trying to rename from the command prompt, but when I go into the recovery environment it tells me that the workstation service isn't running. Then of course it won't let me start the service in safe mode.

Wow, what a way to ruin a weekend. A 10 minute tweak is now going to be an all day event and likely lead to me having to remove all the PCs from the network, add them back and rebuild / migrate profiles.
0
 
KCTSCommented:
Renaming a DC is never without risk - back it up first - lesson learned :-(
0
 
willp2Author Commented:
Yes I agree. This was actually at the end up an upgrade from a Win2K domain to the 2008 system. Everything went well until now, but I dumbly demoted the Win2K just before this as I thought it was in the bag. Now I can't promote the Win2K machine back and the Win 2008 system is effectively dead.
0
 
willp2Author Commented:
OK, I had to punt and rebuild the DC. I hate stuff like this as much for the principal of the thing as it is for the extra work it creates.
0
 
willp2Author Commented:
Good advice but didnt actually fix the problem. Thanks for the help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now