Deploying DHCP: in This Chapter
Deploying DHCP: in This Chapter
Deploying DHCP: in This Chapter
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003
with SP1, Windows Server 2003 with SP2
In This Chapter
Overview of DHCP Deployment
Defining Scopes
Related Information
For more information about Dynamic Host Configuration Protocol (DHCP), see
the Networking Collection of the Windows Server 2003 Technical Reference (or
see the Networking Collection on the Web at http://www.microsoft.com/reskit).
For more information about integrating DHCP with Domain Name System
(DNS), see "Deploying Domain Name System (DNS)" in this book.
For more information about integrating DHCP with Windows Internet Name
Service (WINS), see "Deploying WINS" in this book.
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003
with SP1, Windows Server 2003 with SP2
Valid IP addresses and other network options must be configured for all computers and
other devices on the network, such as printers, in a corporate network. Manually
configuring this information is a time-consuming process that adds significant costs to an
organization and is susceptible to user error.
By using DHCP options, you can configure DHCP servers to supply a full range of
configuration values when assigning a DHCP lease, allowing you to configure a large
number of computers at one time, and to change configuration as necessary.
Different types of organizations can benefit from the automation and centralization that
Windows Server 2003 DHCP provides, including:
If you are deploying DHCP in a new Windows Server 2003 environment, begin your
deployment process by creating a design for your DHCP servers. When you have
completed all of the design steps for your DHCP infrastructure, you can implement your
DHCP solution by configuring your DHCP servers. If you are upgrading your existing
DHCP infrastructure to Windows Server 2003, begin by reviewing your current DHCP
design and modifying it if required, and then migrate your existing DHCP databases.
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003
with SP1, Windows Server 2003 with SP2
It is important to create a DHCP server design that meets the needs of your organization
in terms of functionality, availability, interoperability, and total cost of ownership (TCO).
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003
with SP1, Windows Server 2003 with SP2
If you use DHCP servers for Microsoft network clients, you must use a name resolution
service. Networks that support clients running Windows 2000, Microsoft®
Windows® XP Professional, and Windows Server 2003 use the DNS service to support
name resolution. Networks that support clients running versions of the operating system
earlier than Windows 2000 must use a form of NetBIOS name resolution, such as WINS.
Networks that support both types of clients must implement both WINS and DNS
servers.
Windows Server 2003 DHCP provides support for both DNS dynamic updates and secure
DNS dynamic updates. DHCP and DNS work together to perform dynamic updates and
work with Active Directory to perform secure DNS dynamic updates. DHCP also works
with Active Directory to prevent unauthorized DHCP servers from running on the
network.
Figure 2.6 shows the process for integrating DHCP with other services.
Defining Scopes
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003
with SP1, Windows Server 2003 with SP2
Before DHCP clients can use a DHCP server for dynamic TCP/IP configuration, you
must define and activate scopes for your DHCP clients. A scope is the full, consecutive
range of possible IP addresses for a subnet. The IP addresses in a scope define a single
subnet on which DHCP services are offered. DHCP servers use scopes to manage
network IP address distribution and the configuration of DHCP options.
Figure 2.7 Defining Scopes
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003
with SP1, Windows Server 2003 with SP2
After you have planned your DHCP solution and made the necessary configurations, you
must implement your new or updated DHCP solution in your production environment.
The DHCP implementation process involves the following steps:
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003
with SP1, Windows Server 2003 with SP2
These resources contain additional information and tools related to this chapter.
Related Information
The Networking Collection of the Windows Server 2003 Technical Reference (or
see the Networking Collection on the Web at http://www.microsoft.com/reskit)
for more information about Dynamic Host Configuration Protocol (DHCP).
Related Tools
DHCPExim tool
For more information about DHCPExim, see the Resource Kit Tools link on the
Web Resources page at http://www.microsoft.com/windows/reskits/webresources.
Netsh
For more information about Netsh, in Help and Support Center for Windows
Server 2003, click Tools, and then click Command-line reference A-Z.
"Checklist: Installing a DHCP server" in Help and Support Center for Windows
Server 2003.
"Checklist: Installing a DHCP Service resource" in Help and Support Center for
Windows Server 2003.
"Checklist: Installing a MADCAP server" in Help and Support Center for
Windows Server 2003.
"Cluster support for DHCP servers" in Help and Support Center for Windows
Server 2003.
"Configure the DHCP Relay Agent" in Help and Support Center for Windows
Server 2003.
"Netsh" and "Netsh commands for DHCP" in Help and Support Center for
Windows Server 2003.
"Add dynamic BOOTP client support to a scope" in Help and Support Center for
Windows Server 2003.
"Using Routing and Remote Access servers with DHCP" in Help and Support
Center for Windows Server 2003.