Re: Migration from NT to W2k3

From: Greg Zygadlo (gregz_at_schange.com)
Date: 08/03/04


Date: Tue, 3 Aug 2004 08:32:55 -0400

What has me puzzled is when to move all the servers from one domain to the
other. Both our Accounts and Resources are in the same domain and all the
documentation points to having an accounts domain and a resource domain.
Nothing seems to talk about Accounts and Resouces in the same domain.

I'm using Virtual PC to try and simulate this in a test enviornment. Just
looking for something that says th recommended order is.

Thanks
"William Wang[MSFT]" <v-rxwang@online.microsoft.com> wrote in message
news:Um47ySReEHA.3064@cpmsftngxa06.phx.gbl...
> Hi Greg,
>
> I did not find a document discusses this scenario. Based on my knowledge,
> the migration should be similar to migrating a NT domain to 2003 domain.
You
> can refer to the following article to migrate each NT domain to 2003
domain:
>
> HOW TO: Set Up ADMT for a Windows NT 4.0-to-Windows Server 2003 Migration
> http://support.microsoft.com/?id=325851
>
> The following are some tips or requirements regarding ADMT:
>
> 1. Generally speaking, domain migrations are complicated tasks. Please
> perform complete backup first for recovery purposes.
>
> 2. We can establish a two way trust between the two domains, and then use
> ADMT with the following three wizards to migrate the group accounts, user
> accounts and client computers:
>
> - Group Account Migration Wizard
> - User Account Migration Wizard
> - Computer Migration Wizard
>
> 3. The account that runs ADMT must have administrator privileges on both
> domains, and also need to be a member of the local administrators group
when
> migrating computer objects.
>
> 4. It is recommended to perform the migration in the following order:
>
> Domain Global Group
> Domain Local Group
> User Account
> Computer Account
>
> 5. Please migrate the groups and users separately (do not migrate the
> associated group members when migrating the groups).
>
> During the group migration, please use the following configurations
>
> [Group Options]
>
> Copy group members * Not Checked
> Fix membership of group * Checked
>
> During the user migration, please use the following configurations:
>
> [User Options]
>
> Migrate associated user groups * Not Checked
> Fix users' group memberships * Checked
>
> 8. For more information regarding ADMT, please refer to:
>
> Active Directory Migration Tool Overview
>
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.a
> sp
>
> Download details: Active Directory Migration Tool v.2.0
>
http://www.microsoft.com/downloads/details.aspx?familyid=788975b1-5849-4707-9
> 817-8c9773c25c6c&displaylang=en
>
> DomainMig.chm in the ADMT installation folder (this file contains very
good
> information).
>
> If you have any questions or concerns, please do not hesitate to let me
> know. I am standing by to help you.
>
> Sincerely,
>
> William Wang
> Microsoft Online Support Engineer
>
> 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.
> --------------------
> >From: "Greg Zygadlo" <gregz@schange.com>
> >Subject: Migration from NT to W2k3
> >Date: Mon, 2 Aug 2004 11:28:21 -0400
> >Lines: 15
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
> >Message-ID: <ODB1KWKeEHA.3476@tk2msftngp13.phx.gbl>
> >Newsgroups: microsoft.public.windows.server.migration
> >NNTP-Posting-Host: 12.96.85.111
> >Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
> >Xref: cpmsftngxa06.phx.gbl
microsoft.public.windows.server.migration:12686
> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >
> >We are planning to do a migration instead of an in-place upgrade so that
we
> >can collapse two NT4 domains into one domain. Does anybody know of a
good
> >document that refers to this type of migration. All the documentation I
see
> >is for an in place upgrade.
> >
> >In my testing enviorment I have the new domain setup and ADMT setup, but
not
> >sure whether I upgrade the BDC's to member servers, upgrade member
servers
> >or bring over the users next.
> >
> >If anybody has any ideas I would appreciate them.
> >
> >Thanks
> >Greg
> >
> >
> >
>



Relevant Pages

  • Re: AD merge with exchange 2007 srv, can ADMT do it?
    ... > ADMT will do user and computer account migration. ... > "Exchange cross forest migration" and you will find some documentations. ... I usually do put together step by step docs such as this, to help folks in the newsgroups, but I haven't yet with this procedure because besides being scattered and the procedure having many facets, my notes are customer specific with domain names, user accounts, passwords, etc, that it will take me some time to go through to compile it into one doc, and I do apologize I am short on time to do anything with this at this point. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2k3 and E2k3 migration to SBS 2003
    ... Most users here have given up on ADMT ... and switched to Swing Migration. ... > Migration Wizard (MigWiz). ... >>>accounts and then using Exchange Migration Wizard ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2k3 and E2k3 migration to SBS 2003
    ... Migration Wizard (MigWiz). ... property is populated on those ADMT migrated accounts. ... and tested process as a basis for this migration. ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange 5.5 to 2003 co-exist question
    ... Use ADMT with SID history for the migration. ... after the ADMT you should get no additional accounts in AD ... Move the Exchange 5.5 Mailboxes fast to 2003. ...
    (microsoft.public.exchange.admin)
  • RE: Migration from 4.5 to 2003
    ... Depends on how far you are in the migration. ... accounts, they will belongs to the new domain. ... unjoin/rejoin the machines back to the domain, or use ADMT to move it back. ... backup, backup, backup. ...
    (microsoft.public.windows.server.sbs)