A Windows Server 2022 file server currently uses the manually configured IPv4 address 10.50.20.25/24 together with static DNS and gateway entries. The networking team is converting the VLAN to DHCP for centralized lease management, but the server must continue to use the same address so that mapped drives and firewall rules are not broken. What is the MOST effective way to meet both requirements while minimizing future administrative effort?
Enable APIPA on the adapter and enter 10.50.20.25/24 in the Alternate Configuration tab.
Delete the static settings, set the NIC to obtain an IP automatically, and create a DHCP reservation that assigns 10.50.20.25 to the server's MAC address.
Enable DHCP failover in load-balance mode for the scope that contains 10.50.20.0/24.
Configure DHCP scope option 66 with the value 10.50.20.25 so the address is delivered during boot.
Changing the NIC from a manual configuration to DHCP and then creating a reservation in the DHCP scope binds the server's MAC address to 10.50.20.25. Each time the adapter requests an address, the DHCP server offers the reserved one, so the server keeps the familiar IP while still receiving any updated scope options.
APIPA and an Alternate Configuration are used only when a DHCP server is unreachable, so the address could change once DHCP becomes available.
Scope option 66 merely supplies a TFTP or boot-server name to clients; it does not set the client's own IP address.
DHCP failover in load-balance mode improves availability by sharing a scope between two servers, but it does not guarantee that any specific client will always receive the same lease unless a reservation is also configured.