Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 438
  • Last Modified:

Retiring old DC - need to move master catalog?

I'm planning on retiring our old DC which is currently running Windows Server 2003 on out-dated proprietary hardware.  It is our main DC that was originally upgraded from NT.  I have another DC on modern hardware running Windows Server 2003 as well.

Before I retire the DC, I seem to remember that I should do the following:

-Move Global Catalog
-Transfer FSMO Roles

Is this correct?  Anything else?  Any tips on performing the above?

Thanks!
0
lauren_it
Asked:
lauren_it
  • 2
1 Solution
 
Jay_Jay70Commented:
can be done quite easily with a clean install of the new server

**Note - If introducing a 2003 R2 Server into the network as a DC you will need to run the ADPREP tools from the second cd

\CMPNENTS\R2\ADPREP

you can also download here
http://www.microsoft.com/downloads/details.aspx?familyid=5B73CF03-84DD-480F-98F9-526EC09E9BA8&displaylang=en

this boosts the schema up to cope with R2 functionality
http://www.microsoft.com/windowsserver2003/r2/whatsnewinr2.mspx

1) Promote your new machine as an additional domain controller in an already existing domain - this will allow AD to replicate to the new server
2) Make sure DNS is AD integrated on your old DC to allow all DNS replications also
3) Transfer the FSMO roles to the new server
http://www.petri.co.il/transferring_fsmo_roles.htm
http://support.microsoft.com/default.aspx?scid=kb;en-us;255690
4) Make the new DC a Global Catalog under Sites and Services
http://support.microsoft.com/?kbid=313994
5) Deactivate DHCP on the old DC (if used) and recreate the scope on the new DC, note if you have a fairly complex or Large DHCP scheme you may want to export and import the database
http://support.microsoft.com/kb/325473/
6) Run DCDIAG to make sure all is well and replication is fine
7) Demote the old DC if you dont intend to keep it as a backup
8) Recreate Shares etc on the new server
9) Reinstall printers and share them etc....


this will allow you to have the complete AD directory on the new DC and clients will barely be aware of any changes
0
 
lauren_itAuthor Commented:
Well, since the new server is already a Domain Controller(clean install), and DNS is AD integrated, and there are no shares or printers to move, that doesn't look too bad!  I'll transfer the FSMO roles and make the new DC a global catalog.  Thanks.
0
 
Jay_Jay70Commented:
no worries
0

Featured Post

Technology Partners: 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!

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