GardIT
asked on
Removal of Dead DC from Active Directory
Hi,
We have had a domain controller / hub transport server die due to hardware failure. We have tried to remove this DC for AD by the use of NTDSUTIL and it just stays there when I try and delete from Active Directory Sites and Services I get an error message "Windows cannot delete object "Full Server Name / Path" because: the DSA object could not be found.
The old DC is not causing us any problems at present just gives errors when you use Exchange console or AD errors in the logs.
Any help would be gratefully appreciated.
We have had a domain controller / hub transport server die due to hardware failure. We have tried to remove this DC for AD by the use of NTDSUTIL and it just stays there when I try and delete from Active Directory Sites and Services I get an error message "Windows cannot delete object "Full Server Name / Path" because: the DSA object could not be found.
The old DC is not causing us any problems at present just gives errors when you use Exchange console or AD errors in the logs.
Any help would be gratefully appreciated.
Last Comment
In addition, go into Active Directory Sites and Services and delete old instances of the server. W2K8 does an automatic cleanup of the environment after you do this.
Force replication through AD Sites and Services or run:
repadmin /syncall
Force replication through AD Sites and Services or run:
repadmin /syncall
ASKER
The dead server has no roles as all the roles have been moved to new servers.
When to delete from Site and Services is when I get the DSA object error.
Extra Information, we have successfully removed DC both prior and after the DC has died. I have a suspension that it could be something to so with the server been a Hub transport server as well as a DC,
When to delete from Site and Services is when I get the DSA object error.
Extra Information, we have successfully removed DC both prior and after the DC has died. I have a suspension that it could be something to so with the server been a Hub transport server as well as a DC,
I just want to verify that you are deleting the non-existent servers correctly.
AD Sites and Services -> Site -> expand Servers -> expand non-existent server -> delete NTDS Settings
Right?
Did you verify your DNS network adapter configuration across your current DCs?
AD Sites and Services -> Site -> expand Servers -> expand non-existent server -> delete NTDS Settings
Right?
Did you verify your DNS network adapter configuration across your current DCs?
ASKER
Metadata clean-up dose not work, when I list servers get the following
select operation target: list servers in site
Found 1 server(s)
0 - (null)
Yes that's how i'm deleting the non-existent server, all the DNS adapters are working and we are not having any DNS issues.
select operation target: list servers in site
Found 1 server(s)
0 - (null)
Yes that's how i'm deleting the non-existent server, all the DNS adapters are working and we are not having any DNS issues.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Found solution else where
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
netdom query fsmo
Then start seizing with the following:
ntdsutil
roles
connection
connect to server <seizing_dc_name>
quit
seize infrastructure master
seize naming master
seize PDC
seize RID master
seize schema master
quit
quit
Verify your results with:
netdom query fsmo