Migration from Windows 2000 to 2003 and replacment of old server to new.

I have a client that has an old Windows 2000 Enterprise Server that I'm going to be replacing with a new Microsoft Windows 2003 Enterprise Server and need help performing the migration on the PDC.  The server has Active Directory Services and files on it.  I'm concerned more with the migration of ADS because of all the groups and policies.  

I'm not sure the order or procedures for a new server including the migration process.  Do demote the existing server and promote the new server and run the Active Directory Migration tool on the new server?  What are the procedures?
mpatrynAsked:
Who is Participating?
 
Brian PiercePhotographerCommented:
The general procedure is:

Install Windows 2003 on the new machine

Assign the new computer an IP address and subnet mask on the existing network
Make sure that the preferred DNS server on new machine points to the existing DNS Server on the Domain (normally the existing domain controller)

Join the new machine to the existing domain as a member server

Inserth the 2003 CD in the 2000 machine and run adprep /forestprep and adprep /domainprep adprep is in the i386 folder on the CD  (If the new Windows 2003 server is the R2 version 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)

From the command line promote the new machine to a domain controller with the DCPROMO command from the command line Select Additional Domain Controller in an existing Domain

Once Active Directory is installed then to make the new machine a global catalog server, 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)

Make sure the new DC is also a DNS server, install DNS. 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, 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. Talking of which all the clients (and the domain controllers themselves) need to have their Preferred DNS server set to one domain controller, and the Alternate DNS to the other, 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 transfer the FSMO roles  - see http://www.petri.co.il/transferring_fsmo_roles.htm

You are now reasy to remove the old DC (or you can leave it running to provide resilliance)

If this is a domain controller then first make sure that you have:-

If the DC is running DHCP:  Install DHCP on the new DC, set up the scope and authorise it. remove DHCP from the old DC.

DNS: Make sure that all of your clients are set to use the new DC as their Preferred DNS server (either by static entries or DHCP options)

Power down to old DC and make sure that all is well, once satisfied power on the old DC again, then run DCPROMO for remove it's domain controller status. If you want to remove the machine from the domain then you can do so one it's DC role has been removed
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.

All Courses

From novice to tech pro — start learning today.