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

Change out a Primary Domain Controller with a new server

We have a Windows domain network with 10 servers.  All servers are running Windows 2003 standard.  We have a primary domain controller and a backup domain controller.  Our primary domain controller is 8 years old and we are planning to take it offline and replace it with another server.  The new PDC will have Windows 2008 standard.  We need some type of procedure to remove the current PDC and slip the new one in.  Active directory and global policies are the primary concern and need to be somehow brought over to the new server.  Data backup is not a problem as we will use our normal backup procedure to handle that task.  

We have over 100 users on the network and cannot setup new profiles on each end user workstation.  How can we put in a new domain controller and have it be recognizable to all the PCs on the network?  We do plan to keep the local domain name the same and the server name will be identical to the one it is replacing.  Aside from those obvious things, what else needs to be done.  

Thank you.
0
PCNNY
Asked:
PCNNY
3 Solutions
 
Mike KlineCommented:
Take a look at this question I helped with

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_26358376.html

A lot of information and good links.  Let me know what questions you have after going through that

You won' t need to setup new profiles

I would suggest that you use 2008 R2 at this point (if you can)

thanks

Mike
0
 
Darius GhassemCommented:
0
 
Renato Montenegro RusticiIT SpecialistCommented:
There are some misconceptions here. There is no PDC/BDC since Windows NT. Active Directory is fully replicated among all of your domain controllers.

What you have are some special roles that can reside in a domain controller. To check out where they are, make sure the Windows 2003 Support Tools are installed and type this command:

netdom query fsmo

Then:

1) Extend your schema to Windows 2008
2) DC promo your new server. At this point, your users will access your new server. There's no need to do anything else.
3) Adjust your DNS servers configuration on the client computers, if needed.
4) Transfer the roles to the new server: http://support.microsoft.com/kb/255504
5) Shut down your old server(s) and evaluate the environment
5) Decommission your old server(s). DC promo them.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Mike KlineCommented:
...well fully replicated unless we are talking about RODC's

You would also want to install DNS on the new box and make it a global catalog.  All explained in the links Darius and I provided.

Thanks

Mike
0
 
Renato Montenegro RusticiIT SpecialistCommented:
If I understood well, he will replace the domain controller. It wont be a RODC. But I forgot to mention the Global Catalog. Thanks.
0
 
PCNNYAuthor Commented:
Thank you.  Great info
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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