There's an official Technet guide for this that I'd use, rather than that one.
The process below is a "merge," rather than what would normally be called an "import", and will only modify existing scopes if you import scopes that exist on the target server.
If that is the case, you'll need to selectively import scopes, instead of just using the
/all switch. The Microsoft KB on importing/exporting specific scopes only is here.
As always, it's better safe than sorry, so you don't want to do anything without some form of backup. In this case, that can be achieved by exporting the database on the target DHCP server before importing the database from the other one. That way, in the event something goes wrong, you can always "restore" the configuration by importing the original database.
Finally, I personally wouldn't bother moving ANYTHING to a Server 2003 server, because I'd be doing everything I can to get rid of or upgrade anything running a decade old OS that's already end of support. (Unless you're paying for extended support, which I doubt). It also happens to be a bit easier to migrate your DHCP database to a DHCP server running Server 2008 R2 or 2012, either through the GUI or with the use of PowerShell.. but if that's not an option, it's not an option.
This step-by-step article describes how to move a Dynamic Host Configuration Protocol (DHCP) database from a computer that is running Microsoft Windows NT Server 4.0, Microsoft Windows 2000, or Microsoft Windows Server 2003 to a computer that is running Windows Server 2003.
Note: You can use the Microsoft Windows backup utility (ntbackup.exe) to back up and restore the DHCP database on a single server. Do not use the backup utility to migrate or to move a DHCP database from one DHCP server to another.
Export the DHCP database from a server that is running Microsoft Windows Server 2003
Note: You must have local administrator permissions to export the data.
Install the DHCP server service on the server that is running Windows Server 2003
Import the DHCP database
Note: You may receive an "access denied" message during this procedure if you are not a member of the Backup Operators group. If you receive an "Unable to determine the DHCP server version for server" error message, make sure that the DHCP Server service is running on the server and that the user logged on is a member of the local Administrators group.
Important: Do not use Dhcpexim.exe to import a DHCP database in Windows Server 2003. Additionally, if the target Windows 2003 server is a member server, and if you plan to promote it to a domain controller, we suggested that you perform the DHCP database migration before promoting it to a domain controller. Although you can migrate the DHCP database to a Windows 2003 domain controller, the migration to a member server will be easier because of the existence of the local administrator account.
- Log on as a user who is an explicit member of the local Administrators group. A user account in a group that is a member of the local Administrators group will not work. If a local Administrators account does not exist for the domain controller, restart the computer in Directory Services Restore Mode, and use the administrator account to import the database as described later in this section.
- Copy the exported DHCP database file to the local hard disk of the Windows Server 2003-based computer.
Verify that the DHCP service is started on the Windows Server 2003-based computer.
Click Start, click Run, type
cmd in the Open box, and then click OK.
At the command prompt, type
netsh dhcp server import c:\dhcpdatabase.txt all, and then press ENTER, where
c:\dhcpdatabase.txt is the full path and file name of the database file that you copied to the server.
833167 A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003
- After you receive the message that the command completed successfully, quit the command prompt.
Authorize the DHCP server
Click Start, point to All Programs, point to Administrative Tools, and then click DHCP.
Note: You must be logged on to the server by using an account that is a member of the Administrators group. In an Active Directory domain, you must be logged on to the server by using an account that is a member of the Enterprise Administrators group.
- In the console tree of the DHCP snap-in, expand the new DHCP server. If there is a red arrow in the lower-right corner of the server object, the server has not yet been authorized.
- Right-click the server object, and then click Authorize.
- After several moments, right-click the server again, and then click Refresh. A green arrow indicates that the DHCP server is authorized.