Upgrading to Small Business Server 2003

Discussion in 'Windows Small Business Server' started by Percy, Aug 14, 2005.

  1. Percy

    Percy Guest

    I have a SBS200 Server with old hw. I am going to do an upgrade of new hw and
    SBS2K3. I know I can do a new SBS2K3 server, then ADMT, transfer data or
    swing method, etc., etc.

    However, I had a thought of another process that I think would be faster
    than a swicng and or temp dc approach. However, I have not found anyone else
    using this approcah below in any of the SBS discussions.
    Anyway Here goes...
    Old Server gets a full backup including system state
    Turn old server off
    New Server gets SBS2000 installed with same name, same IP and a full restore
    of the old server
    Modify server drivers
    New Server ths gets an in place upgrade to SBS2K3

    My issue and concern is the new server will need to have the drivers
    modified: i.e. video, NIC and controller.
    Comments, Concersns?
    Thanks!
     
    Percy, Aug 14, 2005
    #1
    1. Advertisements

  2. You will be much better off with a Swing migration SBSMigration.com than
    your apprach. Inplace upgrades are not as successful and your Workstations
    will not just plugin AFAIK with that approach.
     
    Frank McCallister SBS MVP, Aug 14, 2005
    #2
    1. Advertisements

  3. Percy

    Crina Li Guest

    Hi Percy,

    Thank you for posting in SBS newsgroup.

    From your problem description, I understand your issue to be: you want to
    migrate your SBS 2k to SBS 2k3. If I have misunderstood your concerns,
    please do not hesitate to let me know.

    As I know, you can not restore the SBS 2000 to a New Server gets SBS2000
    installed with same name, same IP because the hardware configuration has
    been changed between old server and the new server.

    Generally, we would use the below Migration WhitePaper to migration SBS
    server from 2k to 2k3. With this method, the new domain name and server
    name would be different from old one, but, the domain user profile will be
    retained and you do not need to recreate it and rejoin your client to the
    domain.

    Migrating from Small Business Server 2000 or Windows 2000 Server to Windows
    Small Business Server 2003
    http://download.microsoft.com/download/6/d/c/6dccf9b4-d915-4c95-b5af-100b89e
    02add/SBS_MigratingSBS2k.doc

    In the above article, the step by step instruction will guide you through
    the whole migration process and you do not need to disjoin the client
    computer from the original domain and rejoin it into the new domain. The
    domain user profile will be retained and you do not need to recreate it.
    The user account migration will be performed by ADMT migration utility.

    If you want to keep the original domain name, you then could use the
    following 2 workarounds.

    I. Use the FSMO transfer method to migrate SBS 2000 to 2003. Using this
    method, the domain name will keep intact however the server name will not
    maintain. If you do want to keep the server name, you can have to use the
    FSMO transfer method again. Using this method you will use an interim
    server hardware. This is called a ''swing'' migration. The detailed steps
    are:

    1. Make a full backup of the SBS 2000 server.

    2. Save the attached tool to your old SBS 2000 server, unzip it, dismount
    the Mailbox Store in Exchange System Manager, run the tool, locate the
    Exchange priv1.edb file (C:\Program Files\exchsrvr\MDBDATA\priv1.edb) and
    the tool will list the Organization Name and Site Name. Write down them.
    You can also copy the priv1.edb file to a Windows XP client computer and
    run the tool on it in case you encounter problems in running the tool on
    SBS 2000.

    3. Install Windows Server 2003 on an interim box using the SBS 2003 CD #1
    and join in the SBS domain.

    IMPORTANT: If keeping the domain name and server IP address (we can change
    it after the migration), but using a different server name is acceptable,
    you can replace the "interim" server box using the destination server box
    where you want to host SBS 2003.
    4. Run DCPromo and set it up as additional domain controller in the SBS
    domain. For more regarding adding an additional server to the SBS 2000
    domain, see:

    http://www.microsoft.com/technet/prodtechnol/sbs/2000/maintain/addsrvrs.mspx

    5. Transfer the FSMO roles from the old SBS install to the interim server.
    More info on how to do this:

    324801 HOW TO: View and Transfer FSMO Roles in Windows Server 2003
    http://support.microsoft.com/?id=324801

    If we cannot transfer the roles using the Graphical User Interface, we can
    use the Ntdsutil tool:

    255504 Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain
    Controller
    http://support.microsoft.com/?id=255504

    6. Set the interim Server as a GC (Global Catalog Server). To promote a DC
    as GC, you can follow the steps in the following MS Knowledge Base article:

    a. On the remote domain controller, start the Active Directory Sites and
    Services snap-in.

    b. In the console tree, double-click "Sites", and then double-click
    <site_name>.

    c. Double-click "Servers", click your domain controller, right-click "NTDS
    Settings", and then click "Properties".

    d. On the "General" tab, click to select the "Global catalog" check box to
    assign the role of global catalog to this server.

    e. Restart the domain controller.

    7. Remove Exchange attributes (not mailbox) from all users by choose the
    Exchange Task in "AD User and computers". If you find that you only have
    the three items (Delete Mailbox, Move Mailbox and Enable Instant
    messages.), you can just ignore them. This step is only to make sure to
    remove all other attributes you have configured for users.

    8. Stop all the Exchange services on Old Server to take the databases out
    of use. Copy the MDBDATA folder (C:\Program Files\exchsrvr\MDBDATA) to the
    interim server.

    9. Stop DHCP on SBS 2000, install DNS (make it AD Integrated so that it
    will replicate all DNS information from the SBS server) and DHCP on the
    interim Windows 2003 server and then configure the DHCP scope the same as
    SBS 2000.

    10. Configure the interim server to point to itself for DNS. Configure all
    the client computers to point to the interim server as DNS. If you are
    using DHCP to issue DNS server settings, you should configure your new DHCP
    server to reflect the changes.

    11. After making sure the clients can successfully log on the domain, open
    AD User and Computers, connect to the interim server and remove the SBS
    2000 server account from the Domain Controllers container.

    12. Take the old SBS server offline.

    IMPORTANT: If you decide to do a swing migration using an interim server,
    you can then re-run the above steps (#3~#12) to install SBS 2003 on the
    destination server box and migrate the AD, DNS, DHCP information and the
    Exchange database files. Otherwise, continue with the steps below.

    13. Insert SBS 2003 Disc 1 on the new server to run SBS setup until
    finished (be sure the organization information and site name for Exchange
    is *exactly* the same as we got at step #1; this is very important as you
    will not be able to move the Exchange database files if you are using a
    different organization name).

    14. Run through your To Do List to get on the client add packs, configure
    Internet connection, etc.

    15. Apply service packs and patches so the new server will be at the same
    update level as the old server.

    16. Stop Exchange Services on both servers. On the NEW SERVER, rename the
    MDBDATA folder to MDBDATAOLD and then copy the same folder we backed up at
    step 7.

    17. If the new Exchange Server won't start the mailbox and public folder
    store, open Exchange System Manager, right click the Mailbox Store and
    choose Properties, click the Database page, select "This Database can be
    overwritten by a restore" and then click OK. Do the same things to the
    Public Folder Store.

    18. Run clean up agent in mailbox store and reconnect user mailbox back to
    AD users

    19. Type in email address for each user.

    20. All software settings won''t be migrated, so you will have to
    reconfigure (eg, Exchange settings, ISA)

    21. The client machines should be able to work on the new server.

    NOTE: Do not remove anything from the old SBS 2000 server before we make
    sure everything is working well on the new server.

    More Information: How to change the server IP address
    ----------------------------------------------------------------
    To change the server''s IP address, we should run the Server
    Management\Standard Management\Internet and E-mail\Change Server IP Address
    wizard to change the server IP address. This wizard will perform a series
    of actions to configure the server and appropriate services (such as RRAS,
    DNS, DHCP, Exchange, WINS, IIS and etc.) to use the new IP address.

    II. The second method is In-place Upgrade method. I understand that the
    older serve may retire after the migration. You could use the KB to move
    the SBS 2k3 from the old server to new one after the upgrading. The main
    method would go through the following process

    1. Use the following upgrade white paper to upgrade your SBS 2k3 to SBS 2k3.

    This page is the migration guide
    http://www.microsoft.com/windowsserver2003/sbs/upgrade/default.mspx

    2. Use the Microsoft Knowledge Base Article to move SBS 2k3 to a new
    hardware box.

    Note: This article has not been published yet, but it will be very soon.

    Please do not hesitate to let me know if you have any further concerns.

    Hope the information help and I look forward to your reply.

    Best regards,

    Crina Li (MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.

    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | Thread-Topic: Upgrading to Small Business Server 2003
    | From: "=?Utf-8?B?UGVyY3k=?=" <>
    | Subject: Upgrading to Small Business Server 2003
    | Date: Sun, 14 Aug 2005 08:22:01 -0700
    | | Newsgroups: microsoft.public.windows.server.sbs
    |
    | I have a SBS200 Server with old hw. I am going to do an upgrade of new hw
    and
    | SBS2K3. I know I can do a new SBS2K3 server, then ADMT, transfer data or
    | swing method, etc., etc.
    |
    | However, I had a thought of another process that I think would be faster
    | than a swicng and or temp dc approach. However, I have not found anyone
    else
    | using this approcah below in any of the SBS discussions.
    | Anyway Here goes...
    | Old Server gets a full backup including system state
    | Turn old server off
    | New Server gets SBS2000 installed with same name, same IP and a full
    restore
    | of the old server
    | Modify server drivers
    | New Server ths gets an in place upgrade to SBS2K3
    |
    | My issue and concern is the new server will need to have the drivers
    | modified: i.e. video, NIC and controller.
    | Comments, Concersns?
    | Thanks!
    |
     
    Crina Li, Aug 15, 2005
    #3
  4. I think Crina left a couple of things out. Start with not giving any credit
    to the methodology research or origination while quoting a process
    researched and documented through www.SBSmigration.com, not Microsoft. My
    website does a better job of explaining the concepts, and has great diagram
    to illustrate what it all means.



    I guess we don't have any copyright enforcement to worry about as long as we
    include that MS disclaimer wherever we post? That probably means the
    copyright on my website isn't of interest too.



    If you go to my website, you will find references to some issues to avoid
    exposing your server to security vulnerabilities that SBS 2003 SP1 should
    patch, but if you follow Crina's steps, SP1 never finishes installing.
    Fortunately, this is documented in my Kit and for my customers.



    I would also think that if PSS still has an official stance on Swing
    Migration, you might expect their staff to post it when they decide to
    describe it, so here's what I understand that policy to be:



    Swing Migration is not supported by PSS.



    To my knowledge, Swing Migration isn't documented by MS either, to that
    hampers PSS in providing support unless they want to follow my project
    outline.



    You see, the irony here is that Crina failed also to point out that PSS
    doesn't support any of what was just described in that post as a migration
    process, and if you get into the middle of it before you call PSS for help,
    the official answer is they will tell you to go back to the MS supported
    project documentation. I think it's wonderful that occasionally PSS does
    help with issues that are discovered in the progress of a Swing Migration,
    and yet they won't guide you through it from end to end.



    I fail to see what the "value add" is for PSS to have engineers post
    detailed steps on things they don't have to support. I'm very grateful to
    PSS for all the kindness I receive for the occasional mention that community
    developed and embraced solutions like Swing Migration exists, but even the c
    ommunity as a whole has been pretty consistent in concluding that it's
    better to point people to the book or go to my website to get completely
    authoritative information, rather than to try to paraphrase something YOU
    DON'T WANT TO SUPPORT. That's why I continue to try to keep my documentation
    complete, up to date set of documentation....and include support. My
    documentation is a viable option to the whitepaper methods that MS
    recommends and supports, but which the community has dubious opinions.



    The only thing that was held back by my release of the documentation in all
    forms was retaining rights of publication or paraphrase it. The only reason
    for that was to discourage someone from doing a half-assed job of providing
    incomplete information that would cause confusion by the claim "this is
    Swing Migration". Nobody would really be helped by that. Any idiot could
    post anything they want and call it Swing Migration, so you can see how that
    doesn't boost confidence in the concept or success using it. You see, if
    people try this without completely accurate documentation, they have really
    bad problems or mess up their servers, and then they call PSS for help. That
    costs them money. And then PSS says they won't help them finish that project
    path because it's unsupported. That really angers people who have just paid
    money. This makes for bad perceptions of the value of PSS..taking your money
    for telling you they won't support what you are doing.



    On the other hand, it's great to have PSS validate the project guide I
    created. So if you would like to avoid the various issues of finding out
    after the fact that PSS won't give you any support on this, you might prefer
    to either buy the book with the chapter I wrong on Swing Migration, or come
    to my website to buy the complete project guide...including support.



    Don't forget, after you pay for that support call to PSS, they will tell you
    they don't support this. On the other hand, you are assured of support when
    you buy the Swing It!! Kit from my website.



    If you don't want any support, get the book, I'm sure that Harry would
    appreciate the plug, so it's: www.smbnation.com



    Advanced SBS 2003 technical book written by SBS-MVPs, acclaimed authors,
    columnists, SBS experts. ISBN: 0-974858-07-2, 950-pages Advanced Windows
    Small Business Server 2003 Best Practices



    Jeff Middleton SBS-MVP

     
    Jeff Middleton [SBS-MVP], Aug 16, 2005
    #4
  5. BTW, Percy, the process that you originally described is somewhat of a
    paraphrase of a KB by MS on how to restore a Domain Controller to different
    hardware. I don't recommend you do that, and you will find some related
    information on my website about the problems of doing in-place upgrades with
    SBS 2003 over the top of SBS 2003.

    How to perform a disaster recovery restoration of Active Directory on a
    computer with a different hardware configuration
    http://support.microsoft.com/default.aspx?scid=kb;en-us;263532

    Like I said, I recommend you not try to migrate using that KB, but I thought
    you might find it useful to answer your questions about the process.

    I suggest you look at my website instead.

    Jeff Middleton SBS-MVP
     
    Jeff Middleton [SBS-MVP], Aug 16, 2005
    #5
  6. Percy

    Crina Li Guest

    Hi Percy,

    Regarding the ''swing'' migration, please refer to the website and
    suggestion of Jeff.

    Thanks again!

    Best regards,

    Crina Li (MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.

    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | Thread-Topic: Upgrading to Small Business Server 2003
    || From: "=?Utf-8?B?UGVyY3k=?=" <>
    | Subject: Upgrading to Small Business Server 2003
    | Date: Sun, 14 Aug 2005 08:22:01 -0700
    | | Newsgroups: microsoft.public.windows.server.sbs
    |
    | I have a SBS200 Server with old hw. I am going to do an upgrade of new hw
    and
    | SBS2K3. I know I can do a new SBS2K3 server, then ADMT, transfer data or
    | swing method, etc., etc.
    |
    | However, I had a thought of another process that I think would be faster
    | than a swicng and or temp dc approach. However, I have not found anyone
    else
    | using this approcah below in any of the SBS discussions.
    | Anyway Here goes...
    | Old Server gets a full backup including system state
    | Turn old server off
    | New Server gets SBS2000 installed with same name, same IP and a full
    restore
    | of the old server
    | Modify server drivers
    | New Server ths gets an in place upgrade to SBS2K3
    |
    | My issue and concern is the new server will need to have the drivers
    | modified: i.e. video, NIC and controller.
    | Comments, Concersns?
    | Thanks!
    |
     
    Crina Li, Aug 17, 2005
    #6
  7. Percy

    Percy Guest

    Cirna, Thank you for your thoughts and detailed infomation it is very much
    appreciated.
     
    Percy, Aug 20, 2005
    #7
  8. Percy

    Percy Guest

    Jeff,
    I will take a look at the site and iformation. Thank you it is very
    appreciated.
     
    Percy, Aug 20, 2005
    #8
  9. Percy

    Crina Li Guest

    Hi Percy,

    Thanks for your reply.

    It is my pleasure to work with you in this post. If you have any questions
    or concerns regarding the issue, please do not hesitate to let me know. We
    are glad to be of the assistance.

    Again, thank you for using Microsoft newsgroup. Have a nice day. :)

    Best regards,

    Crina Li (MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.

    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | Thread-Topic: Upgrading to Small Business Server 2003
    || From: "=?Utf-8?B?UGVyY3k=?=" <>
    | | Subject: RE: Upgrading to Small Business Server 2003
    | Date: Sat, 20 Aug 2005 06:31:01 -0700
    || Newsgroups: microsoft.public.windows.server.sbs
    |
    | Cirna, Thank you for your thoughts and detailed infomation it is very
    much
    | appreciated.
    |
     
    Crina Li, Aug 23, 2005
    #9
    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.