At my company we replaced the sole domain controller (Server 2003) with a new domain controller using Server 2008 R2. The old server has a failed RAID and shortly after transferring the domain controller roles to the new server it finally died.
The new domain controller was working beautifully right up until I was told to rename it to reflect the old server name. The machine is a fileserver also, so it was thought that this would cut down on time to change all of the workstation shares.
Instead, by following the instructions here: http://technet.microsoft.com/en-us/library/cc794951%28v=ws.10%29.aspx
I've managed to create a hideous mess.
After renaming the system from (let's call it "WIN-LB5RBOTH3CB") to "cwrpdx" I no longer have access from any workstation. I can log in as myself and the administrator directly from the server. But I cannot access any AD services - not Users and Computers, etc.
Looking through ADSIEDT.MSC, I can log into the name "cwrpdx" and see all kinds of information. Nearly everything shows the new servername, but the entry for OU=Domain Controller points to the wrong server name, WIN-LB5RBOTH3CB. I cannot change it due to a permissions error. If I try to change the permissions, the computer sits eternally and never brings up the security dialog.
So now I'm totally screwed. This is the sole domain controller, and the old controller is dead. So I cannot just use a secondary domain controller to try to set things right.
What can I do?
Here's the output of dcdiag:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = cwrpdx
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site\WIN-LB5RBOTH3CB
Starting test: Connectivity
The host
64019081-b859-458a-9eac-b98bb93d7fe8._msdcs.cascadewestern.local could
not be resolved to an IP address. Check the DNS server, DHCP, server
name, etc.
Neither the the server name (WIN-LB5RBOTH3CB.cascadewestern.local) nor
the Guid DNS name
(64019081-b859-458a-9eac-b98bb93d7fe8._msdcs.cascadewestern.local)
could be resolved by DNS. Check that the server is up and is
registered correctly with the DNS server.
Got error while checking LDAP and RPC connectivity. Please check your
firewall settings.
......................... WIN-LB5RBOTH3CB failed test Connectivity
Doing primary tests
Testing server: Default-First-Site\WIN-LB5RBOTH3CB
Skipping all tests, because server WIN-LB5RBOTH3CB is not responding to
directory service requests.
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : cascadewestern
Starting test: CheckSDRefDom
......................... cascadewestern passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... cascadewestern passed test
CrossRefValidation
Running enterprise tests on : cascadewestern.local
Starting test: LocatorCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1722
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1722
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1722
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
1722
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1722
A KDC could not be located - All the KDCs are down.
......................... cascadewestern.local failed test
LocatorCheck
Starting test: Intersite
......................... cascadewestern.local passed test Intersite