Migration Steps?

Discussion in 'Active Directory' started by Jeff7566, Nov 8, 2006.

  1. Jeff7566

    Jeff7566 Guest

    Does anyone know of any good books, websites or anything else that has a good
    step by step how to migrate a Win 2k domain to a Win 2k3 R2 domain?
    Jeff7566, Nov 8, 2006
    1. Advertisements

  2. Paul Bergson [MVP-DS], Nov 8, 2006
    1. Advertisements

  3. Jorge de Almeida Pinto [MVP - DS], Nov 8, 2006
  4. Jeff7566

    Jeff7566 Guest

    Thanks for your reply Paul, but I guess im looking for more of a how to on
    the actual ADMT tool and what order to preform the steps in, I have already
    gone through all the the steps suggeted to prepare for the migration now I
    just want to make sure that when I do migrate that I dont do this in the
    wrong order and have a whole ton of issues.
    Jeff7566, Nov 8, 2006
  5. Then you aren't upgrading. Are you creating a seperate forest and looking
    to move the objects to the new forest?
    Paul Bergson [MVP-DS], Nov 8, 2006
  6. Jeff7566

    Jeff7566 Guest

    Ok Im sorry, here is what Im doing, I have 2 Domains one named domain and one
    named recu.local Im trying to migrate all my user and computers from domain
    to recu.local and getting rid of the old domain controller so the domain
    domain will not exist after this is complete, so this is a migration not a
    upgrade as im trying to get away from the old domain name.

    sorry for the confusion
    Jeff7566, Nov 8, 2006
  7. Jeff7566

    kj Guest

    kj, Nov 9, 2006
  8. Migration high level steps are:
    * Make sure the AD has been configured (sites, subnets, replication, OUs,
    GPOs, delegations, DNS, WINS, DHCP, etc.)
    * Setup name resolution (WINS or DNS) between source and target
    * Setup trusts (if an external trust is configured and sidhistory is used,
    disable sid filtering)
    * Install and configure migration tooling
    * Migrate groups, user accounts with passwords and group memberships (with
    * Migrate clients from the source domain to the target domain, translate
    security on the client, and translate profiles (at this moment users start
    logging on with their new AD account on the migrated clients that have been
    migrated previously to the w2k3 domain)
    * Migrate mailboxes if needed
    * Migrate servers to the new domain or migrate data to new servers
    * Translate security (Re-ACL) of the data/resources from source security
    principals to target security principals (replace the security descriptors
    from the old domain with the security descriptors from the new domain )
    * Cleanup temporary configurations
    * Cleanup sidhistory (recommended!). sIDHistory is used to access resources
    while those resources still have security descriptors from the old domain.
    As soon as all data (file, folders, mailboxes, etc.) have been re-ACL-ed
    sIDHistory can be cleaned. Sidhistory should only be used temporary for
    migration purposes!
    * Remove trusts
    * Decommission old domain(s)

    For more info on migrating to an AD domain also see:

    ADMTv3 has been out for a while, so be sure to use that version.



    # Jorge de Almeida Pinto # MVP Windows Server - Directory Services

    BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
    BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
    Jorge de Almeida Pinto [MVP - DS], Nov 9, 2006
    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.