<div>
Only reason why would be to make it simplier in regards to the windows time service. &nbsp;All of the static IP addressed servers have the IP address of the exisitng DHCP server in their registry to pull the time service from. &nbsp;Would not be impossible to change all of them just thought it might be easier to keep same address.<br />
<br />
Call me lazy :)
</div>


Only reason why would be to make it simplier in regards to the windows time service.  All of the static IP addressed servers have the IP address of the exisitng DHCP server in their registry to pull the time service from.  Would not be impossible to change all of them just thought it might be easier to keep same address.

Call me lazy :)

<div>
lazy...<br />
Would the registry entry not allow you to use a dns entry instead of IP? &nbsp;That way you can change the ip address in dns next time<br />

</div>


lazy...
Would the registry entry not allow you to use a dns entry instead of IP?  That way you can change the ip address in dns next time


<div>
Yeah it does...unfortunetly it was set up using IP.<br />
<br />
No biggee. &nbsp;Thanks for your input
</div>


Yeah it does...unfortunetly it was set up using IP.

No biggee.  Thanks for your input

<div>
<div class="content wysiwyg-content">
The DHCP DC is up for replacement and I will be replacin it with a machine that will be running 2003 Server. &nbsp;The current DC is the primary and also serves as the windows time server.<br />
I would like to have the new machine assume the same static IP address if possible but the name can be anything different.<br />
<br />
What would be the best way to accomplish this?
</div>
</div>


The DHCP DC is up for replacement and I will be replacin it with a machine that will be running 2003 Server.  The current DC is the primary and also serves as the windows time server.
I would like to have the new machine assume the same static IP address if possible but the name can be anything different.

What would be the best way to accomplish this?

Best practice to replace DHCP DC?

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

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

DHCP

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.