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

Need to replace a Windows 2000 Domain Controller with a Windows 2003 Standard Server that is currently a member of the domain. What steps do I need to take?

My Current setup is Windows 2000 server (Primary Domain Controller),  Windows 2000 Terminal Server (Backup Domain Controller), and a Windows 2003 Standard server that has been joined to the domain and has some data shares on it.  

I need to have the Windows 2003 server become the new domain controller and phase out the current Windows 2000 Primary Domain controller.  Can someone give me a step by step on how to do this?  I've found here something about moving FSMO roles?  Also, currently Active Directory is not installed on the 2003 server so I know that will need to happen at some point as well during this process.  

Is this typically a pretty easy thing to do?  It seems like it should be, but I'm trying to find out what I'm getting into before I get there!  :)

Thank You for all of your help!

0
bscott13
Asked:
bscott13
  • 4
  • 3
2 Solutions
 
Alan Huseyin KayahanCommented:
           Hi bscott13
                 First, you should prepare the active directory for 2003 structure/schema. Follow the article
http://www.petri.co.il/windows_2003_adprep.htm
                Then promote the new 2003 to an additional domain controller by Start>Run>dcpromo.  
                Then transfer FSMO roles to new server
http://www.petri.co.il/transferring_fsmo_roles.htm

Regards
0
 
bscott13Author Commented:
Do i run the "ADPrep /forestprep"  and "ADPrep /domainprep"  from the current Windows 2000 PDC or will this be run on the Windows 2003 server?  Also, the 2003 server is a member of the domain but does not have Active Directory installed.  At what point will I need to do this and will there be any special options I need to choose?

Thanks!
0
 
KCTSCommented:
You need to run ADPrep from the Windows 2003 CD on the Windows 2000 DC. This will extend the Win2003 AD Schema - ADprep is in the i386 folder on the Windows 2003 CD. Note if this is Win2003 R2 which comes with 2 CDs  then you need to run Adprep  from CD2 of the R2 disks on the existing Domain controller. Adprep is in the \CMPNENTS\R2\ folder on CD2.

Once this has been done then youy can run DCPROMO on the 2003 machine to make it a domain controller. You will then need to make it a global Catalog server so go to Administrative Tools, Active Directory Sites and Services, Expand ,Sites, Default first site and Servers. Right click on the new server and select properties and tick the Global Catalog checkbox. (Global catalog is essential for logon as it needs to be queried to establish Universal Group Membership)

Assuming that you were using Active Directory Integrated DNS on the first Domain Controller, DNS will have replicated to the new domain controller along with Active Directory.

If you are using DHCP you should spread this across the domain controllers for now. In a simple single domain this is easiest done by Setting up DHCP on the second Domain controller and using a scope on the same network that does not overlap with the existing scope on the other Domain Controller. Dont forget to set the default gateway (router) and DNS Servers.

For now, all the clients (and the domain controllers themselves) need to have their Preferred DNS server set to one domain controller (the new one), and the Alternate DNS to the other (the old one), that way if one of the DNS Servers fails, the clients will automatically use the other.

Both Domain Controllers by this point will have Active Directory, Global Catalog, DNS and DHCP.
You now need to move the FSMO roles (including the PDC emulator from the old machine to the new machine.  You should cleanly transfer the FSMO roles. This can be done in different ways see http://support.microsoft.com/kb/255504 or http://support.microsoft.com/kb/324801 or http://www.petri.co.il/transferring_fsmo_roles.htm for alternatives methods that can be used.

You should now test that all is OK by disconnecting the old DC (just unplug the network cable). The domain should continue to function, if not then troubleshoot. Reconnect the old Domain Controller when you are satisfied all is OK.

Once you are sure that all is OK then you can either leave both Domain controllers operational, (two domain controllers are normally recommended for fault tolerance)

If you really want to get rid of the old Domain controller then:

You should make sure that all the clients are using the new Domain Controller as their preferred DNS Server - and the Alternate DNS server either points to an alternative domain controller or is blank.

Run DCPROMO on the old DC to demote it back to a member server, and then remove it from the domain.
Reconfigure the DHCP scope if required.

0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
bscott13Author Commented:
Thank you very much KCTS for the in depth explanation.  That's exactly the type of explanation I was looking for.

 My only question is when do i need to install Active Directory on the Windows 2003 server?  It is currently just a file server on the domain.  I would assume i need to install AD right away on the 2003 server.  Is there any special options I need to look out for when doing the AD install?  It's been awhile since i've done an AD install but I do remember it asking things such as member of a new forest, etc.  Which should I choose?

0
 
Alan Huseyin KayahanCommented:
            After adprep on 2000 DC is completed, you can start installing active directory on new 2003 server.
               *Start>run>dcpromo
                    Follow the instructions and choose additional domain controller. After restart, your 2003 server is a DC with AD installed
                     Then follow the instructions I posted (in petri) for making your new server the PDC (transferrings FSMOs)

Regards
0
 
bscott13Author Commented:
Thanks MrHusy for your input as well.  I appreciate the input that both of you provided.

I'll be doing this cut over tomorrow night.  Any idea how long this would typically take?  Couple hours for the AD prep, setup, and move?



0
 
Alan Huseyin KayahanCommented:
           Hi bscott13
                 It shouldnt last longer than 1 hour if no problems/coincidences encountered

Regards
0
 
bscott13Author Commented:
I forgot to ask, do I need to run the domain and forest prep on the terminal server as well or will it propogate over the network after running it on the primary domain controller?

Thanks!
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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