Games Microsoft DNS

Renaming Domains

Renaming Domains

An Overview of the Area Renaming Function

With the Home windows NT four area mannequin, you needed to utterly rebuild an present area when you needed to vary the names of any of your present domains. In Home windows 2000 domains, you additionally need to create a brand new area however the Lively Listing Object Supervisor can be utilized emigrate present customers, teams and computer systems into the brand new area. The Lively Listing Object Supervisor performs an important position in shifting the contents of present Home windows 2000 domains into new area buildings. The Lively Listing Object Supervisor is included within the Home windows 2000 Help Instruments. Though you can’t instantly change the DNS and NetBIOS names of a Home windows 2000 area, the Lively Listing Object Supervisor lets you migrate the objects of an present area into a brand new area. Home windows Server 2003 then again features a area rename utility and the potential to rename domains.

In Home windows Server 2003, you possibly can rename a website in a forest which has area controllers operating Home windows Server 2003. You can too transfer any of your present domains to a unique location within the hierarchy of domains. Lastly, you’ll be able to rename area controllers with not needing to first demote them. The renaming area function of Home windows Server 2003 permits you to tackle altering group wants resembling reorganizations, and mergers as a result of it lets you change your present forest construction. You’ll be able to transfer a website to any location inside the forest by which it’s situated. You may as well increase a toddler area to make it the basis of its personal area tree. Renaming domains subsequently lets you create a brand new forest construction.
You can too rename domains with out truly impacting the belief relationships between present domains inside your Lively Listing setting. Whenever you rename domains, you possibly can change the DNS and NetBIOS names of the area, however the area GUID and area SID are left intact. This lets you rename the area and all related baby domains with out affecting the construction of the area tree.

The area rename utility, Rendom.exe, might be discovered on the Home windows Server 2003 CD-ROM, within the ValueaddMsftMgmtDomren folder. The folder additionally consists of one other software, Gpfixup.exe, which is used to wash up the International Catalog. You need to use Rendom.exe for the next duties:

  • Change the DNS identify and NetBIOS identify of the forest root area.
  • Change the DNS identify and NetBIOS identify of a tree root area
  • Change the DNS identify and NetBIOS identify of mother or father domains and youngster domains
  • Change the situation of a website inside a forest.

After you have got used Rendom.exe to carry out one of many above duties/processes, your finish outcome ought to be a well-formed forest. In a well-formed forest, domains within the forest should make up a DNS tree(s) with the forest root area being one of many timber. Along with this, the area listing partition can’t have a mum or dad software listing partition.

The capabilities obtainable in Home windows Server 2003 differ to what you might obtain with Home windows 2000 domains utilizing the Lively Listing Object Supervisor. Home windows 2000 domains have the next limitations:

  • You can’t be a part of two domains to type one area as a single activity
  • You can’t cut up an present area to type two totally different domains as one process.
  • You can’t transfer an present area to a special location in a forest utilizing one course of.

Home windows Server 2003 additionally has a couple of limitations with regards to restructuring a forest, and renaming domains. These are summarized under:

  • The precise variety of domains previous to performing restructuring, and after you’ve gotten carried out restructuring, have to be the identical. What this implies is that in the course of the area rename course of, you can’t add a brand new area to the forest, nor are you able to take away a website from the forest.
  • Though you’ll be able to change the DNS and NetBOS identify of the forest root area, you can’t change the precise forest root area.
  • You additionally can’t transfer a website identify from an present area to a unique area as a single course of.

The Necessities and Penalties of Area Renaming

Earlier than you need to use Rendom.exe to carry out any area renaming duties, you need to guarantee the next:

  • The area controllers have to be operating Home windows Server 2003
  • The forest useful degree have to be raised to the Home windows Server 2003 forest useful degree.
  • You want Enterprise Administrator privileges to carry out any area renaming duties.
  • You need to use a member server to hold out area renaming duties – you can’t use a website controller. The member server turns into your management station for performing the area rename course of.
  • Area DFS root servers have to be operating Home windows 2000 – SP3 or above
  • Trade 2000 should not be put in within the area.

