Best Practices Analyzer for Dynamic Host Configuration Protocol

Applies To: Windows Server 2008 R2

In Windows management, best practices are guidelines that are considered the ideal way, under normal circumstances, to configure a server as defined by experts. While best practice violations, even critical ones, are not necessarily problematic, they indicate server configurations that can result in poor performance, poor reliability, unexpected conflicts, increased security risks, or other potential problems.

Topics in this section can help you bring DHCP running on Windows Server® 2008 R2 into compliance with best practices. Content in this section is most valuable to administrators who have completed a Best Practices Analyzer scan of DHCP, and who want information about how to interpret and resolve scan results that identify areas of DHCP that are noncompliant with best practices.

For more information about Best Practices Analyzer and scans, see Best Practices Analyzer.

More information about DHCP

DHCP in Windows Server 2008 R2 provides technologies that reduce the administration burden and complexity of configuring hosts on a Transmission Control Protocol/Internet Protocol (TCP/IP)-based network, such as an intranet.   By using DHCP server computers to centrally manage IP addresses and other related configuration parameters, using DHCP client computers to request and accept TCP/IP configuration information from DHCP servers, and using DHCP relay agents to pass information between DHCP clients and servers, the process of configuring TCP/IP on DHCP clients is automatic.

For more information about DHCP, see the DHCP page on the Windows Server 2008 TechCenter at https://go.microsoft.com/fwlink/?Linkid=.

See Also

Concepts

Best Practices Analyzer for Dynamic Host Configuration Protocol: Prerequisites
Best Practices Analyzer for Dynamic Host Configuration Protocol: Configuration
Best Practices Analyzer for Dynamic Host Configuration Protocol: Operation
Best Practices Analyzer for Dynamic Host Configuration Protocol: Security