[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 180
  • Last Modified:

Replacing a 2000 AD/DNS server with 2003 server and keep same name.

Would like to replace the 2000 server (srv1)which is a GC/AD/FSMO and Dns (active directory intergrated as well as other domains) server. We also have one other 2003 server(srv2) which is a GC, I understand the need to dcpromo and make the new one a GC,  but have questions:
1. Would like to rename the new server(srv3) to the same as srv1 because that hardware is going away and because of dns, is that a problem?
2. Can I transfer the FSMO roles to the new server before the name change? Thank You.
0
raindave
Asked:
raindave
  • 3
  • 2
  • 2
1 Solution
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
So you already have a 2003 Domain Controller, right?  

1. Transfer the FSMO, DNS, GC, etc to the existing 2003 DC.  
2. Then demote the old 2000 server.  
3. Then remove it from the network and reset the computer account in Active Directory Users and Computers.
4. Then rename the new server to the old server's name.
5. Then add the new server to the network.
6. Then run DCPROMO and Make it a domain controller.  
7. Then transfer the services you want it to run back to it.
0
 
raindaveAuthor Commented:
Yes I have a existing 2003 DC(srv2), the new server(srv3) is already a member server. Should I drop it out of the domain then?
0
 
NJComputerNetworksCommented:
In case there are left over symptoms of the old DC being in your AD environment still, you can use this procedure to verify that the server has been removed:  http://www.petri.co.il/delete_failed_dcs_from_ad.htm

After you validate, you can coninue with adding the new server as a domain controller.

0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
Lee W, MVPTechnology and Business Process AdvisorCommented:
NJ... No DC has failed.  If he runs DCPROMO and removes it properly, this should be entirely unnecessary.

I would remove the 3rd system from the domain and rename it outside the domain - it may work just fine renaming if from within the domain, but I this is what *I* would do.  And ONLY rename it after you have properly removed the old server1
0
 
NJComputerNetworksCommented:
Leew your right...  You don't "have" to do this.  However, if your environment is not working properly (say DNS is pointed wrong) and you have trouble with the DCPROMO, you may refer to the document to manually remove the DC (or check the verify that the DC has been removed from AD.)

Sorry to confuse you, my post was only included as additional information.
0
 
raindaveAuthor Commented:
When we do the dcpromo, will it automatically get the Active Directory intergrated zone?
0
 
NJComputerNetworksCommented:
yes
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

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