How To Check Domain Name In Windows Server 2012

In this short commodity, we volition bear witness y'all how to properly change an Active Directory domain name from test.com to resource.loc. In fact, it is not the best thought to rename an Agile Directory domain. In large and complex AD infrastructure, it is better to migrate users, computers, and servers to a new domain. All the same, for elementary and minor Advertizing environments (examination, pre-prod, or DMZ ), you can hands rename your AD domain co-ordinate to this guide

Before you start, brand sure that:

• You lot have an upwardly-to-date backup of your domain controllers;
• Replication works correctly in your domain and in that location are no critical errors of domain controllers or DNS (How to check Active Directory health);
• There is no Substitution in your domain. You cannot rename an AD domain if Commutation is deployed in it (except for Substitution Server 2003);
• To rename a domain, you need Windows Server 2003 or newer (in my case, the functional level of my AD domain and forest is Windows Server 2016).

Kickoff of all, create a DNS zone for your new domain on your electric current domain controllers. To do information technology, open the dnsmgmt.msc snap-in, create a new primary Forward Lookup Zone with the name resource.loc and replicate it on all DNS servers in your erstwhile test.com domain.

You can create a new DNS zone using PowerShell:

Add-DnsServerPrimaryZone -Proper name resource.loc -ReplicationScope "Domain" –PassThru

Wait till the new DNS zone is replicated on all DCs.

Run the rendom /list control to generate a Domainlist.xml file with the current AD forest configuration.

Get-Content .\Domainlist.xml

<Forest> <Domain> <!-- PartitionType:Application --> <Guid>6944a1cc-d79a-4bdb-9d1b-411fd417bbbc</Guid> <DNSname>DomainDnsZones.examination.com</DNSname> <NetBiosName></NetBiosName> <DcName></DcName> </Domain> <Domain> <!-- PartitionType:Application --> <Guid>bb10d409-4897-4974-9781-77dd94f17d47</Guid> <DNSname>ForestDnsZones.test.com</DNSname> <NetBiosName></NetBiosName> <DcName></DcName> </Domain> <Domain> <!-- ForestRoot --> <Guid>b91bcb80-7cbc-49b7-8704-11d41b77d891</Guid> <DNSname>test.com</DNSname> <NetBiosName>Test</NetBiosName> <DcName></DcName> </Domain> </Wood>

Open the Domainlist.xml and replace all onetime domain names with the new ones:

Notepad .\Domainlist.xml

Save the file and run this command:

rendom /showforest

The command volition show the changes to be fabricated in the configuration.

The following control volition upload Domainlist.xml with the new configuration of Advertising partitions to the domain controller with the Domain naming master FSMO function:

rendom /upload

After that, you won't be able to make changes to the Advertizement forest configuration because it volition be locked.

The rendom /prepare control will check the availability of all DCs in the forest and if they are ready to be renamed.

Brand sure that the command has not returned any errors.

Waiting for DCs to answer. 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 fourth dimension 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.exam.com ii servers contacted, 0 servers returned Errors The functioning completed successfully.

Make sure that the new domain proper noun is displayed in the domain properties. Note that the full reckoner proper name did not change.

You must provide an business relationship name in the format newdomain\username to login to the DC.

To go to the DC, specify the account from the domain. On Windows Cadre domain controllers you can specify a different username by pressing ESC several times.

Run the post-obit command to update GPO bindings:

gpfixup /olddns:examination.com /newdns:resources.loc

Group Policy set upwardly utility Version ane.1 (Microsoft) Start fixing group policy (GroupPolicyContainer) objects: Starting time fixing site group policy links: Outset fixing non-site grouping 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 brand them primary ones:

netdom computername %COMPUTERNAME%.test.com /add:%COMPUTERNAME%.resources.loc
netdom computername %COMPUTERNAME%.test.com /makeprimary:%COMPUTERNAME%.resource.loc

Restart the DCs:

Shutdown –f –r –t 0

Simply domain controllers need to exist manually renamed. The rest of the computers and servers tin be rebooted twice and they will automatically switch to the new domain.

This must exist done after /execute and BEFORE executing the rendom /make clean command.

Or you tin can use the commands above to rejoin computers to the new domain.

The control beneath will remove links to your old domain from Advert:

rendom /make clean

Unlock the domain configuration:

rendom /end

Open the ADUC (dsa.msc) console and brand sure that information technology has continued to the new domain name and all OU structure, users and computers remain in place.

Annotation that you volition accept to do some extra steps to re-configure some services (CA, Failover Clusters) to a new domain.

After renaming your domain, bank check the AD replication state and errors on the DCs (see the link above).

Source: http://woshub.com/rename-active-directory-domain/

Posted by: mcgonaglewourease.blogspot.com

Share this post