DHCP is extremely common and is used by nearly every company out there. Windows Server 2008 R2 is also a very popular server for this kind of operation. These two facts identify this topic as ‘old news’ and is therefore more just for my benefit than anyone else. As usual though, I would be all the more excited if it did turn out to be beneficial for someone else.
Here we go then:
First off, we go into the ‘add roles’ section of server manager and the wizard appears. Under server roles, we check DHCP and click next.
You will end up getting a message that states that you should have these things set:
- A static IP address configured at least for the DHCP server.
- Plan your subnets.
- Plan your scopes.
- Get list of exceptions.
- Record and safely store this information.
After this, you continue to press ‘next’ until you arrive at the network connection bindings page. Here is where you will select the interface through which you will service clients. Usually there is only one network connection and therefore only one option.
After this step, if your server was configured correctly, the next step will be automatically filled out. Including domain and DNS addresses. The next screen is where you add the scope and settings associated with it. It looks something like this:
From here you can add as many scopes as you want. From here you will be able to configure some of the basic things that will be sent out to your clients on the network. The next screen is for disabling or enabling the ipv6 which, for me, I disabled it.
One of the next screens is about authorizing the DHCP server with Active Directory. This is obviously only applicable to those who have Active directory. This is what it looks like:
After this step, it is a confirmation of settings and install. From here, you set your clients to be on DHCP and watch them connect!
Hope it worked!