<div>
There is a minor security issue regarding dynamic registration in DNS when DHCP is running on DC. Check Windows 2003 Security Guide for details (<a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=8A2643C1-0685-4D89-B655-521EA6C7B4DB" rel="ugc">http://www.microsoft.com/downloads/details.aspx?FamilyId=8A2643C1-0685-4D89-B655-521EA6C7B4DB</a>).
</div>


There is a minor security issue regarding dynamic registration in DNS when DHCP is running on DC. Check Windows 2003 Security Guide for details (http://www.microsoft.com/downloads/details.aspx?FamilyId=8A2643C1-0685-4D89-B655-521EA6C7B4DB [http://www.microsoft.com/downloads/details.aspx?FamilyId=8A2643C1-0685-4D89-B655-521EA6C7B4DB]).

<div>
The only reason I wouldn't is if you had multiple non microsft dhcp servers that don't like having multple dhcp servers on the network segment.<br />
<br />
Some cheap routers that have dhcp turned on don't like seeing another dhcp server running.
</div>


The only reason I wouldn't is if you had multiple non microsft dhcp servers that don't like having multple dhcp servers on the network segment.

Some cheap routers that have dhcp turned on don't like seeing another dhcp server running.

<div>
<div class="content wysiwyg-content">
I'm about to decomission an old 2000 Member Server, and the only thing left running on it is the DHCP Server service for our network. &nbsp;I was wondering if I should add the DHCP role to one of my two 2003 DC's, or to one of my Member Servers....Or does it even matter? &nbsp;I would think that it would be best o put it on one of the DC's.....??? &nbsp;Thanks.
</div>
</div>


I'm about to decomission an old 2000 Member Server, and the only thing left running on it is the DHCP Server service for our network.  I was wondering if I should add the DHCP role to one of my two 2003 DC's, or to one of my Member Servers....Or does it even matter?  I would think that it would be best o put it on one of the DC's.....???  Thanks.

Any reason not o put DHCP services on one of my DCs?

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.

Network Architecture

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.