• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 710
  • Last Modified:

Migrating DHCP from Windows 2003 Server to 2008R2

I've used this article to assist me ( I liked the screenshots) with the migration of DHCP from 2003 to 2008R2. http://social.technet.microsoft.com/wiki/contents/articles/7411.step-by-step-migration-dhcp-from-windows-server-2003-to-windows-server-2008-r2-with-windows-server-migration-tools-en-us.aspx

Everything went well up until I needed to import the configuration to the 2008R2 server.  The import failed, there were many messages that so and so users was not imported because it already existed, etc.  Per this article, I used this powershell command for the import:

Import-SmigServerSetting -featureid DHCP -User All -Group -Force -path\\2008r2 servername\DHCPData -Verbose

I did not remove the 2003 server from active directly yet, because we are not yet ready to decommision it.  Could that be why the import failed?   Also, why does this command reference "User" and "Group"  if I'm looking to import the IP scope, leases, reservations, etc?   Should I be using a different command for the Import to the 2008R2 server?
  • 2
1 Solution
The main thing is making sure that your old DHCP server is no longer authorized in AD for DHCP.  Once that is complete, you should be in the clear to import.  Also, your command looks correct from what the article is suggesting.  I believe you mainly need to make sure that your 2003 server is no longer authorized.
quincycreditAuthor Commented:
ok, so I should go to DHCP on the 2003 server and de-authorize DHCP before running the import on the 2008R2 server?

If there are still issues, can I safely re-authorize DHCP on the 2003 server to bring it back to the way it was?
Yes and yes.  Deauthorize on the 2003 server, and attempt the import.  If things don't go as planned, you should be able to authorize the 2003 without issue.
Though I love Powershell, the link you quoted describes one of the most cumbersome method to migrate DHCP. Another, equally verbose and convoluted method is given here: http://technet.microsoft.com/en-us/library/dd379535(v=ws.10).aspx.

The most simple and pain-free method is to use Netsh command:
netsh dhcp server export C:\temp\dhcpDB all
netsh dhcp server import C:\temp\dhcpDB all


Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now