Migrating Server Roles

This guide will demonstrate how to migrate a role from one server to another; for this example we will migrate DHCP but this method can be amended to suit other roles. You should always follow Microsoft's guides and checklists when migrating roles.

On source machine
Create a shared folder on the source machine called "Mig"

On destination machine
Next if not already, intsall Windows Server Migration Tools

Import-Module ServerManager
Add-WindowsFeature Migration

Cd \
cd C:\windows\System32\ServerMigrationTools\

smigdeploy.exe /package /architecture amd64 /os WS08 /path \\sourceserver\Mig

On source machine
cd c:\Mig\<folder-name of your deployment>


Before continuing
Make sure the role being migrated is Installed on the destination server.
Make a note of the source NIC MAC address = getmacgetmac

Stop Service on Destinartion server
Stop-Serve DHCP
Check with that it stopped with:
Get-Service DHCP

Export-SmigServerSetting -FeatureID DHCP -Group -IPConfig -path C:\StorageMig -verbose
Prompted with a password.

Remove DHCP from AD

netsh DHCP delete server.domain.local

On Destination server

We must import the snapin before we can use the Import-SmigServerSetting cmdlet.

Add-PSSnapin Microsoft.windows.servermanager.migration

Import-Smigserversetting -FeatureID DHCP -IPConfig ALL -SourcePhysicalAddress <M-A-C-A-D-D-R-E-S-S> -TargetPhysicalAddress <M-A-C-A-D-D-R-E-S-S> -Path \\sourceserver\c$\StorageMig -Verbose

Start-Service DHCP
netsh DHCP add server newserver.domain.local

Use JetPack to compact the DHCP database

Jetpack is not in the location it should be on a clean install.
Search the windows directory for "Jetpack" and copy it to c:\windows\system32\DHCP\


DHCP (Multi Holmed)

In order for the DHPC binding to be set eech adapter must have only one IP address and it must be static.


Windows server 2012 applies an AutoConfiguration APIPA address as an additional IP. This needs to be disabled to see the Bindings in the DHCP console for additional NICs



the Autoconfiguration belongs to APIPA which is only used if a DHCP server is not available(if enabled) or NO fixed ip address is configured, which you did.

So what problem do you have if it is enabled? Anyway, check this option:

This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly.

Disable APIPA on All but One Network Adapter

  1. Use Registry Editor to create the following registry key, where <var>adapter name</var> is the name of the Dynamic Host Configuration Protocol (DHCP) configured adapter where you want to disable APIPA:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\Tcpip\Parameters\Interfaces\<var>adapter name</var>

  1. Add the following value to this key:

Value name: IPAutoconfigurationEnabled
Value type: REG_DWORD
Value in hexadecimal: 0 (A value of 0 disables APIPA support on this adapter)

NOTE: If the IPAutoconfigurationEnabled entry is not present, a default value of 1 is assumed, which indicates that APIPA is enabled.

  1. After you make this change, restart your computer.