SBS migration from 2000 to 2003

[sieistganzfett]

My understanding of this is config the newserver, servername and domain must be different (SBS 2003). Then when you are going to connect the 2003 SBS to the existing network, dhcp has to be disabled on the existing SBS. then all the data is copied, the active directory migration tool is run which handles a bunch of stuff, and the exchange migration tool is run. this is probably a gross sumarization of the process, MS's article on migration to a new SBS is over way over 50 pages, but it boils down to time... is there a quicker way?

 

[Genx87]

I'd read their detailed paper myself. But I dont see a reason to put the newserver into its own domain. I'd imagine a simplified process is something like this.

Join SBS2003 to current domain, transfer roles, decomission old SBS 2000 server.

You wont be able to run two SBS server in the same domain for more than a few days at a time before the SBS without the master role shuts itself off.

 

[RebateMonger]

Most SBS consultants will recommend that you use the migration methods developed by http://swingmigration.com if you are trying to migrate from SBS 2000 to SBS 2003.

Microsoft's ADMT is NOT simple. Even Microsoft admits it's not the best tool for migrating SBS. If you use the Swing Migration tools (the kit is $200 including support by the owner, SBS MVP Jeff Middleton), you'll have a guaranteed result, guaranteed timetable, and much less pain.

 

[kstornado]

I'll second RM's suggestion of the swing migration. Especially if you've never done a SBS migration in the past...

 

[dphantom]

Originally posted by: RebateMonger
Most SBS consultants will recommend that you use the migration methods developed by http://swingmigration.com if you are trying to migrate from SBS 2000 to SBS 2003.

Microsoft's ADMT is NOT simple. Even Microsoft admits it's not the best tool for migrating SBS. If you use the Swing Migration tools (the kit is $200 including support by the owner, SBS MVP Jeff Middleton), you'll have a guaranteed result, guaranteed timetable, and much less pain.

Thanks for the link. I may have such a project shortly so this could come in handy.

 

[sieistganzfett]

i read a bunch on the swingmigration, tons of people recommend it. I was wondering if swingmigration will turn the mess admt is, and taking 2 hours to perfect things (6 hrs on avg for a migration start to finish for a small bus. w/ less than 20 pc w/ a 2000 sbs) to maybe far less time where the chunk is almost solely the transfer part. now its like 60% of the time, and the next 40% of headaches w/ things not working...

you cant add a SBS to a domain and promo it, and demote the orig, change the destination SBS name to the orig's name, is what pisses me off about this current process, the svr name change breaks half the stuff and eats up the time since trobleshooting across everything needs to be done... my main goal is figure out how to do it, even though it isnt supported and doesnt seem allowed or even possible under the current method. will swing migration satisfy my goal? is there any sites that explain even just this and will give a working end product?

 

[RebateMonger]

Did you look at this chart? It shows the effects of the various migration approaches.

Swing Migration retains your old Server name and domain name, as shown in the chart. It also retains all current Domain Workstation User profiles, keeps Outlook rules, and keeps your current SBS Server running. You should only be without a Server during the final data transition.

Finally, if something goes wrong with the migration, you still have a fully working SBS 2000 Server.