A couple of elements on the area rename course of must be stored in thoughts. These are famous under:

  • Your complete forest is unavailable through the area rename course of.
  • If a website controller(s) can’t be reached, or doesn’t take part in, or end the area rename course of, you must take away the area controller from the forest to ensure that the method to be finalized.
  • As a result of some modifications will not be replicated, and exterior belief relationships not exists, you would need to look at every considered one of your area controllers.
  • The DNS host names of the area controllers usually are not mechanically modified by the Lively Listing area rename function. This creates the necessity so that you can perform the area controller rename course of in your area controllers individually.
  • Though the DNS suffix of your member servers and shopper workstations shall be up to date, it won’t be instantaneously.
  • As soon as the area controllers are rebooted, every shopper workstation operating Home windows 2000 or Home windows XP needs to be rebooted twice.

Getting ready for the Area Rename Course of

The method of getting ready for the area renaming process is mentioned within the forthcoming part of this text.

  • One of many preliminary duties that must be carried out is to boost the forest useful degree to the Home windows Server 2003 forest practical degree. Earlier than trying this, be sure that every area controller is operating Home windows Server 2003. You should use Lively Listing Domains And Trusts to carry out this process:
    1. Open the Lively Listing Domains And Trusts console
    2. Proper-click Lively Listing Domains And Trusts within the console tree, and choose Increase forest Useful Degree from the shortcut menu.
    3. The Increase Area Practical Degree dialog field opens.
    4. Click on Increase.
    5. Click on OK.
  • You additionally want to organize DNS earlier than performing the area rename course of. This includes drawing up the listing of DNS zones that have to be created for the brand new area identify, after which creating the required ahead lookup zones. The area controllers will dynamically replace every DNS zone as soon as the required DNS zones are created.
  • In case you are intending to vary the DNS and NetBIOS names of a website with out affecting the belief relationships between present domains, you needn’t fear about manually creating shortcut belief relationships between the domains in your forest. Nevertheless, in case you are altering the prevailing construction of the forest, you need to create shortcut belief relationships between the domains to take care of trusts relationships after you have got renamed them. You should use Lively Listing Domains And Trusts to create shortcut belief between the domains that you simply need to relocate and its new dad or mum area within the forest. That is crucial as a result of father or mother/youngster area belief relationships wouldn’t exist after the restructuring of the forest. In case you are planning to restructure an present area that’s each a mum or dad area and baby area, you need to create the shortcut belief relationship at two places.
  • The place the area goes to be a brand new tree root after the restructuring course of, you’ll want to create two one-way transitive belief relationships with the forest root area earlier than performing the area renaming operation and restructuring the forest.
  • When domains are renamed, member computer systems mechanically change their main DNS suffixes if the first DNS suffixes are outlined to replace mechanically when the area membership of the pc modifications; and if the pc has no assigned group coverage that defines a main DNS suffix.
    You possibly can confirm whether or not member computer systems will routinely change their main DNS suffixes by way of Management Panel.
    1. On the member pc, open Management Panel
    2. Choose Pc Identify, after which Change
    3. Choose Extra
    4. The Change main area suffix when area membership modifications choice ought to be enabled to ensure that the member pc to vary its main DNS suffix.

    If you wish to verify whether or not group coverage that defines a main DNS suffix is assigned for the member pc,

    1. On the member pc, open a command immediate and enter gpresult
    2. View the output to verify whether or not Main DNS Suffix seems beneath Utilized Group Coverage objects.
  • Earlier than performing the area rename course of, you even have to organize certificates authorities in order that enterprise certificates administration continues to be supported. For this to happen, the Certificates Authority (CA) shouldn’t be put in in any area controllers, and all CAs ought to include LDAP URLs and HTTP URLs in its Authority Info Entry (AIA) and Certificates Distribution Level (CDP) extensions.

The Area Rename Course of

Earlier than performing any area rename processes, you must first carry out a full backup of the system state knowledge hosted by every area controller inside the forest. All infrastructure elements must be backed up.

