DHCP is a critical service for almost all data and voice networks as it allows the allocation of IP addresses that are needed to ensure appropriate communication. In this tutorial I will be showing you how you can create a DHCP scope in Windows Server 2012 R2 so you can service client devices from a central location. Equally, you may wish to follow this as part of the process in enabling Windows Deployment Services so you can deploy Windows images over the network.
Note
To demonstrate this tutorial I will be using the following topology consisting of one switch, one PC and the server. As a simple configuration this configuration only consists of one subnet (10.1.1.0/24) with the server having a static IP address of 10.1.1.1 (not included in tutorial).
INSTALLATION
1. The first step is to open Server Manager and then click on Manage and then Add Roles and Features
2. After that click on Next if you haven't skipped the page by default and then select the Role-Based or feature-based installation option then click on next.
3. Next, select the server that you wish to install the DHCP service to and then click on Next
Note
4. Now from the list ensure a tickbox is checked by the DHCP Server service. Upon selection you may be prompted to add additional features, click Add Features to continue. Once checked please click Next to proceed.
5. When presented with the features option simply click Next since the relevant features were already selected previously. After this then click on Next again to proceed to the confirmation.
6. Once presented with the confirmation simply click on Install to start the install and then let it complete the install.
CONFIGURATION
1. After the installation you can now start the configuration of the service. Launch the DHCP console from the start menu and then right click the IPv4 section in the server. Then select New Scope... to create a new scope.
2. From the initial wizard prompt click Next to proceed and then input a suitable name/description that will identify this scope. After that click Next to proceed
3. Next, configure the range of addresses that should be given to clients via DHCP. Also dictate what subnet mask will also be given out as well. Once the relevant details have been filled in click on Next.
4. From this next section you can specify what addresses in the range need to be excluded for static IP addresses as well as how much delay is made before an offer is given. If you set the range correctly you should not need this feature. Once filled in accordingly you can click on Next to proceed
5. The next part is to setup the lease time. The lease dictates how long an IP address should be assigned to a client before it is taken away. Please note that if the client is online and is still using this lease then it will continue to keep the IP address. This feature is for when clients disconnect from the network and how long the server should wait before re-using an IP addresses again. For this example I am going to set it to 1 day.
6. Now we move onto the extended options for DHCP configurations. This includes dictating what the default gateway and DNS servers are. In my topology I do not have these set up however I will still walk you through the process. To continue select Yes, I want to configure these options now and then click on Next
7. To set the default gateway used to reach other networks you need to input the IP address and then click on the Add button. After the relevant addresses have been added simply click on Next
8. Now you need to setup what DNS servers are being used by client devices. If you are using Active Directory then this will be the IP address of your domain controller. Once the relevant IP address has been setup simply click Next
9. The next section is with regards to WINS. WINS is a legacy protocol that was designed to compete with DNS. Chances are very likely you do not have any WINS servers in your network and therefore you can simply click on Next to continue.
10. The final part of configuration is to activate the scope which will enable the service and allow it to service client devices. To complete this select the Yes and then click on Next. After this you can then click on Finish to complete the wizard.
VERIFICATION
To verify the first action I noticed was that PCA had been automatically assigned an IP address from a DHCP server within the range of addresses that we had configured. This can be clearly seen below.
Secondly when reviewing the given leases in the DHCP management console on the server we can see that a lease was handed out to PCA and therefore verifies that our configuration is working.
Hope this Helps,
Josh :smile9:
Note
This tutorial also applies to Windows Server 2012. Most configuration steps do apply to Windows Server 2008 and 2008 R2 however server role installation is different
To demonstrate this tutorial I will be using the following topology consisting of one switch, one PC and the server. As a simple configuration this configuration only consists of one subnet (10.1.1.0/24) with the server having a static IP address of 10.1.1.1 (not included in tutorial).
INSTALLATION
1. The first step is to open Server Manager and then click on Manage and then Add Roles and Features
2. After that click on Next if you haven't skipped the page by default and then select the Role-Based or feature-based installation option then click on next.
3. Next, select the server that you wish to install the DHCP service to and then click on Next
Note
Since this topology only includes one server I will only be selecting this option.
4. Now from the list ensure a tickbox is checked by the DHCP Server service. Upon selection you may be prompted to add additional features, click Add Features to continue. Once checked please click Next to proceed.
5. When presented with the features option simply click Next since the relevant features were already selected previously. After this then click on Next again to proceed to the confirmation.
6. Once presented with the confirmation simply click on Install to start the install and then let it complete the install.
CONFIGURATION
1. After the installation you can now start the configuration of the service. Launch the DHCP console from the start menu and then right click the IPv4 section in the server. Then select New Scope... to create a new scope.
2. From the initial wizard prompt click Next to proceed and then input a suitable name/description that will identify this scope. After that click Next to proceed
3. Next, configure the range of addresses that should be given to clients via DHCP. Also dictate what subnet mask will also be given out as well. Once the relevant details have been filled in click on Next.
4. From this next section you can specify what addresses in the range need to be excluded for static IP addresses as well as how much delay is made before an offer is given. If you set the range correctly you should not need this feature. Once filled in accordingly you can click on Next to proceed
5. The next part is to setup the lease time. The lease dictates how long an IP address should be assigned to a client before it is taken away. Please note that if the client is online and is still using this lease then it will continue to keep the IP address. This feature is for when clients disconnect from the network and how long the server should wait before re-using an IP addresses again. For this example I am going to set it to 1 day.
6. Now we move onto the extended options for DHCP configurations. This includes dictating what the default gateway and DNS servers are. In my topology I do not have these set up however I will still walk you through the process. To continue select Yes, I want to configure these options now and then click on Next
7. To set the default gateway used to reach other networks you need to input the IP address and then click on the Add button. After the relevant addresses have been added simply click on Next
8. Now you need to setup what DNS servers are being used by client devices. If you are using Active Directory then this will be the IP address of your domain controller. Once the relevant IP address has been setup simply click Next
9. The next section is with regards to WINS. WINS is a legacy protocol that was designed to compete with DNS. Chances are very likely you do not have any WINS servers in your network and therefore you can simply click on Next to continue.
10. The final part of configuration is to activate the scope which will enable the service and allow it to service client devices. To complete this select the Yes and then click on Next. After this you can then click on Finish to complete the wizard.
VERIFICATION
To verify the first action I noticed was that PCA had been automatically assigned an IP address from a DHCP server within the range of addresses that we had configured. This can be clearly seen below.
Secondly when reviewing the given leases in the DHCP management console on the server we can see that a lease was handed out to PCA and therefore verifies that our configuration is working.
Hope this Helps,
Josh :smile9: