ibysmalls

If they are setup in an windows Domain Controller environment then they need Authorisation. Its basically right clicking the server in the dhcp console and clicking on Authorise. You’ll need admin credentials to setup the server or you could put dhcp role on any windows server on the domain. At our company we install DHCP on the primary domain controller and have the scope split, then install dhcp on the secondary controller too. So both servers dish out ip addresses to clients within the same scope hut different range.

Hi, In windows server you can get dhcp running in very less time, and if you have two windows servers you can split the scope between them for resilience. If your network has tagged vlans etc then you might need to reconfig the switches for the dhcp helper / relay option. If its a bog standard network then yeah, i’d go with windows. Its clearer and easy to use. Ibrahim