Score:0

Migrating DHCP clients to new subnet using DHCP superscope?

br flag

I am migrating our dynamically addressed DHCP clients to a new subnet due to requirements coming from the higher ups. I am thinking of doing it like so:

1. Create new scope on DHCP server (Server 2019 DHCP) containing new subnet/scope information
2. Create new superscope containing the old subnet/scope/allocations, plus the new
3. Simply deactivate the old scope

I am hoping that this will result in DHCP clients receiving an address on the new subnet when they time out and request a new address. I will of course add a secondary IP to the VLAN interface which is acting as the default gateway for this subnet.

Can someone with more experience with subnet migrations/DHCP Server chime in? Does this sound like a plan that will succeed?

Thanks!

Appleoddity avatar
ng flag
Why do you need to recreate the old scope and then disable it? What is the challenge to just creating a new scope and getting rid of the old? What are you trying to change about the existing subnet?
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.