How To Move Dhcp Service From Server 2008 To Server 2016

DHCP Server Migration: Migrating the DHCP Server Function

Commodity
08/31/2016
seven minutes to read

Applies To: Windows Server 2008, Windows Server 2012 R2, Windows Server 2012

Complete the following procedures to migrate a DHCP Server.

Migrating DHCP Server to the destination server
Migrating DHCP Server from the source server
Destination server final migration steps

Migrating DHCP Server to the destination server

Membership in Domain Administrators or equivalent is the minimum required to consummate these procedures. Review details near how to employ the advisable accounts and group memberships at Run a program with authoritative credentials (https://go.microsoft.com/fwlink/?LinkId=131210).

To migrate DHCP Server to the destination server

If it is not already installed, install DHCP Server on the destination server, as previously described in the "Prepare the destination server" section in DHCP Server Migration: Preparing to Migrate.

If information technology is running, stop the DHCP Server service by running the following command:

                  End-Service DHCPserver

If you are unsure whether the service is running, you can check its state by running the following command:

                  Get-Service DHCPServer

Migrating DHCP Server from the source server

Follow these steps to migrate DHCP Server from the source server.

To migrate DHCP Server from the source server

Open up a Windows PowerShell session with elevated user rights. To exercise this, click Start, click All Programs, click Accessories, open the Windows PowerShell binder, correct-click Windows PowerShell, and then click Run as ambassador.
Load Windows Server Migration Tools into your session.

If you opened the current session past using the Windows Server Migration Tools shortcut on the Start menu, skip this stride, and get to step 3. Merely load the Windows Server Migration Tools snap-in in a session that was opened by using some other method, and into which the snap-in has non already been loaded. To load Windows Server Migration Tools, type the post-obit, and then press Enter.
```
                  Add together-PSSnapin Microsoft.Windows.ServerManager.Migration                                  
```
Collect data from the source server past running the Consign-SmigServerSetting cmdlet as an administrator. The Consign-SmigServerSetting cmdlet parameters can collect all source DHCP server data in a single file (Svrmig.mig). Or, the Export-SmigServerSetting cmdlet can be run multiple times, with each iteration using one or more parameters to collect and store data in multiple Svrmig.mig files. For more information, see DHCP Server Migration: Preparing to Migrate. Before you run this command, review the following:
- When yous run the control in step iv, you are prompted to provide a countersign to encrypt the migration shop information. You must provide this same password to import from the migration shop.
- The path parameter can exist an empty or nonempty directory. The actual data file in the directory (Svrmig.mig) is created past the Export-SmigServerSetting cmdlet. Therefore, the user does non have to specify a file name.
- If the path is not a shared location that the destination server can read from, y'all must manually copy the migration shop to the destination server or a location that the destination server tin access.
- If a migration store location already exists and you want to rerun the Export-SmigServerSetting cmdlet, you must motility the Svrmig.mig file from that location and shop it elsewhere, rename or first delete the migration shop.
- You can perform both IP and DHCP Server migration at the same time from a Windows PowerShell prompt past using the Export-SmigServerSetting cmdlet combined with the IPConfig switch, on a single command line.
- Additional command line parameter information:
  - -Users and -Group parameters
    
    The -Users parameter must be specified merely if the DHCP Administrators group includes local users. Otherwise, you can use the -Grouping parameter and all members of DHCP administrators will be migrated. Administrator group members can include domain users.
    
    Important
    
    If the source server is a domain controller, but the destination server is not, Domain Local groups are migrated equally local groups, and domain users are migrated as local users.
  - The -IPConfig parameter collects IP data when information technology is used with the Export-SmigServerSetting cmdlet on the source server; the -IPConfig parameter applies settings when the Import-SmigServerSetting cmdlet is used on the destination server.
    
    If the source DHCP Server has multiple network adapters and the DHCP server service is bound to more i network adapter and serving IP addresses on different subnets, the destination DHCP Server must also have multiple network adapters so that information technology can serve the same subnets as the source DHCP Server. For more information, run into Migrate IP Configuration to Windows Server 2012. Because IP configuration details will exist used later when importing IP configuration settings to the destination server, it is a best exercise to salve the IP configuration settings past using the following command:
```
                          IPConfig /all > IPSettings.txt                                                  
```
    The Import-SmigServerSetting cmdlet requires you lot to map the source physical accost to the destination concrete address.
  Note
  
  The destination server can exist assigned the same static IP address equally the source server, unless other roles on the source server must keep to run on it. In that example, the static IP accost of the destination server can be whatsoever unallocated static IP accost in the same subnet as the source server.
On the source server, run the Export-SmigServerSetting cmdlet, where <storepath> is the path that will contain the Svrmig.mig file after this step is completed. An example of the path is \\fileserver\users\username\dhcpstore.
```
                  Export-SmigServerSetting -featureID DHCP -User All -Group -IPConfig -path <storepath> -Verbose                                  
```
For more than information nearly how to export IP configuration settings, run across Migrate IP Configuration to Windows Server 2012.
On the source server, delete the DHCP authorisation for the source DHCP server by running the following command, where Server FQDN is the fully qualified domain name (FQDN) of the DHCP server and Server IPAddress is the IP address of the server. The command parameters are case-sensitive and must announced exactly as shown.
```
                  Netsh DHCP delete server <Server FQDN> <Server IPAddress>                                  
```

Destination server final migration steps

Render to the destination server and follow these steps to consummate the migration.

Before you lot use the Import-SmigServerSetting cmdlet to import the DHCP server settings, be aware of the post-obit weather condition:

You tin either apply a single control line with all the parameters to import DHCP settings (as when you export information from the source server) or yous tin use the Import cmdlet multiple times to import data one parameter at a time.
If you make up one's mind to run the Import-SmigServerSetting cmdlet separately to import the IP settings, see Migrate IP Configuration to Windows Server 2012. Use the source IPSettings.txt file, referred to in step three of the previous procedure. Yous will map the source physical addresses to the destination physical addresses in footstep three of this procedure.

Important

If you will be importing office and IP settings separately, you should import IP settings first to avoid any IP conflicts. You can and then import the DHCP office.

If the DHCP Administrators group includes local users, then use the -Users parameter combined with the -Group parameter to import local users into the DHCP Administrators grouping. If it only contains domain users, then employ just the -Grouping parameter.

Security Notation
If the source server is a domain member server, but the destination server is a domain controller, imported local users are elevated to domain users, and imported local groups become Domain Local groups on the destination server.

If the DHCP Server role that you are migrating has not yet been installed on the destination server, the Import-SmigServerSetting cmdlet will install that DHCP Server role and its dependencies, described in the side by side step. you might have to restart the destination reckoner to complete the installation after the DHCP Server office is installed by the cmdlet. And so, to complete the import operation after you restart the computer yous must run the Import-SmigServerSetting cmdlet once more forth with the -Force parameter..

On the destination server, run the following command, where <storepath> is the bachelor path that contains the Svrmig.mig file, <SourcePhysicalAddress-1> and <SourcePhysicalAddress-2> are comma-separated lists of the concrete addresses of the source network adapter, and <TargetPhysicalAddress-one> and <TargetPhysicalAddress-ii> are comma-separated lists of the physical addresses of the destination network adapter:
```
                  Import-SmigServerSetting -featureid DHCP -User All -Grouping -IPConfig <All | Global | NIC> -SourcePhysicalAddress <SourcePhysicalAddress-1>,<SourcePhysicalAddress-2> -TargetPhysicalAddress <TargetPhysicalAddress-i>,<TargetPhysicalAddress-2> -Force -path <storepath> -Verbose                                  
```
The -IPConfig switch should exist used with the value All in case the user wants to import all source settings. For more information, encounter Migrate IP Configuration to Windows Server 2012.

Important

If you import the source server IP address to the target server together with the DHCP role without disconnecting or irresolute the IP address of the source server, an IP address conflict will occur.

Run the following command to start the DHCP service:

                  Start-Service DHCPServer

Qualify the destination server. Control parameters are case-sensitive and must appear exactly every bit shown. On the destination server, run the post-obit command where Server FQDN is the FQDN of the DHCP Server and Server IPAddress is the IP address of the server:
```
                  netsh DHCP add together server <Server FQDN> <Server IPAddress>                                  
```

Note

After authorization, the Server Director result log might show result ID 1046. This is a known result and is expected to occur merely once. The event can be safely ignored.

When this migration is finished, client computers on the network server are served by the new x64-based destination server running Windows Server 2012 R2. The migration is complete when the destination server is set up to serve IP addresses to the network.