The member server which you’ll use to carry out the area rename course of from ought to be recognized and ready. The member server needs to be a member of one of many domains that you simply planning to rename. Keep in mind that you can’t carry out the area rename course of from a website controller. The member server (additionally referred to as a management station) which you select needs to be operating one of many following Home windows Server 2003 editions:

  • Home windows Server 2003 Normal Version
  • Home windows Server 2003 Enterprise Version
  • Home windows Server 2003 Datacenter Version

You even have to put in a set of Home windows Help instruments on the management station/member server that’s crucial for the area rename course of. These rename instruments are situated on the Home windows Server 2003 CD-ROM.
Use the steps under to put in the required set of rename instruments on the management station/member server.

  1. On the management station, create a folder through which the rename instruments ought to be positioned.
  2. Place the Home windows Server 2003 CD-ROM within the CD-ROM drive.
  3. From the command immediate, copy the rename instruments from the ValueaddMsftMgmtDomren folder. Be sure that rendom.exe and gpfixup.exe are copied to the member server
  4. Set up the Home windows Server 2003 Help instruments on the member server as properly.
    Make sure that repadmin.exe and dfsutil.exe are put in.

The next step within the area rename course of is to make use of rendom.exe to generate a present forest description file. This file might be used because the baseline from which you’ll work. The forest description file will include all present area listing partitions and software listing partitions inside your forest.
Use the steps under to create a forest description file:

  1. On the member server, utilizing Enterprise Administrator privileges open a command immediate.
  2. Change to the RenameTools listing.
  3. Enter rendom /listing to create the domainlist.xm file. That is the file that lists all the prevailing area listing partitions and software listing partitions inside your forest. The domainlist.xml file is created within the present listing.
  4. Enter copy domainlist.xml domainlist-save.xml to save lots of the forest description file.

The subsequent step within the area rename course of is to design the brand new forest. To do that, use a textual content editor like Notepad to vary the domainlist.xml file. You possibly can change the prevailing domains to new domains, and alter the prevailing software listing partitions’ names to new names. Keep in mind that whenever you change the identify of a website, you additionally want to vary the related DNS-specific software listing partition identify. Once you rename a dad or mum area that features baby domains, keep in mind to vary the names of all related youngster domains as properly. After finishing all modifications, confirm the contents of the domainlist.xml file. You need to use the rendom /showforest command to view the brand new forest construction within the domainlist.xml file.

After you’ve created the modifications within the domainlist.xml file, you subsequent need to create the area rename directions that may execute on every area controller in order that your modifications might be carried out. Your modifications are ultimately written to the msDS-UpdateScript attribute on the Partitions container object. The Partitions container object is discovered within the configuration listing partition on the Area Naming Grasp for the forest.
Use the steps under to create the area rename directions

  1. From a command immediate, change to the RenameTools listing
  2. Sort the next command to add the area rename directions to Lively Listing: rendom /add.

The command creates a dclist.xml state file within the RenameTools present listing. That is the file that rendom.exe makes use of to watch the area rename course of and the state of the area controllers inside the forest.

The next step within the area rename course of is to drive Lively Listing replication in order that the area rename directions loaded to the Area Naming Grasp are pushed to every area controller inside the forest.
Use the steps under to pressure Lively Listing replication:

  1. From a command immediate, change to the RenameTools listing
  2. Enter the next command: repadmin /syncall /d /e /P /q DomainNamingMaster (DomainNamingMaster = DNS host identify of the prevailing Area Naming Grasp for the actual forest)

Following this, it’s essential confirm that the DNS data for the brand new area have been created. The Internet Logon service of every area controller publishes the SRV useful resource data to the authoritative DNS servers.
To confirm the DNS data,

  1. Click on Begin, Packages, Administrative Instruments, after which DNS
  2. Proceed to broaden the server identify, Ahead Lookup Zones, after which broaden the area which you need to examine.
  3. Verify that the next DNS data exist for every area controller within the area:
    • One CNAME document related to every area controller on all authoritative DNS servers.
    • One SRV document for the PDC FSMO on all authoritative DNS servers
    • One SRV document for one area controller on all authoritative DNS servers for each area
    • One SRV document related to one International Catalog on all authoritative DNS servers within the forest.

