No more transition Pack?

Discussion in 'Windows Small Business Server' started by Adam S., Feb 5, 2009.

  1. Adam S.

    Adam S. Guest

    Hi all

    We requested a quote a for a transition pack, and were told that
    "Microsoft does not make the transition packs any more."
    So what are the option to move from SBS03 to 2003 standard and
    eventually to 2008, or directly to 2008?

    TIA
     
    Adam S., Feb 5, 2009
    #1
    1. Advertisements

  2. Adam S.

    Adam S. Guest

    Thank you sir.
    One more question if you do not mind.
    The company I work for and baby sit the server moved from Windows
    standard server 2003 to SBS 2003 abut 5 years ago, and still have the
    original license agreement.
    Now that we were acquired again, we needed to move back to 2003
    standard, and let the parent company upgrade to 2008.
    Will they need to re-purchase those licenses? or Can they use the old
    ones?
     
    Adam S., Feb 5, 2009
    #2
    1. Advertisements

  3. The last I heard, the TP had been discontinued in error and was being
    reinstated on the part lists. Have your vendor double check with Microsoft
    or their supplier.
     
    Merv Porter [SBS-MVP], Feb 6, 2009
    #3
  4. Unless the license for Windows 2003 has been sold to another party, it is
    valid imo. But you should call the MS license team for their advice.

    From an MS CSS support post:

    For more information about SBS Licensing, I would like to suggest you
    contact our License Office for help. You can call 1-800-426-9400 (select
    option 4), Monday through Friday, 6:00 A.M. to 6:00 P.M. (PST) to speak
    directly to a Microsoft licensing specialist.

    Worldwide customers can use the Guide to Worldwide Microsoft Licensing
    Sites
    http://www.microsoft.com/licensing/index/worldwide.asp to find contact
    information in their locations.

    More information about SBS licensing:

    How to configure licensing on an additional Windows server in an SBS network
    http://support.microsoft.com/default.aspx?scid=kb;en-us;327644

    Detail price information about the SBS 2003 CAL:
    http://www.microsoft.com/windowsserver2003/sbs/howtobuy/pricing.mspx

    Client Access Licensing for Windows Small Business Server 2003
    http://www.microsoft.com/windowsserver2003/sbs/howtobuy/CALs.mspx

    Frequently Asked Questions About Windows Small Business Server 2003
    Licensing.
    http://www.microsoft.com/windowsserver2003/sbs/techinfo/overview/licensingfa
    q.mspx

    Hope this helps.
     
    Larry Struckmeyer [SBS-MVP], Feb 6, 2009
    #4
  5. Adam S.

    Adam S. Guest

    Adam S., Feb 6, 2009
    #5
  6. Adam S.

    Adam S. Guest

    Cris

    Thanks again.
    We do not have R2, just SP2, would it make any difference?
    Also, our vendor (Insight) is suggesting we go directly to 2008
    server, so is there any documentation from MS on how to perform such
    upgrade?
     
    Adam S., Feb 6, 2009
    #6
  7. Depends on whether you want/need to keep the same server name same domain
    name same ip scheme, and how many users and how difficult to visit each
    desktop and what portions of SBS you actually use.

    Simplest is to export the exchange mailboxes with .pst or exmerge, add a
    Windows 2008 server(s), seize all the FSMO roles, add GC, and kill the SBS.

    Install Exchange, import the mail.

    Next would be to export, create a new Server 2008, visit each desktop,
    disjoin from SBS and rejoin the new nw.

    You might also want to look at www.sbsmigration.com

    or carry on with your quest for a transition pack. Last time I visited this
    it required upgrade of SBS to R2, then the transition pack, which is why it
    may have been killed off prematurely.

    The benefit of the transition pack is that it brings you to Server Standard
    and Exchange Standard and if premium SQL and ISA standard without throwing
    out the investment you have already made in SBS, as it is priced to give you
    parity.
     
    Larry Struckmeyer [SBS-MVP], Feb 6, 2009
    #7
  8. Adam S.

    Adam S. Guest

    50 users.
    I do not have to keep the same domain name.
    Easy Access.
    The 08 path looks good to me. If you do not mind, I am going to
    prepare a little plan and post it for your review.
     
    Adam S., Feb 6, 2009
    #8
  9. Adam S.

    Adam S. Guest

    What bothers me is that we were already on 2003 standard 4 or 5 years
    ago, paid for SBS license and now have to get back to go out.
    Thank god it is only a temporary baby sitting job for me :).
    Can the same "out of SBS" path work with 03, or must it be to 08?
     
    Adam S., Feb 6, 2009
    #9
  10. Adam S.

    Adam S. Guest

    Can I use the active directory migration tool for the accounts an file
    permissions, or are there other programs available?
     
    Adam S., Feb 6, 2009
    #10
  11. Adam S.

    Adam S. Guest

    I am lost.
    Are you saying that I can:
    Introduce an new DC,
    seize the FSMO using NTDSUTIL ( I read about it online)
    wipe the SBS C drive,
    install it as a BDC for that purpose
    re-establish the shares
    I and I am good to go (Exchange aside?)
    So why does one need a TP?
     
    Adam S., Feb 7, 2009
    #11
  12. You have the basics, but there are some pitfalls. There are some specific MS
    documents about the process of replacing a DC and seizing the roles. Sorry
    I don't have the references here.

    You would use the Transition Pack to keep your server infrastructure in
    place, to avoid paying for the licenses you have already purchased a second
    time, and to facilitate the "transition" from SBS to a Windows Server
    Standard server and domain without the restrictions imposed by SBS. This is
    usually done by organizations that have outgrown the 75 user/device limits,
    but may also be done for reasons such as trusts, acquisitions. But to throw
    out the monetary investment is a big waste. Your SBS license and 50 users
    licenses represents a substantial investment, which you "recoup" by using
    the Transition Pack.
     
    Larry Struckmeyer [SBS-MVP], Feb 7, 2009
    #12
  13. Adam S.

    Adam S. Guest

    Too many political aspects, I must concentrate on the task...
    After all the reading I did, and endless phone calls I made to the new
    owners, I found out a class mate of mine from CSUN is working for the
    new parent company, and among others he is an MCSE with significant
    hands on experience.
    He unofficially suggested the following, after imaging and backing up
    the SBS server with storage craft(yet to learn)
    1) Introduce 2003 Enterprise to the domain.
    2) Install Exchange to a member server and move everything over after
    backing up offline EDB along with exmerger.
    Remove First exchange following
    http://support.microsoft.com/kb/822931
    3) AD Integrated DNS on the new server verify zone transfer.
    4) Make the new DC a GC server and transfer the FSMOs with ntdsutil.
    http://support.microsoft.com/kb/255504
    Establish DHCP scope, WINS on the new server.
    5) Run DCPROMO to demote the SBS server.
    6)Uninstall Exchange on SBS.
    7) check members login and permissions.
    8) Wipe out former SBS C drive an and install as member.
    9) Re-create shares.
    Pray to the Active Directory lord.

    Comments are greatly appreciated for these upcoming cold nights.
    I am planning on next weekend, it's my Valentines day bailout plan
    ;-).
     
    Adam S., Feb 7, 2009
    #13
  14. Adam S.

    Adam S. Guest

    Un-necessary spending and time IMHO.
    We have created and completed the entire procedure with no transition
    pack in a VM lab. It worked.
    Advantage TP:
    1. Avoid having to add a DC to the domain.
    2. Avoid having to go to through the exchange procedure.
    Disadvantage TP (assumptions by reading online).
    1. Patching, getting to R2 cleanly.

    Here is the final lab procedure:
    1) Install 2003 Enterprise to the domain (We only had Ent. Version in
    the lab).
    2) Install Exchange to a member server and move everything over after
    backing up offline EDB along with exmerge (I used exmerge for the
    import).
    Remove First exchange following
    http://support.microsoft.com/kb/822931
    3) Installed AD Integrated DNS on the new server, verify zone
    transfer.
    4) Make the new DC a GC server and transfer the FSMOs with ntdsutil.
    GUI did not work, I had to force.
    http://support.microsoft.com/kb/255504
    Establish DHCP scope, WINS on the new server.
    5) Run DCPROMO on the SBS to demote.
    6)Uninstall Exchange on SBS.
    7) check members login and permissions.
    8) Wipe out former SBS C drive and install as member / different name.
    9) Re-create shares.
    10) NTDSUTIL metadata cleanup.
    11) ADS Edit to clean all replication partners.

    We are planning on the real deal this coming weekend.
     
    Adam S., Feb 9, 2009
    #14
  15. Adam S.

    Adam S. Guest

    Which is pretty much what we are doing.
    We have now done this twice in a VM environment, and the process is
    refined and works every time.
     
    Adam S., Feb 10, 2009
    #15
  16. Adam S.

    Adam S. Guest

    Russ

    We have them.
    We moved to SBS about 5 years ago, and still have the MOLP agreement
    for 60 CAL, and 10 servers, all for 2003.
    At this point we have only 43 users and 7 servers, so we are good.
    Anyway, I will do my best to document step by step and do a post
    posting.
     
    Adam S., Feb 10, 2009
    #16
  17. Adam S.

    Adam S. Guest

    The ad company I work for was acquired by a large financial
    institution, so In the next two weeks we have to move out of SBS in 4
    offices. The others have 3-5 users, so it would be a no brainer.
    The instructions are to move out of SBS and integrate into the parent
    company AD forest.
    HQ wants a "clean sheet", meaning windows domain, routers configured
    per their specs, two way trust, and they will take care of the rest.
    I assume there is a plan for the day after, non of my business or
    concern.
     
    Adam S., Feb 11, 2009
    #17
  18. Adam, hoping you get this message... you posted last year that you successfully migrated from SBS 2003 to Server 2003 Enterprise without the Transition Pack. Your procedure looks sound and makes sense. My only concern is whether or not this process cleans up all the SBS licensing limitations in the Active Directory, primarily the 75-user limit and inter-domain trust limit. Any feedback?

    Dean N.
     
    Dean Niquette, Nov 23, 2010
    #18
  19. Adam,

    Hope you get this post... I saw that you were able to successfully migrate last year from SBS 2003 to Server 2003 Enterprise without the Transition Pack. Your process looks sound and makes sense, but I am concerned that it might leave behind all the SBS licensing restrictions in the pre-exsiting AD, particularly the 75-user limit and the inter-domain trust limitation. Did your manual migration process lift these restrictions?

    Thanks,
    Dean N.
     
    Dean Niquette, Nov 23, 2010
    #19
  20. Adam,

    Hope you get this post... I see you were able to manually migrate last year from SBS 2003 to Server 2003 Enterprise, without using the Transition Pack. The procedure looks sound and makes sense. However, I'm concerned that the manual procedure might leave behind all the SBS restrictions in the pre-exsiting AD, particularly the 75-user limit and the inter-domain trust limitation. Any feedback on that?

    Thanks,
    Dean N.
     
    Dean Niquette, Nov 23, 2010
    #20
    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.