Upgrading SBS 2003 to Windows Server 2003 Standard/Ent.

Discussion in 'Windows Small Business Server' started by S H A R I Q U E, Aug 1, 2008.

  1. i want to upgrade my SBS 2003 Prem. Edition to Windows Server 2003
    Standard/Ent. Edition without loosing domain. I am running to Exchange server
    on SBS. I have heared a SBS migration kit performing these steps easily. i
    have thoroughly technet site but didnt find any SBS migration kit or SBS
    migration article.

    S H A R I Q U E, Aug 1, 2008
    1. Advertisements

  2. Not sure I'd call that an upgrade, but regardless - you have two choices - a
    Transition Pack, which will convert the existing to Windows Server 2003
    Standard Edition with no limitations plus Exchange Server 2003 Standard
    Edition. Plus your Premium components are unlocked as well. You'll need the
    Premium Transition Pack appropriate to your version (SP1 or R2), and the
    same number of CALs you currently have.

    The "migration" you're referring to is probably Swing Migration
    (www.sbsmigration.com) - that's a solution, assuming you want to lose your
    investment in SBS and buy full, new, copies of Windows Server and Exchange,
    along with your CALs.
    Charlie Russel - MVP, Aug 1, 2008
    1. Advertisements

  3. which option is better choice..Swing migration or Transition Pack..can i save
    domain using both strategies....
    what is the cost associated with transition pack suppose that i have 100 CAL
    requirements, that is, difference of 25 users from SBS users.
    i assume that using Swing migration i dont need to pay for Transition Pack
    or purchase transition pack either.
    furthermore, i have yet to find any technet resource regarding migrating SBS
    2003 to Windows Server 2003 Standard/Ent. Edition ....
    or if you have any detailed documentation for Swing Migration or transition
    S H A R I Q U E, Aug 1, 2008
  4. for the sake of clarity can you go a bit deeper....as to HOWs of
    i have managed to grasp following ideas from your reply.
    is it possible that i install Windows Server 20003 Stndrd/Ent. on separate
    machine make it ADC of SBS...then replicate AD schema and
    attributes...transfer FSMO roles to new server and decommision old one.

    i would appreciate your clarity in your reply.
    is this what initial process ????
    S H A R I Q U E, Aug 1, 2008
  5. The Swing IT method is fundamentally based on retaining the origin server(s)
    'as is' for business continuance. In a 'pure' swing the only change to the
    origin AD is the addition of a DC, the 'swing server'.

    The swing server is then taken offline (after replicating the AD) while the
    FSMO roles remain with the origin server(s). You then 'seize', rather than
    transfer, the FSMO roles on the swing server while it is disconnected from
    the origin AD. At this time the additional DC (swing server) can be removed
    from the origin AD and the origin is back to a pre-swing condition. (nobody
    ['cept me, maybe] normally bothers to do this. The presumption is that the
    origin AD is going to, eventually, be discarded. Who cares if it has an
    orphan DC?)

    At this time you have one DC (the swing server) containing a copy of your AD
    and you clean that copy up (I would remove any additional DCs from the AD
    copy but you might want to run that idea past Jeff, I don't always follow
    the procedure to his letter), including any references to Exchange.

    At this point you can shut down all existing DC's in the origin AD and put
    the swing server online but here comes the 1st mention of SBS (you will note
    that until now I have not mentioned SBS, the swing process is 'designed for'
    but not 'limited to' SBS). _Normally_ you would build your SBS at this point
    using Jeff's version of 'Adding SBS to an existing AD', which is only
    slightly different to the MS way of doing same. Machines and Users can
    hardly tell the migration has happened because of the process. Most
    'swingers' do not put the swing server online, only the eventual SBS.

    In an SBS to SBS swing, and assuming you are using Exchange, you have
    additional tasks about copying DATA and 'forklifting' the Exchange stores.
    This is _basically_ the only 'down time' for users.

    in non-SBS to SBS, SBS to non-SBS, non-SBS to non-SBS, or multiple DC swings
    there are other points to consider and these will likely contribute to
    further down time. eg. in a multiple DC swing I would DCPromo all origin
    servers that are to be retained in the swung domain out of DC roles while
    connected to the origin AD and back to DC roles after the swing.
    SuperGumby [SBS MVP], Aug 1, 2008
  6. I don't have costs - you should do your own calculations. Both methods will
    retain your domain.

    The Swing Migration is quite reasonable (but includes no CAL or license
    conversions), and will do what you want. You'll be on your own for CALs -
    it's simply a set of tools, documentation and support for migration to/from
    SBS. It won't affect your existing license - you'd need to purchase new
    licenses for Server, Exchange, CALs and any others you're using. See the
    sbsmigration web site for details. Even though it's primarily designed to
    migrate from one version of SBS to another version of SBS, it can certainly
    be used for what you want.

    Transition pack will convert your existing licenses into full product
    licenses, and remove the single domain/no trust limitation os SBS. You
    purchase CALs to match your existing CALs, and if you need additional beyond
    the current CAL level, you purchase those separately as normal product CALs.
    Charlie Russel - MVP, Aug 1, 2008
    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.