After verifying that the required DNS data exist, it’s a must to confirm the standing of the area controllers inside the forest. This primarily includes checking the Lively Listing database state on every area controller.

  1. From a command immediate, change to the RenameTools listing
  2. Enter the next command: repadmin/put together.
  3. At this level, rendom.exe verifies that the msDS-UpdateScript and msDS-DnsRootAlias attributes are replicated to every area controller inside the forest. It additionally checks that the servicePrincipalNameattribute is replicated to every area controller inside the area and the International Catalog. Rendom.exe checks too that the dclist.xml state file is current within the RenameTools listing. It verifies that the file has an entry for every area controller within the forest.
  4. The member server/management station sends a Distant Process Name (RPC) to every area controller within the forest as nicely to examine the state of the Lively Listing listing copy. The standing of the area controllers is up to date within the dclist.xml file state file to the Ready standing. This means that the area controllers are able to run the area rename directions.

The next step is to execute the area rename directions utilizing the rendom utility on the area controllers. What occurs is that the management station/member server sends an RPC to every area controller. When a website controller receives its RPC from the management station, it in flip executes the area rename directions. The area controller reboots after this. In any case area controllers have executed the area rename directions, you’ll be able to examine the standing of the area controllers within the dclist.xml state file. A standing of Finished signifies that the area controller has efficiently executed the area rename course of. A standing of Error signifies that the area controller was unable to conclude the area rename course of. Any area controller that’s unable to finish the area renaming course of needs to be faraway from the forest.

Use the steps under to execute the area rename directions in your area controllers inside the forest. It’s a must to repeat the method till every area controller is up to date or to the purpose that a specific area controller couldn’t full the area rename course of. As talked about earlier, you’ll be able to confirm the standing of the area controllers within the dclist.xml state file.

  1. From a command immediate, change to the RenameTools listing
  2. Sort the next command: rendom /execute
  3. Proceed to verify the standing of the area controllers within the dclist.xml state file.

You’ll be able to pressure the rendom/execute command in the event you assume that a area controller which has the Error state within the dclist.xml file could be recovered. Forcing the rendom/execute command, leads to the management station resending the RPC to the actual area controller
To do that,

  1. From a command immediate, change to the RenameTools listing
  2. Within the dclist.xml file, discover the Retry> subject for the area controller that you simply need to pressure the rendom /execute command for.
  3. Proceed to edit this to Retry>sure for the actual area controller.
  4. To resend the RPC to the actual area controller, proceed to enter the rendom /execute command.
  5. Recheck the standing of the actual area controller within the dclist.xml state file. A standing of Carried out would imply that the area rename course of accomplished efficiently on the actual area controller. If the state is Ready, attempt getting into the rendom /execute command once more. If the state is Error, think about eradicating the area controller from the forest.

