Step-by-Step Migration DHCP from Windows Server 2003 to Windows Server 2008 R2 with Windows Server Migration Tools

Step-by-Step Migration DHCP from Windows Server 2003 to Windows Server 2008 R2 with Windows Server Migration Tools

I see every day question about DHCP server migration from Windows 2003 to Windows Server 2008 R2, which is why I am writing this article.

I think some people have no information about Windows Server 2008 R2 new feature (Windows Server Migration Tools). With this new feature, you can easily DHCP migration. I'll show how you can use this function and I hope that helps people solve their problems.

First basic Infos:

I use Windows Server 2003 R2, if you have Windows Server 2003, all steps are same.

Windows DHCP Server 2003 Name:
Windows DHCP Server 2003 IP Address:

My Windows DHCP Server 2003 config in TestLab:

Let's go:

First, we must installing PowerShell and .NET Framework on Windows Server 2003.

  1. Windows PowerShell 1.0 Localized Installation Package for Windows Server 2003 and for Windows XP OR Windows PowerShell 2.0 and Windows Remote Management (WinRM) 2.0 (KB968930)
  2. Microsoft .NET Framework 3.5

After installing, click Start, All Programs, Windows PowerShell, click Windows PowerShell.

Run this command:
Net stop “DHCP Server”

After runing, you can see result: The DHCP Server services was stopped successfully.

Now, we install DHCP role on Windows Server 2008 R2. Open Server Manager console, right click on Roles, click Add Roles.

Select DHCP Server, click Next.

Click Next.

Select the network connections that the DHCP Server will use for servicing clients. In my test Lab is (I use IPv4), then click Next

On Parent domain write your Doman Name (my Domain name is, on Preferred and Alternate DNS server IPv4 address, write your DNS IP address (my DNS IP address and, after writing click Validate, then click Next.

I don't have WINS Servers, I select WINS is not required for applications on this network, then click Next (If you have WINS Servers, select WINS is required for applications on this network then write your WINS Server IP address on Preferred and Alternate WINS server IP address).

Click Next.

I don't use IPv6, select Disable DHCPv6 stateless mode for this server, then click Next.

I use Contoso\Administrator account on Use currect crendentials for authorize DHCP sever in AD DS, then click Next.

Now, we can our settings, if is correct, click Install.

After installig, click Close.

Now, install Windows Server Migration Tools feature on Windows Server 2008 R2. Open Server Manager console, right click on Features, click Add Features.

Select Windows Server Migration Tools, then Next.

Click Install.

After installing, click Close.

Click Start, Administrative Tools, Windows Server Migration Tools, then click Windows Server Migration Tools.

Go to ServerMigrationTools folder. Run this command:
cd C:\Windows\System32\ServerMigrationTools

I run ls command and see which files are in ServerMigrationTools folder.

We find a description of utility SmigDeploy by the following command:
.\SmigDeploy.exe /?

To migrate DHCP server running on Server 2003, you created a deployment package using the following command:
.\SmigDeploy.exe /package /architecture x86 /os ws03 /path c:\SMIGDeploy

Folder SMIGDeploy\SMT_ws03_x86 was created successfully.

Content folder.

SMIGDeploy folder must be copied on Windows DHCP Server 2003.

Windows Server 2008 R2

Windows Server 2003

We can run directly from the folder SmigDeploy.exe snap-in to start the Windows Server Migration Tools in Windows Powershell.

We find the cmdlets for migration with this command.
Get-Command –PSSnapin

We learn about the commands with this command.
Get-help Get-SmigServerFeature

Run Get-SmigServerFeature command (Gets the set of all Windows features that can be migrated from the local server or from the migration store).

Result returns, Windows DHCP server 2003 is valid for migration.

To export the DHCP settings from server 2003 to 2008 R2, create new folder on Windows 2008 R2, for example DHCPData, then share this folder with read and change permissions.

After creating and sharing DHCPData folder, run thic command on Windows 2003.
Export-SmigServerSetting -featureID DHCP -User All -Group -path \\DC-2008R2\DHCPData -Verbose

Now, set a password.

Export was completed successfully:

The folder was created a new DHCP svrmig.mig file, this file will be imported in new Windows DHCP Server 2008 R2.

I run this command and delete my Windows DHCP Server 2003 (This command deletes the server with the DNS name of and an IP address of from the list of servers in Active Directory. This effectively removes any authorization for the DHCP Server service to run).
Netsh DHCP delete server

Open PowerShell on Windows Server 2008 R2 and stop DHCP Services. Run this command.
Net Stop "DHCP Server"

Now, run this command for migration.

Import DHCP Configuration Data, points to the folder DHCPData. Run this command.
Import-SmigServerSetting -featureid DHCP -User All -Group -Force -path \\DC-2008R2\DHCPData -Verbose

After finishing, run this command.
Set-service DHCPServer –startuptype automatic

Now, start DHCP Services with this command.
Start-Service DHCPServer

Authorize the DHCP server with this command.
Netsh DHCP add server

DHCP Server has been migrated successfully.

Leave a Comment
  • Please add 4 and 4 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
  • Fernando Lugão Veltem edited Revision 7. Comment: removed em-US from the title

  • Craig Lussier edited Revision 6. Comment: added en-US to tags and title

  • Patris_70 edited Revision 5. Comment: completed

  • Patris_70 edited Revision 4. Comment: completed

  • Patris_70 edited Revision 3. Comment: not completed

  • Patris_70 edited Revision 2. Comment: added photos, not completed, Tonight will be ready  

  • Patris_70 edited Revision 1. Comment: added photo, not completed, Tonight will be ready

  • Patris_70 edited Original. Comment: need work, not completed

Page 1 of 1 (8 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
  • Nice, but too much informations. Short version here

  • Thanks Patris but long procedure.

  • Fernando Lugão Veltem edited Revision 7. Comment: removed em-US from the title

  • This procedure is too long and sticky

    This link can do same thing very simple

  • Worked like a charm. Thanks a ton

  • Thanks for the wonderful article and the nitty gritty details for each step.  If I may say, while this is certainly one way to get the DHCP migration done, it seems like an awful lot of work/configuration compared to simply exporting the database from the original server to a text file, then import it on the new machine and call it a day.  It literally took me about ten minutes.

    You of course will have to shuffle some DC IP addresses around (so the DHCP service will function on the network, using the original server's IP address), but that's relatively painless.

    I just did the DHCP migration from a 2003 to 2008R2 box last night.  Moving the IP addresses was key because we had the following items configured in our environment:

    1) scope options for time service that referenced one 2K3 DC that was replaced by a 2k8r2 DC.

    2) scope options for DNS resolution that referenced the old 2k3 DC IP addresses.

    3) All static member servers in that building/server room were already configured with the original 2k3 DC IP.

    I had been using this method for years when switching out DCs with the DHCP role enabled...2k3 to 2k3.

    Hope that helps and thanks again for this article.

  • Hi.

    If you are doing a revision later of the powershell pictures, you are using "ls" to list all files. Ls is an alias to Get-ChildObject. Ls is used in *nix operating systems, to less confuse people new to powershell i would suggest you use the full cmdlet or short form. Get-ChildObject / CGI. otherwise a great article.