Upgrading Windows 2000 DC to Windows 2003 on New Hardware (Also a file and print server)

I am currently in the process of Upgrading a Windows 2000 Domain Controller to Windows Server 2003 on new hardware.  This computer is also a file and print server.  I want to keep the domain controller the same name and I also want to transfer all of the file shares and printers housed on the current server to the new one without having to change any setting on the users' computers.  This is one of 3 domain controllers in this site.  Can someone help with instructions on whether what I want to do is possible.  Thanks.  
GDB IanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
Of course it's possible.  But why do you have 3 domain controllers at this site?  That's excessive, unless "this site" is serving 100,000 people.   Frankly, I recommend doing a SYSTEM STATE backup of ALL Domain Controllers before proceeding, then I'd demote the existing DC, properly moving FSMO masters it may hold off it first.  If necessary, move the GC and DNS and DHCP services off it as well and onto another server.  Finally, do a complete DATA backup of the old server.  Then restore that backup to the new server (DATA ONLY - NOT C: and NOT SYSTEM STATE).  Then rename the existing server something else.  Rename the new server to the old server's name and finally do a differential backup on the old server and restore it to the new server - this will be a QUICK backup as MOST of the data has been moved already and will end up having your system moved over with the smallest amount of down time.  If you REALLY want 3 DCs you can then DCPROMO the new system back up to a DC.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
To add to this, I found a great tool that will back up your print server (drivers, port definitions, printers, ACL, etc...): Print Migrator 3.0


This is a Microsoft tool that can backup and/or migrate your print server.  

As for the rest, here is what I do and this is just my $.02
-First, make your 3rd DC a Global Catalog server (see link below) and a primary DNS server and take it off of your network...just put it on a switch w/ no uplink.  Then, use this machine to seize your FSMO roles (see link below) for the domain...just DO NOT put this DC back in the domain when you are done.  It must be retired for good.  
-with the new DC acting as your FSMO role holder and serving its own DNS it can be upgraded to Server 2003.  This will upgrade your domain as well and give you a good idea of the issues that may pop up when you do this for real.  
-Once you have done a dry run, you can get ready to upgrade your domain for real.  
-Take a good backup of your actual FSMO holder, move DHCP off of it, make sure it is a GC server, and (one the weekend) upgrade it.  
-Now if this goes well do not upgrade your other 2000 DC.  Turn it off and leave it alone or, at least, take out its drives and mark them as "last 2000 dc"...just in case.  You can now take your 3rd DC and wipe it out.  Load Server 2003 on it and do a DCPromo to join it up.  Make it a GC, DNS, etc.  
-If you wish to have things really clean you can rebuild your original DC (the one we upgraded) so you have 100% pristine 2003 domain controllers...nothing upgraded.  

Thats how I did my NT --> 2000 domain migration and it worked like a charm (I changed the instructions to apply to 2000 --> 2003).  

How to create or move a Global Catalog in Windows 2000

Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

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.