<div>
If source and target data center will not communicate each other, then post your data center migration, remove those dc from ad directly, the process is known as metadata cleanup<br />
<br />
Basically from domain controllers ou, remove / delete dc, accept any prompted checkboxes when asked and remove it, force ad replication <br />
Then remove dc object from ad sites and services and remove dc records from ad sites and services
</div>


<div>
Mahesh,<br />
<br />
Do you have a link you suggest following ?
</div>


<div>
Check below links<br />
<br />
<a href="https://blogs.technet.microsoft.com/canitpro/2016/02/17/step-by-step-removing-a-domain-controller-server-manually/" rel="ugc">https://blogs.technet.microsoft.com/canitpro/2016/02/17/step-by-step-removing-a-domain-controller-server-manually/</a><br />
<br />
OR<br />
<br />
<a href="http://www.msserverpro.com/metadata-cleanup-using-ntdsutil-in-windows-server-2008-r2/" rel="ugc">http://www.msserverpro.com/metadata-cleanup-using-ntdsutil-in-windows-server-2008-r2/</a><br />
<br />
Both methods will work
</div>


<div>
We'll update this post this weekend when we make the changes
</div>


<div>
The above makes no reference to modifying static and DHCP configuration on clients that use these two servers as DNS.<br />
<br />
Also, what else runs on these two DCs?
</div>


<div>
I have done this numerous times and I have always done it using metadata cleanup. &nbsp;Below is another link. &nbsp;If you are not familiar with ntdsutil then I suggest stick with MS ways of doing cleanup using AD Users and Computers.<br />
<br />
<a href="https://www.itprotoday.com/data-security-and-encryption/quantum-computing-doesn-t-threaten-good-encryption-yet" rel="ugc">https://www.itprotoday.com/data-security-and-encryption/quantum-computing-doesn-t-threaten-good-encryption-yet</a>
</div>


<div>
That process is already posted above. As mentioned, this does not take in account the endpoint configuration, additional roles on DCs or the overall health of the environment
</div>


<div>
Yes, Issue might come if both DCs are listed in DHCP scopes etc or static entries on servers / clients, good catch Shaun !<br />
<br />
post data center migration and during metadata clean-up those DC entries should be removed from all places it may exists such as DHCP scopes, static dns entries, access points and so on.
</div>


<div>
The static DNS entries on the NIC will be changed to only reference the DC's that will be staying and the firewall was the DHCP server. In our steps we have noted to remove the old DNS server reference. &nbsp;I'll update everyone asap
</div>


<div>
We just noticed that in sites and services there are two sites. &nbsp;One site has the local subnet of where one of the DC's we are removing is located. &nbsp;Shouldn't we post migration remove that subnet and add it to the sites and services where the DC we are keeping will be? &nbsp;That way clients in that subnet use the DC we are keeping, correct?<br />
<br />
Also,<br />
<br />
The firewall handles DHCP and DNS points to the DC we are keeping.
</div>


<div>
The subnets where the old dc is located will remain their with old site<br />
<br />
Are you using same old subnets at new data center?<br />
If yes, you need to change those subnets site assignments to reflect to new data center AD site<br />
Else simply delete those subnets from AD sites and services
</div>


<div>
Users and / or the LAN/subnet will stay but the DC in the LAN/subnet will be gone. &nbsp;That DC is one we'll be removing manually. &nbsp;The loosing provider won't make changes prior to migration.. &nbsp;so... &nbsp;I assume after the migration we remove the subnet from the old site and add to the site we'll be keeping where the DC we'll be keeping is. &nbsp;Correct? &nbsp;That was the local LAN's subnet will match the site listed that has the DC we are keeping
</div>


<div>
<div class="content wysiwyg-content">
We are migrating an entire domain environment for to a new datacenter. &nbsp;Two of the old DC's will be staying and not moving. &nbsp;They do not hold any of the FSMO roles. &nbsp;How do we manually remove them? &nbsp; We can't do it before hand for the loosing data center won't let us and they manage the existing domain environment for two companies reside in it.
</div>
</div>


We are migrating an entire domain environment for to a new datacenter.  Two of the old DC's will be staying and not moving.  They do not hold any of the FSMO roles.  How do we manually remove them?   We can't do it before hand for the loosing data center won't let us and they manage the existing domain environment for two companies reside in it.

manually removing two DC's that don't have any FSMO roles

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

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