<div>
Hi, <br />
<br />
When you say your DC is down, is it a hardware error or the ntds got corrupted? <br />
<br />
Since the other DC's doesn't have DNS role in it, I'm sure you might be facing issues with net, access etc.. <br />
<br />
The best course of action would be, <br />
<br />
1. Make the preferred DNS on the other DC as itself<br />
2. Install DNS role in it<br />
3. Sieze the fsmo roles to the other DC from the failed one <br />
4. Perform Metadata cleanup to remove all the entries belongs to failed dc<br />
<br />
Let us know if you need further help. <br />
<br />
Good luck
</div>


Hi,

When you say your DC is down, is it a hardware error or the ntds got corrupted?

Since the other DC's doesn't have DNS role in it, I'm sure you might be facing issues with net, access etc..

The best course of action would be,

1. Make the preferred DNS on the other DC as itself
2. Install DNS role in it
3. Sieze the fsmo roles to the other DC from the failed one
4. Perform Metadata cleanup to remove all the entries belongs to failed dc

Let us know if you need further help.

Good luck

<div>
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.<br />
<br />
I have recommended this question be closed as follows:<br />
<br />
Accept: Alexey Komarov (<a href="https:#a42075143" rel="ugc">https:#a42075143</a>)<br />
<br />
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.<br />
<br />
seth2740<br />
Experts-Exchange Cleanup Volunteer
</div>


No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: Alexey Komarov (https:#a42075143 [https:#a42075143])

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer

<div>
<div class="content wysiwyg-content">
Our domain controller is down for good. We have 2nd DC which act as backup. Active directory is there but no DNS and when i tried installing DNS, it gives me an error
</div>
</div>


Our domain controller is down for good. We have 2nd DC which act as backup. Active directory is there but no DNS and when i tried installing DNS, it gives me an error

How to reemove FSMO roles from dead DOmain controller

Act! (previously known as Sage ACT!) is a customer relationship management (CRM) software application which is used to keep track of client and prospect details in a single database that can be shared by multiple users. Act! features include contact, company and opportunity management, a calendar, communication tools, the ability to track prospective customers, "dashboards", reports, and the ability to synchronize data from other applications or other Act! users over the web.

fsmo

roles

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).