Brief Introduction to DHCP server migration

For some migration problems, we need to pay attention to the server applications. Here we will explain the migration of DHCP servers. Recently, one of my migration projects needs to migrate the DHCP server from the original domain to the newly created domain, because the original domain is no longer available ). Of course, you can simply create a new DHCP server in the new AD environment, and then close the entire company. However, most companies still want to maintain their original services and do not need to re-create lease projects.

You need to migrate two parts of the DHCP server: DHCP server configuration and database rental. The migration configuration can only be disabled by "Closing the entire company", because every customer wants to close the configuration at the same time, so that the two computers do not have the same IP address. The two computers here refer to the computers that obtained the address from the original DHCP server and the other computers that obtained the address from the new server ). Therefore, the best solution for migrating DHCP servers in the new AD environment while allowing customers to continue running is to migrate configurations and lease databases together.

The first step is to install DHCP in the new AD forest and perform authentication. For more information about installing DHCP, see MSKB300429. Next, the actual migration section. Most customers receive their lease from the very beginning of their work day, so this part can be completed during work.

If you are migrating from a Windows 2003 AD environment to another environment, you can use the netsh command to export the original DHCP data and then import it to the new server. Three steps are required:

Run the following command on the original DHCP server: netsh dhcp server export all

Disable and invalidate the DHCP server service

Migrate the file to the new DHCP server and run the following command: netsh dhcp Server Import <File Name> All

If the migration is not performed from a Windows 2003 environment, you can still complete the task. Microsoft has created the DHCP Export Import tool DHCPEXIM), which was initially launched with the Windows 2000 resource tool. Running this tool on the original DHCP server can be exported and make the range you have migrated invalid. Compared with the NETSH method, this tool has great advantages. By selecting the migration range, you can migrate data from one server to several other servers ). Create a binary file that includes the configuration you selected and the scope of the lease database. Migrate the file to the new DHCP server where the DHCP server has been installed and authenticated), and then run DHCPEXIM. After the information is imported into the exported file, it is the running DHCP server. After the activity scope and active client leasing are completed, you don't have to worry about the same IP configuration.