Become a fan of Slashdot on Facebook


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


+ - SBS 2003 to SBS 2008 Migration-> 2

Submitted by serverguy
serverguy (1650163) writes "Migrating from SBS 2003 to SBS 2008 using the conventional method or "Microsoft's recommended method" can be a simple process but when things don't go according to plan it can be very stressful for Server Admins, and while the Microsoft method is well documented, it's the Swing Migration has been praised as the better option by many Admins due to the simplicity and transparency of the process. If you do go down the path of a MS Migration a common issue you may encounter is the "Exchange Certificate Error" when moving Mail Boxes. It can be a royal pain if you ever come across this mid Migration but simple to fix if you know how."
Link to Original Source
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

SBS 2003 to SBS 2008 Migration

Comments Filter:
  • Swing migration is the only way to go, I have followed what you call the "conventional method" which has faild me many times. I can't recall what version MS are up to on their migration documentation but I suspect they have cleaned it up somewhat as the guide I followed was poorly writen and misleading at times. Also with Swing I can keep the source and destination's name the same which can save a lot of time in large implementations.
  • While I agree with what Micro is saying, I have used the MS method many times without a hiccup, we are very careful with prepping all servers before migration which I think is the key here, nice story btw.

"Pascal is Pascal is Pascal is dog meat." -- M. Devine and P. Larson, Computer Science 340