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

upgrading vs migrating

Hi All,

we are planning to move our domain to w2k3 from w2k.

here is the setup like

one w2k domain server
one w2k3 exchange server

want to setup another w2k3 server and make it the domain controller.

i have already read alot of articles but still want to be 101% sure of what would be the correct path for success in this case will be and what can happen if not; also what would be the prime difference between migration and upgrading .

according to my thinking i would say the process should e something like this

no migration required, just add the new DC

1 Build new server
2 Running dcpromo on it to become a DC
3 Makeing sure that it is running a DNS
4 Changing the DNS entries to use this as primary DNS server (eg change the properties of your DHCP scope)
5 Moving all the FSMO roles to it and make it a GC (for exchange)
6. Turning off the old one for a while and test that everything works. & if it does, turn on the old DC, run dcpromo to make it a member only.

but but but... whatever i have read uptill now i only see the story of adperp untility running on OS 2000 . please help me out in this case as which method would be the correct one. thanks alot and thanks in advance

thanks alot and thanks in advance
0
lomaree
Asked:
lomaree
1 Solution
 
Jay_Jay70Commented:
Hi lomaree,

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

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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