Jeff Middleton’s Swing Migration (www.sbsmigration.com) methodology has been used successfully around the world. You can use it to simply move a current SBS installation to new hardware, or to also upgrade from sBS2000 to SBS2003 at the same time. I thought I would post what I liked about using SBS Migration:
- It alows you work on the new server completely offline from the current server, allowing you to setup and configure everything without impacting users and current server. In fact, you can do it with the new server back at your office, and not at the custome site
- It does require a third computer that is used to swing the AD and other required files from the current to the new system. But in my case, I used a laptop with 1GB of memory, and Virtual PC.
- The current production server is only offline for a few minutes when you first copy over some files to your interim. After that, you don’t touch the current server again until you are actually ready to do the cutover
- The Swing process retains the same server domain name on the new server, and that’s important because:
- When you are done, in most cases, you do not have to go to any workstation and make any changes – no reconnecting workstations to the domain, etc.
I did my first Swing earlier this year, and when the users came in at the beginning of the week, they literally had no clue that we had swapped out servers. They logged in as normal, and began working!