Renaming Domain Controllers in Windows 2003

Windows Server 2003 introduces a new feature that allows domain controllers to be renamed, allowing you to rebuild your network based on your organization and business needs, enhancing management flexibility Sex. The following describes the specific implementation steps and precautions in detail through an example.

1. First, look at the name of the current domain controller (desktop, my computer, properties, computer name): you can see the FQDN name of the current domain controller www.ddvip.net.

2. Execute: Start, run, cmd, switch to command line mode.

3. Enter netdom and you can see that netdom provides a wealth of parameter options.

4. Similar to many command-line tools, the netdom command is also a context-sensitive mode command-line tool that provides context-sensitive parameters and descriptions based on input parameters. For example, typing netdom add will echo the subcommands associated with add. (Note: netdom provides a lot of parameters, you can complete a variety of functions, only the commands related to domain controller renaming are introduced here.)

5. Use the enumerate parameter to see the computer name of the domain controller currently configured. The syntax is as follows:

netdom computername ComputerName /enumerate:{AlternateNames |  PrimaryName |  AllNames}

where ComputerName is the FQDN name of the current domain controller, and enumerate is a filter item with a selectable output name category: AllNames (all displayed), AlternateNames (only alias displayed), PrimaryName (only The main name is displayed. The default is all displayed.

For example: netdom computername www.ddvip.net /enumerate

You can see that there is only one FQDN name www.ddvip.net.

6. Add a new FQDN name with the add parameter, the syntax is as follows:

netdom computername CurrentComputerName /add: NewComputerName

CurrentComputerName -- the current host name, can be FQDN or IP

NewComputerName -- The new hostname to be added, in the format FQDN, note that the DNS suffix needs to be consistent

For example: netdom computername www.ddvip.net /add:smtp.df .com

You can see that the command has been executed correctly. You can see that the new alias has been successfully added using the above view command: smtp.df.com.

7. The following uses the makeprimary parameter to raise the alias to the primary name. The syntax is as follows:

netdom computername CurrentComputerName /makeprimary:NewComputerName

For example: netdom computername www.ddvip.net /makeprimary:smtp.df.com < Br>

Change the DC main name to smtp.df.com, the screen prompts that the command is completed correctly, and the new name will take effect only after restarting.

8. After rebooting, check the current FQDN name of the domain controller. You can see that the name has been successfully renamed to smtp.df.com.

9. After confirming that the renaming is successful, you can remove the old FQDN name with the remove parameter. The syntax is as follows:
netdom computername NewComputerName /remove:OldComputerName

For example: netdom computername smtp. Df.com /remove:www.ddvip.net

At this point, DC renaming has been successfully completed!

Note: 1. To achieve domain controller renaming, the domain controller must be a Windows Server 2003 version with a functional level in 2003 native mode. By default, the newly installed 2003 Server domain controller works in Windows 2000 mixed mode and needs to be promoted to 2003 native mode (AD user and computer, operation, all tasks, and elevated domain functional level) through "AD users and computers".

2. Rename the domain controller with netdom, the essence is to modify the SPN attribute of the domain controller in the active directory, and update the DNS record, these modifications will be automatically copied to other DCs and DNS.

3. After upgrading the main name, the client still maintains access to the old name before restarting.

4.netdom is a system support tool, which needs to be installed before use (CD: \\SUPPORT\\TOOLS\\SUPTOOLS.MSI).