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

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 .

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services.  The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database.  Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet.  Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS.  You may want to make sure the database is being backed up and also have a restore plan in place.  Should the database become corrupt, the application that uses that database will fail.  This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...