Duties that ought to be accomplished after the area rename course of

  • As a result of your complete forest is unavailable in the course of the area renaming course of, you would wish to principally make the forest configuration out there once more after the area rename course of is accomplished.
    To do that,
    1. Proceed to reboot the management station/member server two occasions.
    2. Open a command immediate and change to the RenameTools listing
    3. Enter the next command: rendom /finish.
    4. This motion removes the msDS-UpdateScript attribute from the configuration listing partition on the Area Naming Grasp for the forest.
  • One of many steps carried out when getting ready for the area rename course of was to create the suitable shortcut belief relationships between the domains within the forest. These trustrelationships are mechanically created as a part of the area rename course of. Any mandatory exterior belief relationships should be manually created.
  • After the area rename course of is accomplished, you need to look at all of your belief relationships to examine whether or not any belief relationships exist which are not wanted. You’ll be able to take away these belief relationships by way of the utilization of the Lively Listing Domains and Trusts console.
  • Along with checking for not wanted belief relationships, it is best to verify for DNS zones which might be not required. If you must take away any DNS zones, use the DNS administration device.
  • Subsequent, you must use the gpfixup.exe command-line device that you simply downloaded when putting in the Home windows Server 2003 Help instruments to restore the GPOs and their hyperlinks in order that they mirror the right info in every area that was renamed. You would need to run Gpfixup.exe on every area controller inside each renamed area.
  • One of many instruments downloaded through the set up of the Home windows Server 2003 Help instruments on the management station was the dfsutil.exe command-line software. You must now use the software to scan the DFS topology and repair any situations of the earlier identify(s) with the brand new identify(s).
  • To carry out an attribute cleanup after the area rename course of, execute the rendom /clear command from a command immediate.
  • As a result of the area rename course of might end result within the renaming of TAPI particular software listing partitions, you would wish to republish the service connection factors for the appliance listing partition’s new identify. That is crucial for TAPI shoppers to seek out the appliance listing partition that was renamed.
  • You should use the steps under to restore the shortcuts to the Area Safety Coverage and Area Controller Safety Coverage MMC snap-ins within the Begin menu. This course of needs to be accomplished on every area controller in every renamed area.
    To do that,
    1. Click on Begin, Packages, Administrative Instruments.
    2. Proper-click Area Safety Coverage and click on Properties from the shortcut menu.
    3. Change the Goal subject (/gpobject: setting ) to mirror the brand new area identify.
    4. Click on OK.
    5. Click on Begin, Packages, Administrative Instruments.
    6. Proper-click the Area Controller Safety Coverage and select Properties from the shortcut menu.
    7. Change the Goal area (/gpobject: setting ) to mirror the brand new area identify
    8. Click on OK.
  • Every member pc of the renamed area(s) needs to be restarted for the area membership modifications to take impact. You need to reboot every member pc two occasions.
  • It’s usually advisable to carry out all crucial backups of the area controllers after the area rename course of as a result of the Lively Listing database, Registry and GPOs on every area controller has since modified. You must carry out the next backups:
    1. A full system state backup of all area controllers inside the forest, along with a backup of all knowledge volumes as properly.
    2. A backup of all GPOs on every area controller.

Renaming Area Controllers

As a result of the DNS host names of area controllers within the renamed domains don’t routinely replace through the area rename course of, you must change the DNS host identify. With Home windows Server 2003, you not should first demote the area controller, then rename it, after which re-promote the server to be a website controller. This was principally the method for Home windows 2000 domains.
In Home windows Server 2003, you possibly can rename the area controller with out having to demote it if the area practical degree is raised to the Home windows Server 2003 area useful degree. What this principally means is that every area controller needs to be operating Home windows Server 2003. To boost the area useful degree for area controllers within the area, use the Lively Dirctory Domains and Trusts console.
One other activity that must be carried out earlier than you possibly can rename the area controllers is to maneuver all International Catalog and all FSMO roles from the basis area controller to a unique area controller. This activity just isn’t mandatory in case you have manually created these roles inside your Lively Listing setting.
The Netdom command-line utility is used to rename area controllers. The device is included within the Home windows Help Instruments on the Home windows Server 2003 Setup CD-ROM. The Netdom Computername command is the command used to handle pc names.

To rename a website controller, use the steps listed within the following part:

  1. Open a command immediate.
  2. Execute the next area controller rename command: Netdom Computername OldComputerName /add:NewComputerName.
    • OldComputerName = present pc identify/IP handle of the area controller that you’re renaming.
    • NewComputerName = new identify for the area controller
  3. After some time, the pc account must be replicated all through the area. All applicable DNS useful resource data also needs to be distributed to all authoritative DNS servers. That is often after the replication latency time interval.
  4. Enter the next command on the command immediate: netdom computername OldComputerName /makeprimary: NewComputerName.
  5. Reboot the pc.
  6. You need to use carry out the next duties to confirm that the area controller was renamed:
    • On the command immediate, enter netdom computername NewComputerName /enumerate. At this level, the area controller has two names
    • Click on Begin, Management Panel, after which click on System. Verify that the identify that seems on the Pc Identify tab after Full Pc Identify is right. Click on Cancel to exit.
  7. You now should take away the previous area controller identify. To do that, enter the next command on the command immediate: netdom computername NewComputerName /take away:OldComputerName.

 

Recent Comments

    Categories