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

create a second domain controller and then make primary controller

I have a windows 2000 server.  Very old.  I just installed a 2012 server standard to the same domain.  I would like to activate windows active directory on the new controller but there are several AD roles to choose.  Which ones do I select to make it a domain controller.  Then after I am done, I would like to promote it as the primary controller to the domain.

How can I accomplish this?  Is this too big of a jump?
0
al4629740
Asked:
al4629740
  • 3
  • 2
  • 2
  • +1
6 Solutions
 
Nick RhodeIT DirectorCommented:
That is a pretty big jump.  AD function level has to be at least 2003.

http://social.technet.microsoft.com/Forums/windowsserver/en-US/22825611-af8e-48ca-bef7-98bb981b2f5a/migrate-a-windows-server-2000-to-2012?forum=winserverDS

How many systems do you have in your environment?
0
 
al4629740Author Commented:
Less than 20 pcs
0
 
Nick RhodeIT DirectorCommented:
With that small of an environment you could probably clean it up by just deploying a fresh environment with a new domain and join the systems to it if you wanted or needed to cleanup your infrastructure.  Otherwise my earlier link has some guides to upgrading and migrating.
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
Lee W, MVPTechnology and Business Process AdvisorCommented:
You cannot make the 2012 server a DC in your environment Until you get rid of the 2000 server as a DC and put a 2003 or later DC on the network.  (I'm not but I don't think you can jump to 2008 - I think you need 2003 or 2003 R2).  This means you need to:

1. install a 2003 Server, join it to the domain, promote it to be a domain controller.
2. transfer the FSMO roles to the 2003 server.
3. demote the 2000 server so that it is no longer a DC.
4. change the domain and forest functional levels of AD.
5. install the 2012 server and join it to the domain
6. promote the 2012 server to a DC
7. transfer the FSMO roles to the 2012 server
8. demote the 2003 server
9. remove the 2003 server from the domain
10. transfer the remaining services and features of the 2000 server to the 2012 server.  (You may have to adjust some SMB protocol settings to allow the 2000 server to talk to the 2012 server).

If you've never done this and aren't expecting to make this your day job (doing such migrations), I HIGHLY recommend you hire a consultant with experience to do this transition for you.  It will go much faster and much smoother and though you'll potentially have to cut a higher check, the costs in terms of lost productivity and potential issues in the future will almost certainly be less.

Finally, VIRTUALIZE - 2012 makes this easy and virtualization, while adding a small layer of complexity, adds a HUGE layer of flexibility!  (And Hyper-V in 2012 is FREE!)
0
 
al4629740Author Commented:
In a nutshell what is hyper V?
0
 
Seth SimmonsSr. Systems AdministratorCommented:
hyper-v is microsoft's hypervisor for creating and running virtual machines; competitor to VMware

and yes, you can install a 2008 R2 server and make it a domain controller to migrate the 2000 server to.  the 2003 limit is the domain/forest functional level which is required for a 2012 domain controller which you can't achieve until the 2000 server is gone.  a 2008 R2 server can work in a 2000 native functional mode

http://technet.microsoft.com/en-us/library/understanding-active-directory-functional-levels%28v=ws.10%29.aspx

you can migrate to that first, raise the forest/domain functional level to 2003, 2008 or 2008 R2 then put in your 2012 domain controller
0
 
al4629740Author Commented:
What if I just take rhodes suggestion and just migrate all the computers onto a new domain?
0
 
Seth SimmonsSr. Systems AdministratorCommented:
that's up to you; you can go that route especially with a small number of machines like this and if purchasing 2008 R2 isn't an option

you would also have to create the user accounts again and work on migrating that since user objects won't have the same SID - just keep that in mind also.  with that many client machines it shouldn't be too bad
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
>  with that many client machines it shouldn't be too bad
I disagree - the last time I did a domain of 15 users from scratch it took 5 days to settle everything down.  Doing a migration - if you know what you're doing, should take about 1-2 days depending on how well patched your servers are and how fast your systems and internet connection are.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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