DHCP Migration From Windows Server 2016 To Windows Server 2019

[@geoffreycoffin2805]

Precise steps and directions. Takes only about 10 minutes to complete. Thank you

[@KapTechPro]

Glad you liked it.
Thankyou so much.

[@MrVeeru87]

Awesome explanation sir... Thank you🙏

[@edwinsabroso6189]

Very insightful. This is impressive.

[@gomeagle1989]

Good teacher. thanks a lot

[@gopalthegoku]

Thanks, it was easy to understand. Are you using cloud services for the lab?

[@brodierobson4490]

Brilliant! Subed and liked

[@KapTechPro]

Glad you liked it.

[@hanitimepass]

👌👌👌👌👌👌

[@harfidzulfareez7280]

Nice bro

[@pg4694]

U have exported the file on a server after that you are running the command to import file on other DHCP server and you also want to copy the file on that server so import command is not sufficient and are both the servers connected imean member server and a domain controller

[@pg4694]

I'm confused in a way like when there is an option to always add a server as an additional domain controller and after that everything will be replicated in the same way to other server then why migration is required

[@andrewg.t9714]

Well versed

[@AlexPerez-fc3ov]

This doesn't import the old DHCP leases ?

[@StoryPotter]

i am getting command not found error while importing the dhcp

[@pg4694]

And one more thing that once u have used windows powershell and on other server u have used cmd can we use both or is there any reason to do the same

[@LordSphax]

You can use both cmd or PowerShell, depend what you prefer. I do recommand to start using the DHCP PowerShell module to get used to btw.