• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 317
  • Last Modified:

Best practice to replace DHCP DC?

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?
0
kxcrazy
Asked:
kxcrazy
  • 2
  • 2
1 Solution
 
Andres PeralesCommented:
Not certain why you would want to keep the same IP address?
You will need to load the new machine with windows 2003 server, then promote it to a domain controller for the existing domain, basically you are adding a new domain controller...then you can transfer over all the services to the new server.
then demote the old domain controller.
0
 
kxcrazyAuthor Commented:
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 :)
0
 
Andres PeralesCommented:
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
0
 
kxcrazyAuthor Commented:
Yeah it does...unfortunetly it was set up using IP.

No biggee.  Thanks for your input
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now