locked
SBS 2003 update to SBS 2011 without Exchange RRS feed

  • Question

  • Hello from a newbie.

    I have a SBS2003 and am going to migrate to SBS 2011 soon. I'm not using Exchange on that server, we have a third pary email product. As I understand it, I can boot off the SBS2011 dvd and run the migration and installation at the same time. If that is the case, do you see any problems when it comes to the Exchange migration? After the migration, is the source server still a domain controller or just a member server? Other than restoring from backup, is there any way to recover is the migration fails?

    Thanks.

    Lee

    Tuesday, January 8, 2013 9:40 PM

Answers

  • Hello Lee,

    Please follow the below document for this migration:

    http://www.microsoft.com/en-in/download/details.aspx?id=14570

    If you have mailboxes created for any reason on source server during the very end you might need to disable the mailbox and delete them before you could uninstall and demote the SBS 2003 server to complete the migration. Make sure you source server is clean to proceed with migration.

    SBS 2011 Standard Migrations – Keys to Success 3/3:

    http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx

    http://blogs.technet.com/b/sbs/archive/2011/07/08/sbs-2011-standard-migrations-keys-to-success-part-2-the-setup-phase.aspx

    http://blogs.technet.com/b/sbs/archive/2011/07/11/sbs-2011-standard-migration-keys-to-success-part-3-post-setup-and-common-failures.aspx

    Please take a complete backup of the server using NTbakup, which should include system state for sure.

    Let me know if there are any other issues that I can address.


    Thanks & Regards, Naga Santosh EPS(SBS)

    • Proposed as answer by Naga Santosh Tuesday, January 8, 2013 10:19 PM
    • Marked as answer by Andy Qi Thursday, January 10, 2013 10:58 AM
    Tuesday, January 8, 2013 10:19 PM
  • Short answer: SBS is an integrated suite of products and doesn't like to run without certain components. SBS 2003 was more forgiving than SBS 2011, but none should have been run this way.

    If you aren't going to use Exchange, don't migrate to SBS 2011 Standard. First and foremost, I'd consider 2012, not 2011. Server 2012 Essentials does not include Exchange, but is limited to 25 users. 2012 Standard would be appropriate for users over 25. If you *need* 2008 R2 as a core for some reason, either look at SBS 2011 Essentials (does not include Exchange, but is limited to 25 users) or 2008 R2 standard. Regardless, SBS 2011 Standard is a very poor choice. It is more expensive than its counterparts, really doesn't like it when you disable Exchange, and the CALs are more expensive.

    -Cliff

    • Marked as answer by Andy Qi Thursday, January 10, 2013 10:58 AM
    Wednesday, January 9, 2013 1:29 AM
  • In addition to Cliffs excellent response, make sure that if you migrate to Essentials or Standard, that you properly uninstall Exchange 2003 from the domain.  DO NOT just shut off the server without removing Exchange, you will cause your self no uncertain amounts of grief in the future if you do this.  

    Jeremy

    • Marked as answer by Andy Qi Thursday, January 10, 2013 10:58 AM
    Wednesday, January 9, 2013 3:59 AM

All replies

  • Hello Lee,

    Please follow the below document for this migration:

    http://www.microsoft.com/en-in/download/details.aspx?id=14570

    If you have mailboxes created for any reason on source server during the very end you might need to disable the mailbox and delete them before you could uninstall and demote the SBS 2003 server to complete the migration. Make sure you source server is clean to proceed with migration.

    SBS 2011 Standard Migrations – Keys to Success 3/3:

    http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx

    http://blogs.technet.com/b/sbs/archive/2011/07/08/sbs-2011-standard-migrations-keys-to-success-part-2-the-setup-phase.aspx

    http://blogs.technet.com/b/sbs/archive/2011/07/11/sbs-2011-standard-migration-keys-to-success-part-3-post-setup-and-common-failures.aspx

    Please take a complete backup of the server using NTbakup, which should include system state for sure.

    Let me know if there are any other issues that I can address.


    Thanks & Regards, Naga Santosh EPS(SBS)

    • Proposed as answer by Naga Santosh Tuesday, January 8, 2013 10:19 PM
    • Marked as answer by Andy Qi Thursday, January 10, 2013 10:58 AM
    Tuesday, January 8, 2013 10:19 PM
  • Short answer: SBS is an integrated suite of products and doesn't like to run without certain components. SBS 2003 was more forgiving than SBS 2011, but none should have been run this way.

    If you aren't going to use Exchange, don't migrate to SBS 2011 Standard. First and foremost, I'd consider 2012, not 2011. Server 2012 Essentials does not include Exchange, but is limited to 25 users. 2012 Standard would be appropriate for users over 25. If you *need* 2008 R2 as a core for some reason, either look at SBS 2011 Essentials (does not include Exchange, but is limited to 25 users) or 2008 R2 standard. Regardless, SBS 2011 Standard is a very poor choice. It is more expensive than its counterparts, really doesn't like it when you disable Exchange, and the CALs are more expensive.

    -Cliff

    • Marked as answer by Andy Qi Thursday, January 10, 2013 10:58 AM
    Wednesday, January 9, 2013 1:29 AM
  • In addition to Cliffs excellent response, make sure that if you migrate to Essentials or Standard, that you properly uninstall Exchange 2003 from the domain.  DO NOT just shut off the server without removing Exchange, you will cause your self no uncertain amounts of grief in the future if you do this.  

    Jeremy

    • Marked as answer by Andy Qi Thursday, January 10, 2013 10:58 AM
    Wednesday, January 9, 2013 3:59 AM