Skip to main content

Configuring Split-Scope DHCP

Split-Scope DHCP allows you to have a redundant DHCP system on your network.  To achieve this in past implementations of Windows Server, we would allocate 80% of our address to one DHCP server and 20% to another.  This was referred to as the 80/20 rule. 

To begin, you need to have the DHCP role installed on the two servers that will participate in the split.  On one server have the scope completely configured that you want to split.

Open the DHCP console.

Right click the scope that you want to split and then click Advanced –> Split-Scope.
image
On the DHCP Split-Scope page, click Next.

On the Additional DHCP Server window, enter the name of the second DHCP server and click Next.
image
In the Percentage of Split screen, adjust the slider bar to set a percentage from the number of IP addresses that will be available on each server.  Click Next to continue.
image
In the Delay in DHCP Offer screen, provide a response delay for the secondary server.  This ensures that the primary DHCP has a chance to send an offer to the client before the secondary server springs into action.
image

At the Summary of Split-Scope Configuration screen, click Finish and then Close.

Log into the secondary DHCP server and open the DHCP console.

Select the scope. Right click the scope and click Activate.
image

Your split scope DHCP is now configured and online.

By checking the properties of the secondary DHCP server’s scope, you will see the subnet delay that you configured in the Split Scope wizard.
image

Comments

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .