Need Advice, Migrating Windows 2000 Server to a new SBS2003 Server

[Sn@Ke]

Heya

I haven't done this before, so I want to be sure I'm attacking the problem correctly before I have a go at it.

Situation:
This site is operating on a Windows 2000 Server Domain, its only really using DHCP and some file shares.. The problem is, the server is an old P4 based system and the caps on the motherboard are starting to rise and its VERY old hardware (I lose sleep at night thinking about this thing blowing up).

The client also owns SBS2003 R2 SP2.. With enough user CALs to cover the whole site and some expansion. (They planned to upgrade the software awhile back but never bothered as they don't need the features)

What I've done so far:
Ordered a DELL PowerEdge T310 (I know its overkill, but it future-proofing and offers redundant PSU and hot-swap HDDs)
Got all the user CALs and Software ready to go.

Server arrived, I've installed SBS2003 but not finished the (continue setup) so effectively it's just 2003 Standard at the moment, this way I can join the current domain.

The plan:
From what I've read around the place and just my general understanding of servers, I plan on migrating all the old users to the new server by joining the New SBS2003 server to the current S2000 domain, then promote the new server to a Domain Controller.
Copy all the files and shares to the new server.
Demote the win2k server out of the domain.
Finish the SBS setup on win2k3 server.
Set up DHCP on win2k3 server.

I think that's it?... please let me know if I missed something or if you can give any detailed advice on the above.

Already have all hardware sorted out, got a raid 10 array with external backups being done daily and I'm adding in some UPS shortly as well.

I've also made an image of the current win2k server and backed everything up as well, just in case.


EDIT: Forgot to mention, I would be exporting the active directory from the old server to the new server, ofcourse.

 

[Sn@Ke]

Sorry for double post. I'm still working on this problem (I figure

Update on what I'm thinking:

Set up the new SBS 2k3 server in full, not joining to the old domain. Build it up from scratch then:
Use ADMT or CSVDE / whatever to move the AD users to the new Server
Robo copy / Copy all Data and Shares to new server (easy)
Connect all machines to the new Domain / Server
D/c old Server

Problem:
The old domain is NOT using Roaming profiles. I don't want to have to go to each PC on the network (20+) and have to copy their old Profile into the new one that would be created when they join the new domain.

Can all this be avoided if I join the new win2k3 server to the current win2k domain then somehow promote it to the main domain controller and d/c the old server from the domain? Thus leaving the current domain in tack and all local profiles correct?

 

[RobertH]

This may help

Please read:

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

If you do not have experince withtype of migration, seek assistance from somebody with experience.

A mistake in this process can have serious consequences to the existing network.

 

[onkyo]

Yes it can, if you leave the current server intact, join the sbs2003 system to the domain. before running SBS-Setup then depending on how you want things to end up and what not, you can then transfer all 5 FSMO roles over to the 2k3 system and make sure its the global catalog, then dcpromo out the old 2k system, rename it, then dcpromo it back into the domain. Then transfer all the roles back to it, make sure its now the global catalog, at this point you will then dcpromo the 2k3 system out of the domain, once it is a standalone server rename the server to the old name of the 2k system, dcpromo it back into the domain, transfer FSMO roles back over, make sure you make it a global catalog, then you can dcpromo the 2k system out of the domain, do a metadata cleanup to make sure AD does not have any references to the old server, if events look good, and there are no odd things going on. I would probably transfer data over, and continue SBS Setup. Been fortunate to have done this several times. Seems like a lot to do, but in the end it is worth it. You will end up with a Server, that has the origional name, Domain with the correct SID's, and Workstations that do not require being joined to a different domain.

This works well if you do not currently have exchange running.
I miss these types of jobs.
Good Luck, Its an easy job, but do make sure that before you run SBS-Setup that you remedy as many errors as you can.

Sorry for double post. I'm still working on this problem (I figure

Update on what I'm thinking:

Set up the new SBS 2k3 server in full, not joining to the old domain. Build it up from scratch then:
Use ADMT or CSVDE / whatever to move the AD users to the new Server
Robo copy / Copy all Data and Shares to new server (easy)
Connect all machines to the new Domain / Server
D/c old Server

Problem:
The old domain is NOT using Roaming profiles. I don't want to have to go to each PC on the network (20+) and have to copy their old Profile into the new one that would be created when they join the new domain.

Can all this be avoided if I join the new win2k3 server to the current win2k domain then somehow promote it to the main domain controller and d/c the old server from the domain? Thus leaving the current domain in tack and all local profiles correct?

 

[NorCal Internet]

Google "Swing Migration". You can also search the forums for it...We discussed it a little a week or two ago.

The previous posted basically describes a "Swing Migration", but if you Google it, you'll find a web site that offers very detailed, step-by-step instructions on how to do it. You'll have to buy the kit, but you'll make up the cost with one migration, or at least you should if you're pricing your service decently.

I've used this several times. I believe I bought the "Three Kit" version, which got me SBS2K to SBS2K3, 2K3 to 2k3, and 2K3 to 2K8 migrations. I've used them all several times since...Looks like he's got, or is working on some newer ones...

One thing that's nice is, you can swing onto your own hardware, leave the existing server in place, do your migration to the new hardware, then put the new server in place and only copy a few files over... This allows you to work with a copy of the existing server without fear of "Breaking" something, and you can complete most of the migration with very little downtime for the client...

 

[Tony_Scarpelli]

I don't know I think I would just assume set it up new and fresh with no migrations. Migrations are great for enterprises but for less than 25 users it seems about a break even deal in time.