tronh
asked on
can you run metadata cleanup with server being a member server
had to force domain controller out - now having file replication errors - want to run meatadata cleanup but server is currently a member server on the domain
Run it from your other domain controller.
You run the metadata cleanup on a working DC but you delete all lingering data on the old dc that is still existing in AD. Make sure you delete any SRV records in DNS to for the failed DC.
http://www.petri.co.il/delete_failed_dcs_from_ad.htm
http://www.petri.co.il/delete_failed_dcs_from_ad.htm
That's sort of correct.
NTDSUTIL is run on the DC that is still functional. It doesn't remove any data ON the old DC at all, since it's failed. You can't read or write from it. Luckily, you don't have to. All you have to do is remove the information ABOUT the old DC from AD. Basically you are making it so the functional DC doesn't know the other one existed.
After you do this, do NOT attempt to fix that other DC or turn it back on. It's gone. Kaput. Finito. Permanently.
That petri link is a good guide to follow to accomplish this.
HTH,
exx
NTDSUTIL is run on the DC that is still functional. It doesn't remove any data ON the old DC at all, since it's failed. You can't read or write from it. Luckily, you don't have to. All you have to do is remove the information ABOUT the old DC from AD. Basically you are making it so the functional DC doesn't know the other one existed.
After you do this, do NOT attempt to fix that other DC or turn it back on. It's gone. Kaput. Finito. Permanently.
That petri link is a good guide to follow to accomplish this.
HTH,
exx
ASKER
what about the failed dc's name? i have already joined a new member server (completely different server) with the failed dc's name.
That is fine if you do the metadata cleanup then delete any SRV records and the A record. Then do a ipconfig /registerdns. You shouldn't have any problems but next time make sure you do a metadata cleanup on a failed DC. Also, when you reuse the name of a computer make sure to delete any objects with this name for the old computer before naming a new computer with the same name.
Wait a minute.. You joined a new server using the old DCs name without first doing a metadata cleanup? That should not even have been possible..
You're leaving out some piece of data here, something else you did already..
You're leaving out some piece of data here, something else you did already..
ASKER
no, nothing else. There is now a member server on the domain with the exact name of the forced out domain controller. The only issue that i am currently trying to fix is the file replicaiton between my 2 remaining dc's. Which i suspect could be corrected with metadata cleanup.
Can you run a netdiag then post results.
ASKER
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\dhcadmin>netdiag
.......................... ..........
Computer Name: NASHTNFS
DNS Host Name: NASHTNFS.nashshe.sheraton- nashville. com
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 15 Model 6 Stepping 5, GenuineIntel
List of installed hotfixes :
KB921503
KB924667-v2
KB925398_WMP64
KB925902
KB926122
KB927891
KB929123
KB930178
KB931784
KB931836
KB932168
KB933360
KB933566
KB933729
KB933854
KB935839
KB935840
KB936021
KB936357
KB936594
KB936641
KB936782
KB938127
KB939315
KB939653
KB941202
KB941672
KB943460
Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
Adapter : Local Area Connection 2
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : NASHTNFS
IP Address . . . . . . . . : 192.168.25.5
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.25.2
Dns Servers. . . . . . . . : 192.168.25.5
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{DA25164D-DCFA -4EB7-82EB -8D9C2F167 4D6}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '192.168.25.5
' and other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{DA25164D-DCFA -4EB7-82EB -8D9C2F167 4D6}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{DA25164D-DCFA -4EB7-82EB -8D9C2F167 4D6}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
C:\Documents and Settings\dhcadmin>
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\dhcadmin>netdiag
..........................
Computer Name: NASHTNFS
DNS Host Name: NASHTNFS.nashshe.sheraton-
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 15 Model 6 Stepping 5, GenuineIntel
List of installed hotfixes :
KB921503
KB924667-v2
KB925398_WMP64
KB925902
KB926122
KB927891
KB929123
KB930178
KB931784
KB931836
KB932168
KB933360
KB933566
KB933729
KB933854
KB935839
KB935840
KB936021
KB936357
KB936594
KB936641
KB936782
KB938127
KB939315
KB939653
KB941202
KB941672
KB943460
Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
Adapter : Local Area Connection 2
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : NASHTNFS
IP Address . . . . . . . . : 192.168.25.5
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.25.2
Dns Servers. . . . . . . . : 192.168.25.5
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{DA25164D-DCFA
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '192.168.25.5
' and other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{DA25164D-DCFA
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{DA25164D-DCFA
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
C:\Documents and Settings\dhcadmin>
Everything looks in order. What are the errors you are getting? If you named the DC the same name as the demoted DC you might need to demote the one with the same name. Do a metadata cleanup and clean DNS of all entries with this name then re-promote.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.