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 list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

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.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the