m

With Microsoft’s Server 2012 now upon us it’s time to start testing some migration options. First up it’s a simple DHCP migration, this doesn’t look to have changed much so if you’re familiar with the Windows Server Migration tools all should go pretty smoothly.

First off we need to install the Windows Server Migration tools feature on Server 2012:

  1. Load up Server Manager
  2. Click Manage (up in the top right corner)
  3. Select Add Roles and Features
  4. Select Role-based or feature-base installation and click Next
  5. Select the appropriate Server and click Next
  6. Click Next again on Server Roles without selecting anything as we are after a Feature
  7. Scroll down the Features list and tick the Windows Server Migration Tools, click Install to complete.

With the Migration tools now installed we need to export the appropriate packages for our Source server to use:

  1. On Server 2012 load a command prompt window (winkey+r then cmd)
  2. Change directory to where smigdeploy.exe is stored – cd %Windir%\System32\ServerMigrationTools\
  3. Created the appropriate package based on the source server OS
    Server 2008 R2 – SmigDeploy.exe /package /architecture amd64 /os WS08R2 /path <deployment folder path>
    Server 2008 x64 – SmigDeploy.exe /package /architecture amd64 /os WS08 /path <deployment folder path>
    Server 2003 x64 – SmigDeploy.exe /package /architecture amd64 /os WS03 /path <deployment folder path>
    Server 2008 x86 – SmigDeploy.exe /package /architecture X86 /os WS08 /path <deployment folder path>
    Server 2003 x86 – SmigDeploy.exe /package /architecture X86 /os WS03 /path <deployment folder path>
  4. Once the package has exported copy the folder to the Source server (e.g. folder SMT_WS008R2_amd64 for the 2008R2 server)
  5. Open up a command prompt window on the Source server and browse to the SMT folder that has been copied
  6. Run Smigdeploy.exe

The above will now have the Migration tools powershell loaded and ready to run on the Source server. From here we can now export the DHCP settings:

  1. Stop the DHCP service on the Source server (disable if need be via services.msc)
  2. Run the following – Export-SmigServerSetting -FeatureID “DHCP” -Path “<path to export to>” -Verbose
  3. This will export a .mig file ready for importing on the Destination server.
  4. Now we can import on the Destination server, copy the .mig file to somewhere the Destination server has access to.
  5. Load PowerShell on the Destination server (Server 2012)
  6. Run the following – Import-SmigServerSetting -FeatureID “DHCP” -Path “<path to import from>” -Verbose
    Just a side note, if DHCP is already installed on 2012 stop the service and use the -Force switch to import
  7. Once successful start up the DHCP Server service and check over to confirm

Some sites used as a reference are below:

Technet: Install, Use, and Remove Windows Server Migration Tools
Technet: DHCP Server Migration Guide

2 comments

  1. 02/10/2013 at 3:00 PM Webbo

    Always forget this for 2012 to Add the PSSnapin – Add-PSSnapin Microsoft.Windows.ServerManager.Migration

  2. 03/07/2014 at 6:19 PM Greg

    I’m looking at migrating from Windows 2003 R2 DHCP to Windows 2012 R2. I’ve been able to export the mig files off of each of the 2003 servers but I’m having difficulty importing into two newly built Windows 2012 R2 servers. Base OS, fully patched, then installed DHCP and Server Migration Tools. In Powershell I run:
    Add-PSSnapin Microsoft.Windows.ServerManager.Migration
    Import-SmigServerSetting -FeatureID “DHCP” -Path C:\dhcp3A -Verbose

    I’m prompted for the file’s password which I enter and it replies back with

    ImportSmigserversetting : The requested operation is not supported on this Windows operating system.

    What do I need to do to get this working to import?
    Thanks
    Greg