<div>
As long as you have no intention of bringing DC1 back online as a domain controller, then you are good to go with seizure but since DC1 is a failed domain controller, you must make sure that you have properly cleaned it out of active directory once you have seized the role onto another domain controller.<br />
<br />
Good reference articles:<br />
<a href="https://support.microsoft.com/en-ca/help/216498/how-to-remove-data-in-active-directory-after-an-unsuccessful-domain-co" rel="ugc">https://support.microsoft.com/en-ca/help/216498/how-to-remove-data-in-active-directory-after-an-unsuccessful-domain-co</a><br />
<a href="https://www.petri.com/delete_failed_dcs_from_ad" rel="ugc">https://www.petri.com/delete_failed_dcs_from_ad</a>
</div>


challBOE

<div>
No, you should be able to seize the schema master and move on. In fact, restoring the previous schema master after seizing the role would be a bad idea.
</div>


<div>
Don't restore DC1 now, you already seized other FSMO roles which DC1 holds previously<br />
<br />
seize schema master role as well<br />
<br />
Seize process is there because you cannot bring original FSMO master back online, I don't know where you got document to restore original DC back before seize schema master, that is wrong docuemntation
</div>


<div>
Mahesh,<br />
Here is where I got the original documentation.<br />
<a href="https://www.petri.com/seizing_fsmo_roles" rel="ugc">https://www.petri.com/seizing_fsmo_roles</a><br />
<br />
&quot;The following table summarizes the FSMO seizing restrictions:<br />
FSMO Role &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Restrictions<br />
Schema &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**Original must be reinstalled** &nbsp;&lt;------------<br />
Domain Naming<br />
RID<br />
PDC Emulator &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Can transfer back to original&quot;<br />
<br />
It is that comment &quot;original must be reinstalled&quot; that concerned me.
</div>


Principal Support Engineer

DrDave242

<div>
Thanks everyone, Petri was the document I had originally wanted to use and Mahesh helped me interpret the one line that was holding me back. I did have to go into DNS and remove all references to the failed DC, even after metadata cleanup. And probably most helpful, wait for all the changes to migrate to all DCs before trying to seize the roles.<br />
Thank you all for your help.
</div>


<div>
<div class="content wysiwyg-content">
Seize schema master role repercussions in an 11 DC environment which is at Forest level functionality = 2003, domain level functionality= 2008 r2, and all Domain controllers on server OS=2012.<br />
DC1, with all fsmo roles, failed. <br />
Dc2 was able to grab all roles except Schema Master, in the ADUC Users/Computers mmc it shows &quot;error&quot; under current Schema Master.<br />
In command line (netdom /query fsmo it shows <br />
&quot;Warning: role owner is a deleted DC&quot;.<br />
<br />
&nbsp;I was ready to use NTdsutil to seize the schema Master role, but reading up on it, it says the failed DC (DC1) would have to be restored in order for Schema Master to work (allow DCpromo to work) again . &nbsp;I have no intention of restoring the failed DC1.<br />
<br />
I have Exchange servers, I will probably need to DCPromo again.<br />
<br />
Is this true that the original failed DC1 must be restored, or can I grab the Schema role successfully and have full functionality in my domain with out having to restore the failed server &nbsp;DC1?
</div>
</div>


Seize schema master role repercussions in an 11 DC environment which is at Forest level functionality = 2003, domain level functionality= 2008 r2, and all Domain controllers on server OS=2012.
DC1, with all fsmo roles, failed. 
Dc2 was able to grab all roles except Schema Master, in the ADUC Users/Computers mmc it shows "error" under current Schema Master.
In command line (netdom /query fsmo it shows 
"Warning: role owner is a deleted DC".

 I was ready to use NTdsutil to seize the schema Master role, but reading up on it, it says the failed DC (DC1) would have to be restored in order for Schema Master to work (allow DCpromo to work) again .  I have no intention of restoring the failed DC1.

I have Exchange servers, I will probably need to DCPromo again.

Is this true that the original failed DC1 must be restored, or can I grab the Schema role successfully and have full functionality in my domain with out having to restore the failed server  DC1?

If I Seize Schema Master am I required to restore failed Domain Controller?

fsmo

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.

Exchange

A domain controller is a server that responds to security authentication requests within a computer network domain. It is a network server that is responsible for allowing host access to domain resources. It authenticates users, stores user account information and enforces security policy for a domain