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

Renaming a Domain Controller with Windows 2003 Server

Ok, I am still new to the Server Admin side of things and have a quick question.

I was wondering how would you or do you approach the situation of replacing a current server with a newer server, but keeping the same server name.

My setup:
Server 1 (Current Server) : Windows 2003 Server Standard Edition - Domain Controller w/ DNS & DHCP services.

Server 2 (New Server to replace the current server) : Windows 2003 Server R2 Standard Edition

I was trying to figure out the best approach to building the new server (server2) while keeping the current server (server1) still online.  Should I name server2 something different, go through all the configuration setups and when ready take server1 offline and bring server2 online and rename it?

I am just not sure.

Any suggestions will be greatly appreciated.

Thanks for your time.

Bob
0
dgriffit55
Asked:
dgriffit55
  • 4
  • 4
  • 2
3 Solutions
 
smilerzCommented:
The solution with the least impact is to leave the name as server2 migrate all of the services (FSMO, DNS & DHCP) and call it a day.  The effort to rename the server probably isn't worth it.
0
 
dgriffit55Author Commented:
Well, there is one little catch.  I have about 50 - 60 client PC's that use shared folders on the server.  So, if I could keep the same server name that would be one less thing I would have to do on the client side.

I hope that makes sense.

Thanks.

Bob
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
Network_Data_SupportCommented:
i wouldnt suggest it tho
0
 
smilerzCommented:
Do you have other domain controllers in the environment?  If so, you can
DCPROMO the old server (making it not a domain controller anymore)
rename it.
Name the new server same as the old
DCPROMO it
move all of the data and services to the new computer.
I would avoid renaming the DC if you can.
0
 
Network_Data_SupportCommented:
dont think he has it looks like only one server going on his discription the best way would be bring up the second dc and transfer all roles to it and data , then via group policy map new drives to the new dc and then dcpromo the old
0
 
smilerzCommented:
Another option is to use a desktop as a temporary domain controller until all of the services have been migrated.
Just make sure you move all of the FSMO roles before demoting the old DC!
0
 
dgriffit55Author Commented:
I have several other DC's.  I am asking, because I have never done this before.  The guy who use to do this has left and now I need to figure this out.  I really do appreciate all the help you all continue to give me.

So, you are saying, if I have other DC's than I can just demote my lab server, of course making sure all my FSMO roles are off the DC before demoting than change the name and bring up the new server and promote it to a DC with the same name.  Then move all files / data over to it and presto.  Everything should be a smooth transition.  Right?

Thanks again.

Bob
0
 
smilerzCommented:
Change the name after demoting - but yes, that is drill.
0
 
Network_Data_SupportCommented:
yes i would demote the old dc to member server  and then rename it. rename the new member server and then dcpromo it
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

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