The [FSMO role owners](https://woshub.com/transfer-seize-fsmo-roles-in-active-directory/) can be displayed as follows: netdom query fsmo 
After that, you won’t be able to make changes to the AD forest configuration because it will be locked. The `rendom /prepare` command will check the availability of all DCs in the forest and if they are ready to be renamed. Make sure that the command has not returned any errors.  ``` Waiting for DCs to reply. mun-dc02.test.com was prepared successfully mun-dc00.test.com was prepared successfully The operation completed successfully. ``` The command below will rename the domain (domain controllers will be unavailable for some time and restarted automatically to apply new settings): ``` rendom /execute ```  ``` Waiting for DCs to reply. The script was executed successfully on mun-dc02.test.com The script was executed successfully on mun-dc00.test.com 2 servers contacted, 0 servers returned Errors The operation completed successfully. ``` Make sure that the new domain name is displayed in the domain properties. Note that the full computer name did not change. You must provide an account name in the format `newdomain\username` to login to the DC. To get to the DC, specify the account from the domain. On [Windows Core domain controllers](https://woshub.com/windows-server-core-install-active-directory-domain-controller/) you can specify a different username by pressing ESC several times. 
Run the following command to update GPO bindings: ``` gpfixup /olddns:test.com /newdns:resource.loc ```  ``` Group Policy fix up utility Version 1.1 (Microsoft) Start fixing group policy (GroupPolicyContainer) objects: Start fixing site group policy links: Start fixing non-site group policy links: gpfixup tool executed with success. ``` Then update the NetBIOS domain name: ``` gpfixup /oldnb:TEST /newnb:RESOURCE ``` Then add new names on each domain controller manually and make them primary ones: ``` netdom computername %COMPUTERNAME%.test.com /add:%COMPUTERNAME%.resource.loc netdom computername %COMPUTERNAME%.test.com /makeprimary:%COMPUTERNAME%.resource.loc ``` Restart the DCs: ```bash Shutdown –f –r –t 0 ```Only domain controllers need to be manually renamed. The rest of the computers and servers can be rebooted twice and they will automatically switch to the new domain. This must be done after /execute and BEFORE executing the rendom /clean command. Or you can use the commands above to rejoin computers to the new domain.
The command below will remove links to your old domain from AD: ``` rendom /clean ``` Unlock the domain configuration: ``` rendom /end ``` Open the [ADUC](https://woshub.com/install-active-directory-users-computers-aduc-console/) (`dsa.msc`) console and make sure that it has connected to the new domain name and all OU structure, users and computers remain in place. Note that you will have to do some extra steps to re-configure some services (CA, Failover Clusters) to a new domain.
After renaming your domain, check the AD replication state and errors on the DCs (see the link above). [Original Article](https://woshub.com/rename-active-directory-domain/)