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

2000 to 2003 DC

Hi Folks,I need to replace my windows 2000 DC with windows 2003 DC on a new piece of  hardware.I know the steps to do that but need to KEEP the same IP address & Server name as the old 2000 DC.If someone could please guide me to do that.

Thanks
0
Musafeer79
Asked:
Musafeer79
  • 3
  • 2
  • 2
  • +1
1 Solution
 
snusgubbenCommented:
Make the 2003 server an additional DC with a temp name and IP.

Dcpromo the 2000 DC out.

*Rename the 2003 DC: http://www.petri.co.il/windows_2003_domain_controller_rename.htm

*This is not a recomended task to do, so I would see if there was any option to berry the old DC name because there might be traces of it in the domain even after you dcpromo the 2000 DC.


SG
0
 
snusgubbenCommented:
0
 
zelron22Commented:
Why does it have to have the same name?  Is this something that could be handled with a CNAME in DNS?  
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
AmericomCommented:
If you have to change the domain controller back to the old one later on, just make sure the old DC is completely and successfully removed from AD, DNS, and WINS if there is one. Not sure if the new Windows Server 2003 DC is the only one DC. If so, it would be better if you have a good backup first, even better if you have two or more DCs. If you already have multiple DCs and also with AD site created, then you also need to remove the old DC name from the AD site and services console under Servers. If not, no worry.

In these days, application shouldn't rely on IP address and servername. If you have the dependecy of IP and servername, it would be just some script and those scripts should probably be written in a way where you can adjust it much easier than renaming a domain controller.  Script or application should not rely on IP address, if it does, it's more of a defected configuration. If firewall rule restricted for certain IP, it should be still relative easier to adjust than forcing to reuse the IP and servername. If your IP at one point will be merge with another sister company, you will not be able to reuse the same IP. Same thing as naming convention, one of these days your namename may also need to be changed. So, IP and Servername should be able to change without any concern. If that's the case, why waste time to change your IP and servername back.
0
 
Musafeer79Author Commented:
Thanks guys,I don't think i will change the IP & Server name.
I'm also running exchange 2003 on the same network ,will exchnsge configuration be affected with the dc being 2003.Pls let me know.
0
 
snusgubbenCommented:
Should not be a problem.

I guess you know the adprep you need to run before your allowed to add a 2003 DC in your domain.


SG
0
 
Musafeer79Author Commented:
Thanks SG ,will do this tomorrow night  confirm success.Chrz
0
 
zelron22Commented:
If Exchange is installed on a DC, do NOT demote the DC, or Exchange will break.  If Exchange is installed on a member server, do NOT promote the server to a DC, or Exchange will break.  :)

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

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