Migration Question - MVP's Only Please

Discussion in 'Windows Small Business Server' started by Ian McCulloch, Jun 26, 2004.

  1. Hello guys

    In response to my last post in which I have discovered SBS 2003 must exist
    in its own domain, I really need some advice on migrating an existing 2k
    domain to an SBS domain. I do have white papers in hand and will be reading
    them. I would like to supplement my reading material with some hard core
    experience out there.

    So here goes:

    15 users, 2 servers

    Server A
    P3 1.2GHz, 1 GB RAM
    Win2k SP4 DC, F/P, Backup,
    C (2.6 GB free)/D (20 GB free) (runs a small 250 MB database that is easily

    Server B
    P4 2.4 GHZ Xeon, 1 GB RAM, 70 GB HDD (RAID 5)
    Win2K SP4 Citrix Metaframe XPs FR3
    Runs all users in Citrix

    Server C (not in Production)
    P4, 2.3 GHx, 512 MB RAM
    C (15GB), D(18GB)
    Windows 2003 Server currently member server on Win2k domain

    My thinking so far is this -

    port the database, files, home folders on server A to server C
    Upgrade the 2k domain controller to SBS 2003 using the appropriate white

    A few questions:
    What considerations are there for the TS licensing server currently running
    on Server A
    What about IIS 5.0 on server A? Should this be uninstalled first as it may
    complicate the migration (I run a small web interface for some help desk
    Any paging file considerations?
    any serious AD considerations?
    What would you guys/gals do?

    Your suggestions are so much appreciated!

    Sydney, NS
    Ian McCulloch, Jun 26, 2004
    1. Advertisements

  2. by limiting your respondents to MVP's you're severely depleting your
    'library' of information. Many of the non-mvp regulars would be able to
    answer your questions and Microsoft employees are excluded from our little

    I'd probably dive in headfirst and throw CD1 of the SBS set into ServerA and
    inplace upgrade the 2K domain to SBS2K3.

    BTW. You mention you have a spare box that is not in production. GOOD!!!
    Grab the SBS media, put a second NIC in the spare box and a spare switch so
    the NICs are live but not connected to your existing domain and do a test
    install onto this box. Come back and ask questions, of which you should have
    many. FLATTEN it and DO IT AGAIN. You may then be ready to try a trial run
    of your 'migration' by running up W2K as a DC on the box, make it as similar
    to your existing box as possible, and then upgrading it.

    It's a fairly common belief around here that you don't know how to install
    SBS until you've done it three times.
    DON'T name your AD DNS the same as your public FQDN (and on this point, if
    your current AD is incorrectly named, ie. if it is named as your FQDN, this
    would be a great opportunity to fix it).
    Interfere with the SBS install as little as possible, the wizard will guide
    The most important part of the install is right at the end. You MUST
    complete the To-Do list.

    Sydney, NSW
    SuperGumby [SBS MVP], Jun 26, 2004
    1. Advertisements

  3. Thanks there Gumby - I realize I should have opened up the formun to
    everyone - my mistake - any other takers?

    Why the insistence on the unique FQDN as opposed the Internet one?
    Ian McCulloch, Jun 27, 2004
  4. I like the 'Sydney' location

    How old is your city by the way?
    Ian McCulloch, Jun 27, 2004
  5. http://www.imho.dyndns.org/addns.htm

    SuperGumby [SBS MVP], Jun 27, 2004
  6. http://www.cityofsydney.nsw.gov.au/hs_chos_history_of_council.asp

    The settlement of Sydney was established in 1788 as a convict colony ruled
    by British Governors. In 1823, a Legislative Council was established but the
    Governor retained the power to appoint officials to the Council and to
    over-ride their decisions. By the 1840s, convict transportation had
    virtually ended and the colonists wanted more control over their affairs. An
    Imperial Act of 1842 created a new Legislative Council, of which one third
    was nominated and two thirds elected by property holders.


    Bloody silly pommies stayed in England and thought they were punishing
    people by sending them to the most beautiful place on the planet. I hope
    your Sydney is half as pleasant :)
    SuperGumby [SBS MVP], Jun 27, 2004
  7. Ian McCulloch

    Eric Hartley Guest


    not MVP but would like to contribute.

    we completed a similar migration to the one you describe
    below. I would use server A as your bare metal install
    once the DB, users, files, etc. are migrated off. we had
    to bring in an extra server to the client site simply for
    this purpose. i.e. ,they wanted to keep existing
    hardware for SBS03 install and were unwilling to
    sacrifice gain with risks of moving all data from one box
    to another and then back to same box.

    we also had an existing 2nd server on site which was an
    App server... only TServ 2K, not Citrix add-on. This
    server admin account did not migrate with ADMT but was
    back up and running within 10 minutes following the
    complete migration of the 1st box to SBS03 (ADMT does not
    migrate built-in admin accounts). Once SBS03 was back on-
    line fully, turning on TServ licensing was ticketing to
    getting existing 2nd server back operational. The
    TServer server found the new licensing server without
    problem. Additionally, because the TServ server was left
    as 2K server, licensing contraints remained the same with
    user account still allowed to access TServ without a
    purchase of TServ licenses... now changed with TServ on
    an Server 03 OS.

    During the upgrade, since we were migrating all data to a
    standby hot server and then back to original server, we
    were able to name the original server the same name when
    under the 2K OS as a DC. This saved a little time with
    TServ licensing and mapped drives on user workstations.

    IIS 5.0 had a few minor sites of concern on the original
    2K DC. We simply migrated the files for each site
    (copied) to another network store, copied back to new
    SBS03 buit box and reconfigured the sites. This is best
    scenario with web contence because we also changed the
    local LAN IP address scheme during the migration. Not
    sure if that applies to your implementation.

    We didn't have any issues with page files since the
    original box was taken down to bare metal/reformat, etc.
    installation. Also, now problems with AD migration using
    the ADMT tool. it can give unpected errors sometimes but
    they are work-around-able.

    Obvisouly, use active directory migration tool (ADMT) to
    move users with their SIDs intact. you've probably seen
    other steps involved in the white papers from MS.

    can't think of anything else important to tell. FYI,
    took one of our technicians 29 hours for entire migration
    with existing apps on old server (fax server, document
    management system, OCR system, etc.). Had a hardware
    issue along the way which took up 4 hours to troubleshoot
    but ended up being a 2 minute fix. (!).

    Eric Hartley
    Bluetowne Consulting Group
    Charleston, SC
    Eric Hartley, Jul 27, 2004
    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.