DHCP server ignores link selection option when client send option 50

Question

DHCP server ignores link selection option when client send option 50

Yong-jun Cho 20

Hi Microsoft Support,

We encountered an issue similar to the one described in the following article:

https://learn.microsoft.com/en-us/answers/questions/432543/dhcp-server-ignores-link-selection-option-when-cli

We were able to resolve the issue on Windows Server 2022 by enabling the hidden registry key DhcpFlagSubnetChangeDHCPRequest.

My question is:

Is the DhcpFlagSubnetChangeDHCPRequest registry key supported and functional on Windows Server 2016 as well?

Path: HKEY_LOCAL_MACHINE \System\CurrentControlSet\Services\DhcpServer\Parameters

Value: DhcpFlagSubnetChangeDHCPRequest

Type: REG_DWORD

Value: 0 (disabled, default), 1 (enabled)

Based on our lab testing, it does not appear to have any effect on Windows Server 2016.

Could you please confirm whether this registry key is supported on Windows Server 2016, or if it is only available starting with Windows Server 2022?

Thank you for your assistance.

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hi Yong-jun Cho,

This specific registry parameter acts as a direct instruction manual for the DHCP service. When enabled, it explicitly tells the server to prioritize the network's Link Selection parameters over a client device's request to keep its old IP address when moving to a new subnet. Without this instruction, older servers default to the client's request, resulting in an invalid IP address assignment for the new location. This capability is natively built into the DHCP architecture of Windows Server 2022 and was retroactively added to Windows Server 2019 through cumulative updates.

Because Windows Server 2016 transitioned into Extended Support in January 2022, it receives strict security updates rather than non-security behavioral backports or feature enhancements. The underlying service code for the Windows Server 2016 DHCP engine was never updated to recognize or process this specific registry parameter.

Since the DHCP engine on that version physically lacks the programming required to interpret this flag, there is no alternative registry edit or hotfix available. The only officially supported resolution to this known limitation is migrating your DHCP infrastructure to Windows Server 2019 with the latest updates or directly to Windows Server 2022.

Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

VPHAN