Module 8 Dynamic Host Configuration Protocol
Module 8 Dynamic Host Configuration Protocol
and Maintenance
Module 8
Dynamic Host
Configuration Protocol
• To Provides information about changes in functionality for DHCP in
Windows Server 2012 R2.
• To know the information about changes in functionality for DHCP in
Windows Server 2012.
• To Understand and Deploy DHCP Failover: Provides detailed
information about a new option for DHCP high availability in
Windows Server 2012.
• To enumerate diagnostics tools and procedures in monitoring and
troubleshooting DHCP server and DHCP client services in Windows
Server
• To enumerate DHCP Server Operational Events
• To enumerate DHCP console icons
Overview
8.1
Windows PowerShell for DHCP Improved New Windows PowerShell cmdlets are available.
server
• DHCP policies have been extended to allow users to configure conditions based on the fully
qualified domain name (FQDN) of clients.
• DHCP policies can also be configured to register DHCP clients using a specific DNS suffix, overriding
the DNS suffix that is configured on the client.
• Using suitable FQDN-based conditions and a DNS suffix, DHCP policies can be configured to enable
full control of DNS registration for computers and devices on the network, including workgroup
computers and guest devices, or clients with a specific attribute.
• This feature enables you to configure a DHCP server to register only address (A) resource records of
DHCP clients with the DNS server.
• This can be helpful when a reverse lookup zone has not been configured, causing attempts to register
pointer (PTR) resource records to fail. By disabling PTR registration, DHCP servers can be prevented
from repeated failed attempts to register PTR records. PTR registration can be disabled for all clients
of a DHCP server, or only for clients on a specified subnet or with a specified attribute.
• Previously, it was possible to disable DNS registration for a specified group of DHCP clients. However,
it was necessary to disable both A and PTR registration.
• New Windows PowerShell cmdlets are available in Windows Server 2012 R2. You can use
these cmdlets to perform tasks such as creating DHCP security groups, setting DNS
credentials, managing superscopes, and managing multicast scopes.
• Improvements have also been made in existing Windows PowerShell cmdlets for DHCP
server to help perform tasks such as changing the mode of a failover relationship and
configuring DNS settings for a DHCP policy.
Cmdlet name New or improved Description
Add-DhcpServerSecurityGroup New Adds security groups to a DHCP server.
Add- New Adds a range of addresses to exclude from a multicast
DhcpServerv4MulticastExclusionRan scope.
ge
Add-DhcpServerv4MulticastScope New Adds a multicast scope on the DHCP server.
Add-DhcpServerv4Policy Improved Adds a new policy either at the server level or at the
scope level.
This cmdlet can now be used to specify lease duration
and also add FQDN-based policies.
Get-DhcpServerDnsCredential New Gets an account that the DHCP Server service uses to
register or deregister client records on a DNS server.
Get-DhcpServerv4DnsSetting Improved This cmdlet can now be used to display DNS settings
of DHCP policies.
Cmdlet name New or improved Description
Get- New Retrieves the exclusion range for a specified multicast
DhcpServerv4MulticastExclusionRa scope.
nge
Get-DhcpServerv4MulticastLease New Retrieves multicast leases for a specified scope name.
Remove-DhcpServerDnsCredential New Removes the credential that the DHCP Server service
uses to register or deregister client records on a DNS
server.
Cmdlet name New or improved Description
Remove- New Removes a range of addresses previously excluded
DhcpServerv4MulticastExclusionRa from a multicast scope.
nge
Remove- New Removes one or more multicast scope leases for a
DhcpServerv4MulticastLease specified multicast scope or IP address.
Remove- New Removes multicast scopes.
DhcpServerv4MulticastScope
Rename-DhcpServerv4Superscope New Renames a superscope.
Set-DhcpServerDnsCredential New Sets credentials that the DHCP Server service uses to
register or deregister client records on a DNS server.
Cmdlet name New or improved Description
Set-DhcpServerv4DnsSetting Improved Configures how the Dynamic Host Configuration
Protocol (DHCP) server service updates the DNS
server with the client-related information.
Ths cmdlet can now be used to set the DNS settings of
policies.
Set-DhcpServerv4Failover Improved Modifies the attributes of an existing failover
relationship.
This cmdlet can now be used to change the mode of a
failover relationship.
Set-DhcpServerv4MulticastScope New Modifies the properties of a multicast scope.
Set-DhcpServerv4Policy Improved Sets the properties of an existing policy either at the
server level or at the specified scope level.
This cmdlet can now be used to set lease duration of
a policy and also modify FQDN-based policies.
What’s new in DHCP in Windows Server 2012
In Windows Server 2012, DHCP offers enhanced support in the following areas:
•DHCP failover
•Policy-based assignment
•Windows PowerShell for DHCP Server
• This feature provides the ability to have two DHCP servers serve IP addresses and option
configuration to the same subnet or scope, providing for continuous availability of DHCP service to
clients.
• The two DHCP servers replicate lease information between them, allowing one server to assume
responsibility for servicing of clients for the entire subnet when the other server is unavailable.
• Policies applicable at a scope can be configured at the scope or inherited from server wide policies. A
single client request can match multiple policies, and policies can be associated with multiple address
ranges.
• Windows Server 2012 provides task-oriented Windows PowerShell cmdlets for DHCP server
management.
• The DHCP server configuration operations are implemented in Windows Server 2012 as Common
Information Model (CIM) based cmdlets.
• Windows PowerShell uses object pipelining to eliminate the need for parsing and manipulation of
text output.
• Windows PowerShell for DHCP Server includes 103 cmdlets, covering multiple aspects of DHCP
server configuration and management.
Understand and Deploy DHCP
Failover
8.2
• With DHCP failover, two DHCP servers share DHCP scope and lease information, enabling one server
to provide DHCP leases to DHCP clients if the other server is unavailable.
In Windows Server® 2008 R2 and previous operating systems, two high availability options
are available for DHCP server deployment:
•DHCP in a Windows failover cluster. This option places a DHCP server in a cluster with
another DHCP server that assumes the load if the primary DHCP server fails. The clustering
deployment option uses a single shared storage. The storage unit is a single point of failure,
and requires an additional investment to achieve redundancy. Clustering can be relatively
complex to configure and maintain.
•Split scope DHCP. Split scope DHCP uses two independent DHCP servers that share
responsibility for a scope. Typically, 70% of the addresses in the scope are assigned to the
primary server and the remaining 30% are assigned to a backup server. If clients cannot
reach the primary server then they can acquire an IP address lease from the secondary
server. Split scope deployment does not provide IP address continuity and is unusable in
scenarios where the DHCP scope is already running with high address space utilization, a
common scenario for IPv4 addressing.
In Windows Server® 2012 and later operating systems, a new DHCP high availability option is also
available:
•DHCP failover. DHCP failover provides redundancy and load balancing for DHCP services, enabling
administrators to deploy a highly resilient DHCP service. With DHCP failover, Internet Protocol version
4 (IPv4) scopes with associated leases, reservations, options, and settings, are shared by two Windows
DHCP servers. DHCP failover supports large scale DHCP deployments without the challenges of split
scope and clustered DHCP.
•Benefits of DHCP failover include:
• Simple: A wizard is provided to create DHCP failover relationships between DHCP servers. The
wizard automatically replicates scopes and settings from the primary server to the failover
partner.
• Flexible: DHCP failover can be configured to provide redundancy in hot standby mode, or with
load balancing mode, client requests can be distributed between two DHCP servers.
• Seamless: DHCP servers share lease information, allowing one server to assume responsibility
for servicing of clients if the other server is unavailable. DHCP clients can keep the same IP
address when a lease is renewed, even if the lease is issued by a different DHCP server.
• Muti-site: DHCP failover supports a deployment architecture that includes multiple sites. DHCP
failover partner servers do not need to be located at the same physical site.
Applies To: Windows Server 2012 R2, Windows Server 2012
• DHCP failover in Windows Server® 2012 is a new feature that enables two Microsoft
DHCP servers to share service availability information with each other, providing DHCP
high availability. DHCP failover works by replicating IP address leases and settings in one
or more DHCP scopes from a primary DHCP server to a failover partner server.
• All scope information is shared between the two DHCP servers, including active leases. This
enables either DHCP server to assume responsibility for DHCP clients if the other server
becomes unavailable.
The following tables summarize Windows DHCP Server events. Events are displayed in tables
based on their channel.
•DHCP Server Operational Events
•DHCP Server Administrative Events
•DHCP Server System Events
•DHCP Server Filter Notification Events
•DHCP Server Audit Events