I have set up another server with DHCP on our domain purely for redundancy. I don't want to use the 80/20 rule. I know the standby DHCP server requires manual intervention if the other DHCP server dies but this will do for me at the moment. I exported the DHCP settings using netsh DHCP server and imported them the same to the other server ok. I have a Scheduled task to run to export the DHCP settings nightly to a txt file so i can import the most up to date settings quickly if i did need to manually start the other DHCP.
My only question is and i think i am correct thinking this anyway but second opinions are always good.
I have imported the scope to the standby server, the DHCP service is running, but i have not authorised the scope yet. Can i leave it sitting like this and then just authorise as i need it in case of the the DHCP server going down, or do i need to stop the DHCP service and start it when i need?
Ihave also set the 'conflict detections attempts' to 2 as recommended my MS for a standby server.
Why not just have 2 servers set up with non-overlapping ranges?
eg if you're using 10.0.0.0 - 10.31.255.255 as your range then split it in half. One DHCP server gives 10.0.0.0 to 10.15.255.255 and the other gives 10.16.0.1 to 10.31.255.255
You can have both servers running and they will spread the load (not much load for DHCP!) and give you redundancy. You obviously have to make changes to both servers if anything changes but it's pretty rare that DHCP settings need changing so it shouldn't be a big job.