asked on

Migrating DHCP Server

Hi,

I am migrating Windows 2012 R2 network to Windows 2019 network. So far I have migrated Active Directory from W2012R2 to 2019 and I need to decide on what to do with DHCP server whether to migrate DHCP server currently running on W2012R2 to W2019 or simply create a new DHCP server on W2019 and uninstall DHCP server from W2012R2.

There are only 6 desktop PCs, several mobiles phones & tablet devices registered in Address Leases.
Everything else is straight forward in terms of Address Pool: 192.168.10.100 thru 199, Lease duration: 1 day, Scope Options: Router is 192.168.10.1 DNS Servers: 192.168.10.2 .. etc.

I don't have experience in migrating existing DHCP server to a new server, so I am wondering if it would be wise to create new DHCP server in W2019 and have everyone restart their computers, mobile phones and mobile devices.

Thanks.

Mahesh

you can do either way

U can use netsh commands to export dhcp config from old and import it on new

Follow below artiocle to export from 2012 and import on 2019

https://www.dtonias.com/export-import-dhcp-server-2016-settings/

Prerequisites are you must 1st install and authorize dhcp role on new server
Then export from old server and stop and disable dhcp service on source
Then import it on new server

Finally tell your switches with ip helper protocol and replace old dhcp server IP with new
Else you can uninstall from old and install and configure brand new on new

sglee

ASKER

@Mahesh
Let me try that article and report back.

sglee

ASKER

@Mahesh
At what point do I shut down (or remove DHCP role) DHCP server in W2012R2?
(1) After running "netsh dhcp server export C:\DHCP-Config.txt all" from old server
or
(2) After tunning "netsh dhcp server import C:\DHCP-Config.txt all" on the new server.

Hypercat (Deb)

As Mahesh said, you can do it either way. My advice in your situation it seems it would be possibly easier to simply authorize the new server and create a new scope. Workstations will get new leases whenever their current one tries to renew, IOW, you don't necessarily have to make everyone restart either, unless you want to change the scope.

You need to run the second command and authorize the new server. Then you unauthorize the old one which will stop it from participating in the DHCP on the domain. You can shut down the old server at your leisure.

ASKER CERTIFIED SOLUTION

Mahesh

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

sglee

ASKER

@Mahesh
"then shutdown old server or disable dhcp service on old server" --> are you talking about having to open Services.msc and stop "DHCP server" service?

Mahesh

yes, stop and disable dhcp service

sglee

ASKER

@Mahesh
I stopped DHCP Server service in Services.msc in W2012R2 and ran import command "netsh dhcp server import c:\dhcp\DHCP-Config.txt all" on W2019 Service. But it has been stuck for more than 5 minutes.
Exporting DHCP configuration from W2012R2 Server took only several seconds.

* I could not copy DHCP-Config.txt into C:\ root directory of W2019 due to "permission" error.

Pete Long

I don't know why you are struggling this usually takes me about 25 seconds?.

Windows Server – Migrating DHCP Scopes

Pete

Mahesh

run cmd with run as administrator and then try import

I seen its standard cmd you have opened

Mike Schrock

I'm sure this was completed however we have all been here:
Is the DHCP roll installed and active on the 2019 Server?

sglee

ASKER

@Mahesh
"run cmd with run as administrator and then try import" --> that was it. Thank you!

Philip Elder

We use this CanITPro (Microsoft) method and have been since the 2003 to 2008 days.

It's flawless. Never failed.