Inplace Upgrade vs. Migration

Discussion in 'Server Migration' started by Dell, Jul 28, 2004.

  1. Dell

    Dell Guest

    My problem is one of the client's engineers insist on
    conducting a migration instead of an inplace upgrade.
    Can someone provide me with Pros and Cons for In-place
    Upgrade vs. Migration?

    I am in the process of doing a design for a client from
    NT4/Exchange5.5 to Win2K3/Exchange2K3. They will be
    migrating from a single NT4 domain to a Win2K3 single
    forest/single domain. The email will remain in same
    Exchange Organization which will be in a different
    Exchange Resource domain. A two-way NTLM trust will be
    created between the client domain and the Exchange
    Resource Domain. This will allow for the Exchange
    upgrade to consist of adding an Exchange 2K3 server to
    the current Exchange5.5 site. They would also like to
    keep their current NETBIOS name.

    Thanks in Advance,
    Dell
     
    Dell, Jul 28, 2004
    #1
    1. Advertisements

  2. I think the key thing here is that you want to keep the same Netbios name. I
    think this will break the whole migration plan as in order to migrate, at
    least by using ADMT, you need to setup a trust between the existing domain
    and the new 2k/2k3 AD domain and I don't believe this will work if the
    Netbios names are the same. Also HOW do they plan to migrate Exchange? They
    would have to use Exmerge or something to extract all the email from one
    domain and then import it into Exchange in the new domain. This does work
    and I have done it several times but it a little bit of a pain in the butt.
    I much prefer the upgrade as it is safe and you will not lose SID's and the
    computers won't even know anything changed typically. Also an upgrade gives
    you an easy out if something goes wrong. IE if the PDC that you are
    upgrading, usually a new BDC introduced just for upgrading, fails you can
    just promote you old PDC back to PDC and no one will ever know the upgrade
    failed. With a migration there are several things that can go wrong that can
    cause issues on the network until they are fixed. This will entail two
    domains now and setting up Trusts etc and this can be a adminstrative pain
    until the migration is completely done. I always prefer the upgrade method
    and I have never had it do anything but work. The typical reason for doing a
    migration is that you want ot change your domain name or you are merging
    domain or something to that effect. For a single domain that wants to kep
    it's Netbios name I see no reason to do a migration. Just my $0.02!! Also be
    very careful about your DNS namespace and DNS service setup. It is critical
    to AD. Mainly make sure you do not use the real internet DNS name for your
    internal domain name. Use something like mydomain.local or something.
     
    Scott Harding - MS MVP, Jul 28, 2004
    #2
    1. Advertisements

  3. Hi Dell,

    Thanks for your posting here.

    Migration is used to restructure the domain. You need to build the new
    Windows 2003 domain first and then use ADMT to move the information from
    the original domains to this one. So you need a different domain name.

    If you prefer to use the same domain name, it is recommended that you try
    in-place upgrade. There is little special configuration is required. The
    original account database is maintained, domain instances' SID is kept, and
    settings are also maintained.

    I believe the following documents will be helpful.

    HOW TO: Upgrade a Windows NT 4.0-Based PDC to a Windows Server 2003
    http://support.microsoft.com/?id=326209

    Upgrading from Windows NT Server 4.0 to Windows Server 2003
    http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tows
    03-2.mspx

    Windows NT Server 4.0 Upgrade Guide
    http://www.microsoft.com/windowsserver2003/partners/isvs/ntmigrate.mspx

    Have a nice day!

    Regards,
    Bob Qin
    Product Support Services
    Microsoft Corporation

    Get Secure! - www.microsoft.com/security

    ====================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    ====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Bob Qin [MSFT], Jul 29, 2004
    #3
    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.