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.

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.

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.

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.

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.

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.

Comments

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix. This customization deals with Group Policy and PowerShell. For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material. I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO. This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy. One organization in the crowd had over 5,000 Group Policies. In an environment like that, the comment section can be priceless. I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2 # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2 #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers. The first command creates a collection with 2 duplicates of both 1 and 2. The second command creates another collection with the duplicates filtered out. The Compare-Object cmdlet will first find items that are diffe

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.

Jason Yoder, MCT

Search This Blog