Netdom computername /ENUMerate # (where the parameter is the temporary host name of DC2016): First perform a preflight check with the following command:.On DC4, run the NETDOM command to rename:.In this case you install DC3 and DC4 and promote them to domain controllers 2016 so you will have 4 DCs (2 OLD and 2 NEW): Second method: used when you have or think to have applications hardcoded with DC name and want to preserve OLD names and IPs. Install the Domain Services role and promote it to DC.įor those that are preserving with the rename process here you go:.Removing AD and Domain Services Role from DC2.The first method is the recommended one, always follow this process, as it is much easier:įirst method (recommended): Proceed with removing the domain controller role from DC1 and then DC2 (demote) before inserting DC3 and DC4. There are two methods to achieve the same result. My test environment has the following DCs: The first two attributes should be empty when rename is finished, and there should only exist SPNs for the new names.Īlso you may want to check SRV records in DNS under _' and '_tcp.dc._', they should match new name (old name shouldn't be there anymore) Unfortunately, there are still environments that face this ask so I thought I would write a short how-to just to help to wants to insist this way or maybe mess around in a lab.īefore going through the steps be aware that you may have an issue with DFSR SYSVOL objects after the rename which the following article details:Īlso after performing the procedure, the corresponding computer object contains left-over data with old and new samAccountName : This should be avoided, application owners should be advised about the impact of this misconfiguration and guided on who to properly configure them. One of the needs that arise during an Active Directory upgrade is to have to rename the new Domain Controllers with the Name and IP of the old ones.

Netdom windows 10