Upgrading SBS 2003 to Server 2008 and Exchange 2007

Discussion in 'Windows Small Business Server' started by Paul, Sep 11, 2008.

  1. Paul

    Paul Guest

    I need to migrate an existing SBS 2003 system to a new Windows Server 2008
    box, which will also be running Exchange 2007. As I will not be retaining
    any of the 2003 software I would prefer to avoid the expense of the
    Transition Pack for SBS. I have read some conflicting / confusing advice on
    the best route for making this transition - here is the process as I
    understand it but I would appreciate any comments, particularly if I have
    missed something obvious.

    My plan is:
    * Add the new 2008 server as a member server in the existing SBS 2003 domain.
    * Run adprep on the SBS to update the AD schema.
    * Promote the 2008 box to being an additional Domain Controller. I believe
    that I have to do this before installing Exchange otherwise the promotion to
    DC breaks Exchange.
    * Install Exchange 2007 on the Server 2008 box and add to the domain.
    * Move data to the new server.
    * Transition mailboxes to the new server.
    * Move group policies etc. to 2008 server.
    * Transition FSMO roles from SBS 2003 to 2008 server.
    * Remove SBS 2003 server from domain.

    Does this plan look anything like sensible, or have I missed anything
    important? Any help or comments much appreciated.

    Paul, Sep 11, 2008
    1. Advertisements

  2. Why not just wait a bit more and install SBS 2008?
    Supported migration and a lot cheaper.
    Susan Bradley, Sep 11, 2008
    1. Advertisements

  3. Paul

    Paul Guest

    I went this route because we want to extend to a second domain for mail
    purposes and I was advised that SBS is limited to a single domain. Either
    way, the software is bought now (and buying as a charity at educational rates
    the cost difference is minimal).

    Does my route sound workable?


    Paul, Sep 11, 2008
  4. Not for email, you can have Exchange 2007 pick up multiple

    I think someone misunderstood the meaning of 'single domain' for AD

    I would actually read the SBS 2003 to SBS 2008 migration docs as other
    than the fact you won't be migrating to SBS 2008, it will be similar
    from an AD standpoint.

    The fact you'll lose RWW is a bummer though.
    Susan Bradley, Sep 11, 2008
  5. Paul

    Paul Guest

    Many thanks for your reply Susan. Yes, it turns out I was mis-advised about
    some of the limitations of SBS. I'm not too concerned about RWW though, so
    long as OWA still works.

    My real question, though, is about the workability of the migration path I
    am proposing. I will read the SBS 2003 to SBS 2008 documentation as you
    suggest, but I was under the impression that SBS 2008 provides automated
    migration facilities which I won't have access to runing Server 2008 Standard?


    Paul, Sep 11, 2008
  6. It's not all automated. And what I'm aiming you for is the blocks of

    Let me also get you some KBs that will backup your plan as well.
    Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP], Sep 11, 2008
  7. Hello,

    Thank you for your post and Susan's input.

    November 12, 2008, is the official launch date for Windows Essential
    Business Server 2008 and Windows Small Business Server 2008. As Susan
    indicated, if possible, you may consider migrating from SBS 2003 and SBS
    2008. Since it is big project, the migration is not all automatic. Here are
    some information which list step by step migration guide lines and may be
    of some help.

    Migrate to Windows Small Business Server 2008 from Windows Small Business
    Server 2003

    Migrating from Windows Small Business Server 2003 to Windows Essential
    Business Server

    More information:

    Licensing and Pricing Frequently Asked Questions - Windows Small Business
    Server 2008

    Windows Small Business Server 2008 Release Documentation

    More information:

    Downloadable documentation for Windows Small Business Server 2008

    Hope this helps.

    Best regards,
    Robbin Meng(MSFT)
    Microsoft CSS Online Newsgroup Support
    Robbin Meng [MSFT], Sep 12, 2008
  8. Paul

    Nick Gillott Guest

    SBS2008 is a 64 bit product, 2003 is 32 bit. Consequently there is no
    upgrade path using the same hardware.
    Nick Gillott, Nov 17, 2008
  9. You might want to define "migrate" a little better.
    Lanwench [MVP - Exchange], Dec 30, 2008
  10. Cute. Still insufficient, but cute.
    Lanwench [MVP - Exchange], Dec 30, 2008
  11. The TP removes all SBS restrictions.

    75 user/device limit.
    Must hold FSMO roles.
    DHCP rogue detection (I think).
    and I'm not sure if it does anything else, really.

    What it doesn't remove (and I think it should) is the SBS components you are
    no longer licensed to run and cannot reinstall should you experience a
    problem requiring such. RWW, custom sharepoint site, SBS FAX, Wizards.

    But then, I reckon the TP should also remove GPO customisations, put the
    system completely into 'virgin standard AD' condition. Either you run SBS or
    not. This is not 'snobbery', it is in regard to 'ongoing viability' of the
    system, should you need to rebuild the system you have no right nor method
    to reinstall 'SBS customisations', post TP organisations should not use
    (rely?) on features they have no right, nor method, to repair.
    SuperGumby [SBS MVP], Jan 14, 2009
  12. Paul

    Les Connor Guest

    SBS 2008 (Windows Server 2008) is a 64 bit operating system, while SBS 2003
    (Windows Server 2003) is 32 bit, so inplace upgrades are out of the question
    under any circumstances.
    Les Connor, Jan 15, 2009
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.