Looking for Easiest Way to Copy Users from 2000 Server to Server 2003 2

[1010Tim]

I would hate to think that I'll have to recreate every user account manually when I configure a Server 2003 in a couple months. The thing is I'll be using the same Dell 4400 for 2003 that I am using for 2000. So I guess I will have to store the user accounts and their folders somewhere.

I would like to do a clean install.

What would you recommend? Thank you.

 

[Roadki11]

The best way would be to get a new server and make it an AD server in the 2k domin, transfer the FSMO roles and GC to the new server then demote the old 2k server or better yet leave it alone and keep it as 2nd DC. BUT if you just have to use the old hardware for your new 2k3 server then i would do an implace upgrade but you said you dont want to do that, not sure why. So the next best way would be to find some crappy pc that isnt being used for anything and install 2k or 2k3 server on it and make it an AD server in the domain, then move the FSMO roles and GC to that server then demote and remove the Dell 4400. Install your new 2k3 server on the 4400 and make it an AD server then move the FSMO roles and GC to the 4400 and demote and remove the temp AD server. Make sense?

RoadKi11

 

[LWComputingMVP]

There are reasons why an upgrade may not be appropriate, but in general, in my experience, they work fine in the vast majority of cases (pending of course, on how much disk space you have available).

An alternative to what has been suggested (and no real problem I might add) - setup a VIRTUAL DC as a second DC in your existing domain... then demote the current DC (so you don't have an orphaned DC in your AD). Then copy the virtual machine hard drive to a DVD or something that won't be erased, and wipe and reinstall 2003 (NOT as a DC; use a static IP). Once 2003 is up, boot up your virtual machine and join the 2003 system to the domain. NOW make it a DC. Then demote the virtual DC and get rid of it.

Don't forget to do the usual suspects - Move FSMO roles, create GC, ALLOW TIME FOR PROPER REPLICATION and check event logs at ALL STEPS. Also, MAke sure you make MANY SYSTEM STATE BACKUPS! I would do one before every step involving Active directory - Before the VM DC is created, After it's created, after the FSMO roles are moved, after the old DC is demoted, before the new server is joined to the domain, etc. System State backups are quick to do (usually 2-5 minutes) so this won't cause too much of a delay and if something goes wrong you'll be VERY happy you did.

 

[1010Tim]

Thanks a bunch. I have gleaned from both your comments that an upgrade is the way to go. That should make it much faster and easier. I was just not sure how reliable it would be. Now I am not worried.

Do I merely drop in the CD and kick it off? Or is there another step or two before hand?

I really appreciate the insight and help.

 

[nevets2001uk]

While the upgrade should work OK it would be worth taking the time to ensure you have a current and reliable backup of the DC you will be upgrading before you proceed.



Steve G (MCSE / MCSA:Messaging)

 

[Roadki11]

nevets is right, before you do anything make sure you have backups, multiple backups. I would make sure i have some sort of bit level backup like a ghost image of the server. Then make sure the server is all patched up, all service packs and updates are applied. Of course this will need to be done after hours as it will affect user access to resources.

This is worth the read also:

http://support.microsoft.com/kb/325379

RoadKi11

 

[ductTape]

Definately have a verified good backup before doing the in place upgrade. I would personally create an image, then perform all updates, create another image, then do in place upgrade. Ofcourse I do prefer a clean install whenever it is possible.