migration from win2k with SQL2k to sbs2k3

Discussion in 'Server Migration' started by Guest, May 13, 2005.

  1. Guest

    Guest Guest

    I am planning to migrate win2k server box with SQL2k installed to SBS2k3 Std
    using ADMT ver2.
    MS whitepaper "Migrating from Small Business Server 2000 or Windows 2000
    Server to Windows Small Business Server 2003" was helpful.
    But DHCP portion is unclear to me.
    Does migration work with static IP address on client PCs?
    Also, client want to keep SQL2k server which runs MS Solomon ver4 Database
    as member server.
    What I concern is for computer account "any references to the computer name
    of the source server (for example, UNC paths, shortcuts, and mapped drives)
    are no longer valid at the end of the migration."
    Does SQL database will work after migration if I demote active directory and
    join new domain as a member server?
    Any suggestion will be greatly helpful.

    Followings are site info.
    The source server is win2k-SP1 and is running SQL2k and using active
    directory authentication for Solomon ver 4.
    There is no other windows server on network.
    The client PCs are using static IPs.
    The Destination server is SBS2k3 standard.
    Guest, May 13, 2005
    1. Advertisements

  2. Bong,

    The ADMT method of migration as documented by MS results in renaming your DC
    and your domain, therefore breaking all the namespace involved. This means
    that all those things you listed no longer remain connected. In addition,
    ADMT produces the same results as an Exmerge with regard to breaking single
    instance storage on the new server's Exchange Information Store. That also
    means that you will need to go to each workstation to backup and restore all
    of the Outlook /Exchange rules. You also will find significant disruption to
    the user profiles at every desk and for each user.

    As an alternative, you can review the process that is outlined at my website
    www.SBSmigration.com with regard to Swing Migration. That option eliminates
    the needless disruption of the domain namespace, and it provides you the
    option to build a new server in parallel without shutting down the
    production domain. once you have finished constructing and testing the new
    server, you can make the transition from the old server to the new one in
    about the time it takes to copy the data and Exchange over to the new
    hardware. The server can be a transparent replacement to the previous one,
    and you won't have impact at the local desktops.

    You will not need to shutdown the domain in advance, or do significant
    disaster recovery preparations to the original server because you will have
    it running the whole time. You can mount the original Exchange Information
    Store on the new server, and there's nothing to do in the way of backup
    protection at the workstations.

    If your project plan includes maintaining the original server intact,
    including with all the shared folders, you have the option of just joining
    the SBS to the existing domain without doing anything besides transfering
    the FSMO roles and license management to the new SBS. If you prefer to have
    the new SBS adopt the servername of the original server, you can transfer
    all the shared folder resources to the SBS. At that point, after demoting
    the Win2K server, you would have the option to rename it and that might well
    preserve the SQL application, but that's not certain, it would depend upon
    how that application works.

    You are welcome to contact me directly, or I will watch this thread in the
    Jeff Middleton [SBS-MVP], May 14, 2005
    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.