How to migrate a DHCP server successfully

I found out how to migrate the print server simultaneously during AD migration. Here, I will continue to talk about migrating server issues in a new ad environment. Recently, one of the migration projects that I've done requires migrating the DHCP server from the original domain to the newly created domain (obviously because the original domain is already out of use). Of course, you can simply choose to create an entirely new DHCP server in the newly ad environment and then shut down the entire company. But most companies still want to maintain their original services and do not need to re-create the leased items.

You need to migrate two parts of the DHCP server: the DHCP server configuration and the lease database. The migration configuration can only be done by "shutting down the entire company," because each customer probably wants to shut down at the same time to ensure that the same IP address does not come out of the two computers (where the two computers are the computers from the original DHCP server and another computer that gets the address from the new server). Therefore, while allowing customers to continue running, the best solution for migrating DHCP servers in a new ad environment is to migrate the configuration together and lease the database.

The first step is to install DHCP in the new ad forest and authenticate it. (See MSKB300429 For more information on installing DHCP) Next, the actual migration section. Since most customers can receive their leases at the start of the workday, 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 import it into the new server. This takes only three steps:

• Run the following command on the original DHCP server:
  netsh dhcp server export < filename > All
  
• Shutting down and invalidating the DHCP Server service
  
• Migrate the files to the new DHCP server, and run the following command:
  netsh dhcp server import < filename > All

If you are not migrating from a Windows 2003 environment, you can still complete the task. Microsoft has created the DHCP Export Import tool (Dhcpexim), which was originally launched with the Windows 2000 Resource tool. Running the tool in the original DHCP server allows you to export and invalidate the scope of your migration (compared to the netsh approach, it has a huge advantage and you can migrate multiple scopes from one server to several other servers by selecting a migration range). Create a binary file that includes the scope of your selected configuration and lease database. Migrate the file to a new DHCP server (where the DHCP server is already installed and authenticated), and then run Dhcpexim. After importing the information in the export file, that is, the running DHCP server, complete the activity scope and the active client lease, you do not have to worry about the same IP configuration.

I can find Dhcpexim on Microsoft website.