1. From Server Manager, click on the Tools menu in the top right corner, then click on DHCP to bring up the DHCP configuration console.
2. From the DHCP console, expand your domain you wish to work on. After you expand your domain, right click on the scope you wish to configure failover for and click Configure Failover.
3. On the pop-up, verify your scope is selected, then click Next.
4. On the next screen, put in your secondary server on your network you want to failover to. The one requirement would be to already have DHCP service installed on the secondary server. Once you put in your secondary server (or select an existing server already configured with DHCP Failover settings), click on Next.
5. On the failover configuration screen, you can verify your server information on the top, then you can start making configuration settings. After you are done with the following options, click Next.
a. Maximum Client Lead Time: This is kind of finicky. I have read it is recommended to keep default for you put it too low, performance problems will occur, and if you put it too high, it could delay/cause issues for failover.
b. Mode: This is just selecting whether you want Hot standby or load balancing. For this setup, we will select the Hot standby option.
i. Hot Standby Configuration Role of Partner Server: Select Standby for the secondary server, or you can swap roles for it to be the Active server.
ii. Addresses reserved for standby server: This setting allots a percentage of addresses for the standby server so it has addresses available during a failover to issue out.
c. State Switchover Interval: This is how long until the server will try switching back over from what I understand. I will update accordingly after more testing.
d. Enable Message Authentication: This is the ability to use a Shared Secret for the servers to sync together.
6. Finally, verify your information on the last screen and click Finish.
7. Verify the next pop-up has no errors. If there are errors, go back troubleshoot and reconfigure accordingly.
8. Finally, you still need to verify the secondary server sees the failover options and has added the new scope. Navigate to the secondary server, open the DHCP configuration screen and you might have to do a refresh if you do not see the scope. Click on Action in the top menu on the left, then click on refresh to perform this action.
9. Finally, you should see your new failover scope pop-up in the new IPv4 drop down.
2. From the DHCP console, expand your domain you wish to work on. After you expand your domain, right click on the scope you wish to configure failover for and click Configure Failover.
3. On the pop-up, verify your scope is selected, then click Next.
4. On the next screen, put in your secondary server on your network you want to failover to. The one requirement would be to already have DHCP service installed on the secondary server. Once you put in your secondary server (or select an existing server already configured with DHCP Failover settings), click on Next.
5. On the failover configuration screen, you can verify your server information on the top, then you can start making configuration settings. After you are done with the following options, click Next.
a. Maximum Client Lead Time: This is kind of finicky. I have read it is recommended to keep default for you put it too low, performance problems will occur, and if you put it too high, it could delay/cause issues for failover.
b. Mode: This is just selecting whether you want Hot standby or load balancing. For this setup, we will select the Hot standby option.
i. Hot Standby Configuration Role of Partner Server: Select Standby for the secondary server, or you can swap roles for it to be the Active server.
ii. Addresses reserved for standby server: This setting allots a percentage of addresses for the standby server so it has addresses available during a failover to issue out.
c. State Switchover Interval: This is how long until the server will try switching back over from what I understand. I will update accordingly after more testing.
d. Enable Message Authentication: This is the ability to use a Shared Secret for the servers to sync together.
6. Finally, verify your information on the last screen and click Finish.
7. Verify the next pop-up has no errors. If there are errors, go back troubleshoot and reconfigure accordingly.
8. Finally, you still need to verify the secondary server sees the failover options and has added the new scope. Navigate to the secondary server, open the DHCP configuration screen and you might have to do a refresh if you do not see the scope. Click on Action in the top menu on the left, then click on refresh to perform this action.
9. Finally, you should see your new failover scope pop-up in the new IPv4 drop down.
