Active Directory: Domain Name Rename – Multiple DC for Windows Server 2012

In this tutorial, the Active Directory Domain Name rename is expanded with Multiple DC and include a client. This tutorial will rename domain OldDomain.local to NewDomain.local

 

 

Step 1: Pre-Rename Check List

S1-1. Ensure All Active Directory Catalog are in-sync to all DCs.

a. To check replication status

RepAdmin.exe /ReplSummary

b. To start immediate replication manually

RepAdmin.exe /SyncAll <DC_HOSTNAME> /APed
Note: <DC_HOSTNAME> is the DC hostname.

Step 2: Rename ADDS Domain Name

S2-1. Open Command Prompt in Administrator Mode

S2-2. Execute RenDom /List to generate Forest Naming Context in XML file (Domainlist.xml)

Execute RenDom /ShowForest to view auto generated xml of current domain

ADDS_MD_0002

S2-3. Update the current domain name with new domain name and save the file

In this tutorial, Rename Domainlist.xml entry:
– DNS name OldDomain.local to NewDomain.local
– NetBios name OLDDOMAIN‘ to NEWDOMAIN

ADDS_MD_0003

ADDS_MD_0004

S2-4. Execute RenDom /ShowForest to view the new domain name in xml file

ADDS_MD_0005

S2- 5. Execute RenDom /Upload to the domain name changes from xml file

ADDS_MD_0006

S2-6. Execute RenDom /Prepare to start prepare domain name rename

If RenDom Prepare command fails as the following error:

ADDS_MD_0008

The solution is to sync AD Replication manually with the following command:
RepAdmin /SyncAll DC1 /APed
RepAdmin /SyncAll DC2 /APed

ADDS_MD_0009

S2-7. Execute RenDom /Execute to start domain name rename process.

ADDS_MD_0010

S2-8. Once RenDom completed execute rename domain command, All DCs server will be automatically restarted.

Note: Do not force restart.

S2-9. After the server reboots, take note to switch user to logon with new domain name

ADDS_MD_0011

 

Step 3: Fix Up Group Policy After Rename

S3-1. After rename process completed, GPMC will need to be fix up to use the new domain name.

You will encounter the following error:

ADDS_MD_0012

S3-2. Execute two commands to fix GPMC (DNS & NetBIOS Name):

GPFixUp /OldDNS:<OLD_DOMAIN_NAME> /NewDNS:<NEW_DOMAIN_NAME>
GPFixUp /OldNB:<OLD_NETBIOS_NAME> /NewNB:<NEW_NETBIOS_NAME>

 ADDS_MD_0013

 

Step 4: Rename Server Domain

S4-1. After Domain Name Rename completed, the server domain info still reflects  the old domain name

ADDS_MD_0014

S4-2.  All DCs computer name must be renamed with the following command:

NetDom COMPUTERNAME <OLD_FQDN> /Add:<NEW_FQDN>
NetDom COMPUTERNAME <OLD_FQDN> /MakePrimary:<NEW_FQDN>

ADDS_MD_0016

S4-3. Restart server

 

Step 5: Fix DNS for new Domain Name

S5-1. Open DNS Manager

ADDS_MD_0017

S5-2. Open File Manager and Navigate to %WINDIR%\System32\Config

and backup DNS netlogon file as shown below

ADDS_MD_0018

S5-3. Create Two Active-Directory Primary Integrated DNS Forward Lookup Zone

DnsCmd /ZoneAdd <NEW_DOMAIN_NAME> /DsPrimary
DnsCmd /ZoneAdd _msdcs.<NEW_DOMAIN_NAME> /DsPrimary /DP /forest

ADDS_MD_0019

S5-4. Restore DNS NetLogon backup File

S5-5. Open Properties of new zone and set Dynamic updates to Secure Only

ADDS_MD_0020

ADDS_MD_0021

S5-6. Restart Active Directory Domain Services Service

ADDS_MD_0022

S5-7. Test DNS using DcDiag Tool

Execute DcDiag /Test:DNS /DnsBasic

ADDS_MD_0023

 

Step 6: Finalize Domain Name Rename

S6-1. Execute RenDom /Clean to remove domain rename status

ADDS_MD_0024

S6-2. Execute RenDom /End to unfreeze Directory Services

ADDS_MD_0025

Step 7: Domain Name Change on Windows Client

S7-1. Windows Client must logon using New Domain Name

 

Step 8: Delete DNS Zone for Old Domain

S8-1. Open DNS Manager

S8-2. Remove Old DNS Zone until all clients have logon using new Domain Name

ADDS_MD_0026

Leave a Reply

Your email address will not be published. Required fields are marked *

one − 1 =

YLNotes: Yunlong Notes © 2017 Frontier Theme