Thanks for making this video! Very easy to follow and way easier than other methods. Also works the same going from 2019 to 2022 or even from 2012 to 2022.
Hi Danny, thank you for this video! by the way, will the clients automatically point to the new DHCP without manually releasing and renewing? like if I have hundreds of clients and does not want to involve them to manually release/ renew their IP's.
Another great video Dan is this this same process if coping scope to another server to split the scope between 2 obviously adding exclusions on both to split the scope
DNS zones are stored within Active Directory and are replicated between domain controllers/DNS servers, so you don't need to migrate from one server to another. Thanks for watching!
Hi, i am planning migration from DC1 to DC2 in my lab to solve evaluation expiration period (i know i can rearm, but this is also a good exercise). So far i moved FSMO roles, joined DC2 as secondary DC and next step would be migrating DHCP and DNS. DC1 is also CA for domain and for SCCM so in my mind i would like to proceed as follows: Migrate DHCP and DNS as they are and then when demote and power off DC1, rename DC2 to DC1 and change IP to the current one set for DC1 to avoid messing with Certificates and not having to create DNS alias records Does that make sense? Thanks!
As far as I am aware, you should never rename an active domain controller. If you really need to rename it, you should demote it, rename it, and then promote it again. I would take this as an additional learning opportunity: never run additional services on a domain controller. Your CA should be it's own server. SCCM should be it's own server. I have a feeling that if you do what you are attempting, things will break. However, it's a lab so probably just do it anyway and see what happens, that's what I would do, as I have no idea what will actually happen and it'll probably be quite interesting to look at trying to resolve any issues that are caused by the renaming. Thanks for watching!
Hello Danny, Could you please provide me a link if you have already worked on Migrating the DHCP server scope or create a new video to migrate to new Server 2019/22 export Import another scenario here is from 2008 server to 2019 but I already have some scope on 2019. now I want to move the scope from server 2008 to 2019 I used the command netsh dhcp server dump > C: " File path " I used Netsh because the export command is not working in 2008 server. Please share your suggestion. Thank you,
Hi Danny. Very nice. One question. I have 2 Win 2012R2 DHCP VMs on load balanced mode to migrate to Win 2022. Do I need to do anything special on the source side ? Cheers
I've not tested this method migrating DHCP that is in a failover mode, but I'm not sure it would work as the exported config would have the hostname/ip of the partner server. Would it not be easier to break the failover pair and then pair one of the old dhcp servers with a new dhcp server, and then once it's replicated, break the pairing again and then pair the first new dhcp server with the second new dhcp server? Once you've done that, your dhcp scopes would be running from both of the new dhcp servers. That's how I would attempt it, but I'd have to do some testing to make sure that it works as I've not done that before.
@@danny_moran Thanks I was thinking the same or add 2nd server as hot standby. But like you said the export should have all the details. I do have a 2nd non critical remote site with the same config so I can try this before doing it on the main site. Also asked a few of my MSP mates they also said just export and import quickly and test out of office hours. Will update. Cheers
Hi I found 2 options Migrating DHCP Failover Configuration If you are using a DHCP failover or DHCP load balancing configuration, after importing the DHCP settings on the first server, you only need to import only the server configuration on the second Windows Server: Import-DhcpServer -Leases -File "C:\DHCP\OldDHCPConf.xml" -ServerConfigOnly -BackupPath "C:\DHCP\Backup" -Verbose After that, you need to perform the standard DHCP Failover configuration.
Or like you suggested Or Assuming they are currently both working as fail over, I'd do this: 1. Create a new system and add DHCP 2. Break the partnership and remove the first old DHCP server 3. Re-make the partnership between the old and new systems. 4. Then break the partnership and bring the second new system in.
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
Thank you for this, helped a ton! You went straight to the tutorial, no fluff. Love it!
Thanks for watching! Glad it helped!
Thanks for making this video! Very easy to follow and way easier than other methods. Also works the same going from 2019 to 2022 or even from 2012 to 2022.
Thanks for watching!
Thank you so much for this fantastic tutorial! It worked perfectly and you've saved me an incredible amount of effort. I really, really appreciate it!
Thanks for watching!
Great tutorial, i must say this way is faster than when i use netsh command, thank you.
I prefer the PowerShell commands over the netsh for this. They seem to perform better in my experience.
Thanks for watching! Hope it comes in useful!
Thank you for this, helped a lot amazing video , plz add more and more :)
Thanks for watching!
This worked great! Thanks!
Thanks for watching!
Very Helpfull. Many thanks !!!
Thanks for watching!
Great video!
Thanks for watching!
Hi Danny, thank you for this video! by the way, will the clients automatically point to the new DHCP without manually releasing and renewing? like if I have hundreds of clients and does not want to involve them to manually release/ renew their IP's.
thanks mate! very clear!
Thanks for watching!
Another great video Dan is this this same process if coping scope to another server to split the scope between 2 obviously adding exclusions on both to split the scope
Yes, it should be, however, I've not tried this.
Thanks for watching!
@@danny_moran works a treat 👍
Very Helpful Guide,
Are you able to do the same to migrate DNS as well using a similar command?
DNS zones are stored within Active Directory and are replicated between domain controllers/DNS servers, so you don't need to migrate from one server to another.
Thanks for watching!
Very Helpfull. thank uuuu
Thanks for watching!
Hi,
i am planning migration from DC1 to DC2 in my lab to solve evaluation expiration period (i know i can rearm, but this is also a good exercise).
So far i moved FSMO roles, joined DC2 as secondary DC and next step would be migrating DHCP and DNS.
DC1 is also CA for domain and for SCCM so in my mind i would like to proceed as follows:
Migrate DHCP and DNS as they are and then when demote and power off DC1, rename DC2 to DC1 and change IP to the current one set for DC1 to avoid messing with Certificates and not having to create DNS alias records
Does that make sense?
Thanks!
As far as I am aware, you should never rename an active domain controller. If you really need to rename it, you should demote it, rename it, and then promote it again.
I would take this as an additional learning opportunity: never run additional services on a domain controller.
Your CA should be it's own server. SCCM should be it's own server.
I have a feeling that if you do what you are attempting, things will break. However, it's a lab so probably just do it anyway and see what happens, that's what I would do, as I have no idea what will actually happen and it'll probably be quite interesting to look at trying to resolve any issues that are caused by the renaming.
Thanks for watching!
Hello Danny,
Could you please provide me a link if you have already worked on Migrating the DHCP server scope or create a new video to migrate to new Server 2019/22
export
Import
another scenario here is from 2008 server to 2019 but I already have some scope on 2019.
now I want to move the scope from server 2008 to 2019
I used the command netsh dhcp server dump > C: " File path "
I used Netsh because the export command is not working in 2008 server.
Please share your suggestion.
Thank you,
What is the error you are getting? The netsh command should work fine using Windows Server 2008.
@@danny_moran I was successfully able to pull the info using " netsh dhcp server dump >c:
ew.txt all "
Can’t we simply back up the dhcp server from old server and restore it on the new one ??
This is essentially what's happening. We are just backing up the configuration on one server and restoring it on another.
Thanks for watching!
Hi Danny. Very nice. One question. I have 2 Win 2012R2 DHCP VMs on load balanced mode to migrate to Win 2022. Do I need to do anything special on the source side ? Cheers
I've not tested this method migrating DHCP that is in a failover mode, but I'm not sure it would work as the exported config would have the hostname/ip of the partner server.
Would it not be easier to break the failover pair and then pair one of the old dhcp servers with a new dhcp server, and then once it's replicated, break the pairing again and then pair the first new dhcp server with the second new dhcp server? Once you've done that, your dhcp scopes would be running from both of the new dhcp servers.
That's how I would attempt it, but I'd have to do some testing to make sure that it works as I've not done that before.
@@danny_moran Thanks I was thinking the same or add 2nd server as hot standby. But like you said the export should have all the details. I do have a 2nd non critical remote site with the same config so I can try this before doing it on the main site. Also asked a few of my MSP mates they also said just export and import quickly and test out of office hours. Will update. Cheers
Hi I found 2 options
Migrating DHCP Failover Configuration
If you are using a DHCP failover or DHCP load balancing configuration, after importing the DHCP settings on the first server, you only need to import only the server configuration on the second Windows Server:
Import-DhcpServer -Leases -File "C:\DHCP\OldDHCPConf.xml" -ServerConfigOnly -BackupPath "C:\DHCP\Backup" -Verbose
After that, you need to perform the standard DHCP Failover configuration.
Or like you suggested
Or
Assuming they are currently both working as fail over, I'd do this:
1. Create a new system and add DHCP
2. Break the partnership and remove the first old DHCP server
3. Re-make the partnership between the old and new systems.
4. Then break the partnership and bring the second new system in.
Thanks for providing this information! Hopefully others will find this useful.
no need to authorize the new dhcp server?
I authorise the new dhcp server at 0:55
Thanks for watching!
❤
Thanks for watching!
Cool)