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

Domain Controller

Afternoon All

We Had two WIN2003 DC's however 1 died of death over a year ago, and I need to get another one in place.

I have a Spare Windows 2012 Server that I can Use, can anybody talk me through adding this as a DC, and does anything need to be done to remove the old one from the system, I Believe the one that still works has all the roles etc installed on it but I am unsure of how to check this

John
0
pepps11976
Asked:
pepps11976
  • 2
1 Solution
 
Spyder2010Commented:
the command:

netdom -query fsmo

run from a command prompt will show you who holds the FSMO roles.  To add a Server 2012 Domain Controller, the server needs to be part of the domain, and you would add Active Directory Domain Services to it through the Server Manager -> roles.  There are a lot of things to take into consideration here though... forest/domain functional level, how the old DC died, and the proper steps to remove it.

Procedure to remove an orphaned domain controller:
http://msmvps.com/blogs/acefekay/archive/2010/10/05/complete-step-by-step-to-remove-an-orphaned-domain-controller.aspx

Here's a TechNet blog article going through the steps to add a 2012 DC to a 2003 domain:
http://blogs.technet.com/b/canitpro/archive/2013/05/05/step-by-step-adding-a-windows-server-2012-domain-controller-to-an-existing-windows-2003-network.aspx

Sorry for just pasting links, but the steps for each procedure are lengthy, and you really should do some pretty in-depth reading and consider requirements/prerequisites/etc... before proceeding with this.  Best of luck!
0
 
pepps11976Author Commented:
Ok The Current Working Server Seems to hold all of the Roles, so that's good?

When you say Be Carefull I just thought this would be a standard simple thing?

John
0
 
Spyder2010Commented:
the fact that the working server does hold all the FSMO roles is a good thing:)

Adding a new domain controller is not difficult, just follow the procedure that I linked you to... the reason I said be careful is that if you want your domain to perform certain functions(DNS, Global Catalog) or if you have a large domain spanning WAN links... it is much easier to plan out your strategy before you start installing, rather than installing it, then having to go back and change it later.

If the domain still sees the old domain controller, you will need to remove that to ensure that replication is consistant... this is not a trivial task... not difficult per say, but you really need to follow all the steps in the article.  1+ year for a domain controller being unable to talk to the domain is a very long time.  You want to make sure you get it out of the domain(follow the article I linked), and once out, you want to wipe the hard drive and rebuild it.  The last thing you want is that DC coming back online and trying to replicate with other DCs... the dead one doesn't know anything about all the changes that have happened for the year+ it was offline.

If you have a smaller domain that you just use for authentication, this isn't such a big deal... but depending on the size and geographical diversity of your domain and sites, this could be a big undertaking.
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

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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