Hello All. Thank you in advance for the help. I have a customer that has a SBS 2003 box running exchange for calendaring and message store only, (POP mail at off-site vendor), and we are going to replace their box with a new dell poweredge 1900. The new box came pre-installed from Dell. I went through the setup and named the box the same as the old one, and now would like to migrate the users, exchange store and shared folders over the new box. What is the fastest, easiest and safest method of doing this? I obviously cannot put the machine on the network because it has the same computer name as is setup as a dc, but I am sure that I can change the name of the new machine if necessary. Again, thank you in advance for the help.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
PLEASE HELP..SBS 2003 Migrating to Another Machine 1
- Thread starter ITShelps
- Start date
-
1
- #2
- Thread starter
- #3
- Thread starter
- #5
ShackDaddy
MIS
Active Directory Migration tool, with lots of failures and retries. Copy the folders. Figure out how to bring the Exchange store over if the domain is named differently. Rebuild shares and printers. Then you have to touch all the workstation, migrating their profiles using the Files and Settings Wizard on each workstation.
Swing Migration gives you a full roll-back position and makes it so that you probably won't even need to touch a single workstation, except for to verify that it all went just fine. Swing gives you an exact clone of the SBS, for the most part, so that the clients don't know that anything changed. The alternative is really a migration of your users and data to a new place, and the work to reacclimate your clients to what is really a new domain.
Even what you learn in the process of doing a Swing with the sbsmigration.com kit will be worth the small price, not to mention the time savings. I've used it and highly recommend it. I did things the non-swing way plenty of times before moving to Swing, and I'm not going back.
Dave Shackelford
MCSE, CCNA, Microsoft MVP: Exchange
Shackelford Consulting
Swing Migration gives you a full roll-back position and makes it so that you probably won't even need to touch a single workstation, except for to verify that it all went just fine. Swing gives you an exact clone of the SBS, for the most part, so that the clients don't know that anything changed. The alternative is really a migration of your users and data to a new place, and the work to reacclimate your clients to what is really a new domain.
Even what you learn in the process of doing a Swing with the sbsmigration.com kit will be worth the small price, not to mention the time savings. I've used it and highly recommend it. I did things the non-swing way plenty of times before moving to Swing, and I'm not going back.
Dave Shackelford
MCSE, CCNA, Microsoft MVP: Exchange
Shackelford Consulting
- Status
Similar threads
