RE: MIgration Question

Tech-Archive recommends: Fix windows errors by optimizing your registry



Amanda,

Thank yu very much for your reply. I have to read and understand all the
steps involved and test everything. I will keep you posted on this project.
Once again I sincerely appreciate your guidance.
--
Dipti


"Amanda Wang [MSFT]" wrote:

> Hello,
>
> Thank you posting here.
>
> I found you have posted another post called Migration of two forests to one
> here. Do these two posts describe the same phenomenon?
>
> If so, I would give you my answers in one thread here and please ignore
> that post.
>
> Based on your description, I understand you want to join two sister domains
> into parent company's forest. If I have misunderstood, please feel free to
> let me know.
>
> Q1: Join two sister domains into parent company's forest and move all
> users, computers, groups.
>
> Depends on your real environment, the two sister domains should have their
> own different DNS names. Therefore, I suggest you perform the following
> plan to achieve the goal:
>
> Step1: create two trees under parent's company's forest, install two new
> Win2k3 DC called Domain3 and Domain4.
> ============================================================================
> ==============================
>
> For the convenience, we call one sister domain is Domain1 and the other is
> Domain2.
>
> For the structure of tree and forest, please refer to the following article
> and pay more attention to the figure 1.7:
>
> Active Directory Logical Structure
> http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/
> en-us/Default.asp?url=/resources/documentation/windows/2000/server/reskit/en
> -us/distrib/dsbb_act_uzlw.asp
>
> Step2: Then establish two way trusts between Domain1 and Domain3, Domain2
> and Domain4. Please refer the following article and establish trusts:
> ============================================================================
> ======================
>
> Between Win2k and Win2k3, on Win2k just as from Win2k to WinNT and on
> Win2k3 just as from Win2k3 to WinNT:
>
> How to establish trusts with a Windows NT-based domain in Windows 2000
> http://support.microsoft.com/default.aspx?scid=kb;en-us;308195
>
> HOW TO: Establish Trusts with a Windows NT-Based Domain in Windows Server
> 2003
>
> Step 3: Use ADMT tool to migrate the resources from Domain1 to Domain3, and
> then Domain2 to Domain4.
> ============================================================================
> =======================
>
> You can download ADMT from the link below:
> Active Directory Migration Tool v.2.0
> http://www.microsoft.com/downloads/details.aspx?FamilyID=788975b1-5849-4707-
> 9817-8c9773c25c6c&DisplayLang=en
>
> About how to migrate from 2000 to 2003 by using ADMT just as migrate from
> 2000 to 2003, please refer to:
>
> How to Use Active Directory Migration Tool Version 2 to Migrate from
> Windows 2000 to Windows Server 2003
> http://support.microsoft.com/default.aspx?scid=kb;en-us;326480
>
> During migration process, the Recommended Migration Order is listed below
> for your reference:
> 1. Domain Global Group
> 2. Domain Local Group
> 3. User migration
> 4. Computer migration
>
> Step 4: Remove the old win2k domains.
> ****************************************************************************
> ***8
>
> About the above migration plan, you know we need to change our original
> domain name. From your meaning, my understanding is that you want to keep
> the original domain names after migration. Am I right? If I am right,
> there are two methods can achieve the goal:
>
> Method 1: Rename Windows 2k3 domain name
> =================================
> 1. Install win2k3 on the new server.
> 2. Promote it to DC.
> 3. Use the migration process to migrate user accounts etc..
> 4. Install Exchange 2k3.
> 5. Migrate Exchange information.
>
> NOTE: Don't install Exchange 2k3 before you change the domain name.
>
> Refer to KB articles:
> Windows Server 2003 Active Directory Domain Rename Tools
> http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx
>
> Step-by-Step Guide to Implementing Domain Rename
> http://download.microsoft.com/download/c/f/c/cfcbff04-97ca-4fca-9e8c-3a9c90a
> 2a2e2/Domain-Rename-Procedure.doc
>
> Method 2: Add a new server as a intermittent server
> ====================
> If you have another new server, you use migration process twice. It goes
> like this:
> NOTE: I assume the original domain name is ABC
> 1. Install Windows 2k3 on a server name
> 2. Promote it to DC named EFG.com
> 3. Use migration process to migrate info from ABC to EFG.com
> 4. Take all NT DC offline
> 5. Install Win2k3 on original NT machine
> 6. Promote it to DC called ABC.com
> 7. Use migration process to migrate info from EFG.com to ABC.com
>
> Q2: Related the questions about you also want to migrate the files servers,
> you can use FSMT to migrate file server from one domain to another. We
> suggest you first migrate groups, users, computers by using ADMT and then
> migrate file server by using FSMT. For more references related FSMT,
> please refer to:
>
> Microsoft File Server Migration Toolkit FSMT Site:
> http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfsc.mspx
>
> Overview of the Microsoft File Server Migration Toolkit white paper of FSMT
> http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_over
> view.mspx
>
> Q3: For exchange servers we want to bring in a new exchange 2003 server and
> move information from exchange 2000 server from both forests to new
> exchange 2003 server.
>
> With regards to the Exchange migration, I recommend you post related
> questions to microsoft.public.exchange so that the exchange expert can
> provide more accurate information for you.
>
> HTH! Anything unclear, please feel free to let me know.
>
> Thanks & Regards
>
> Amanda Wang [MSFT]
>
> Microsoft Online Partner Support
>
> 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.
>
> =====================================================================
>
> --------------------
> >Thread-Topic: MIgration Question
> >thread-index: AcVm2tsbj+HTGJieRL6sAU27xUBJGQ==
> >X-WBNR-Posting-Host: 65.213.142.103
> >From: "=?Utf-8?B?RGlwdGk=?=" <Dipti@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >Subject: MIgration Question
> >Date: Wed, 1 Jun 2005 11:51:01 -0700
> >Lines: 20
> >Message-ID: <824DB8BE-DF32-4452-BAA3-2290F6D305AB@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 8bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.migration
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10476
> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >
> >Due to acquisitions/merger I am looking for the options to see how to join
> >our domain to our parent company’s forest. We have windows 2000 domain
> with
> >two domain controllers, 1 exchange 2000 server, SQL 2000, and Windows 2000
> >NAS server for file server. We have a two way trust set up at this time
> with
> >our parent company.
> >
> >We also have other sister companies which will be joining the parent
> >company’s forest . They are also windows 2000 domain and similar set up
> as
> >ours. We also have external trust set up with the sister companies for
> >resource sharing.
> >
> >All domains needs to be able to keep their own group policy etc., when we
> >join our parent company’s forest.
> >
> >What will be best way to accomplish this? Should we move each domain to
> >windows 2003 domain and use AD renaming tool? How is ADMT2 will play out
> in
> >this scenario? Please give me some guidance.
> >
> >--
> >Dipti
> >
>
>
.



Relevant Pages

  • RE: NT 4.0 to windwos 2003 network
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... Windows 2000 Active Directory Migration Tool ... With regards to the Exchange migration, ...
    (microsoft.public.windows.server.migration)
  • RE: Transfer roles
    ... fresh copies of windows 03 and exchange on one of them. ... because migration is more complex. ... The only valid business cases for installing Exchange Server on a DC that I ...
    (microsoft.public.windows.server.migration)
  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • RE: DST update for Exchange 2003 and Outlook 2003
    ... The Ldp GUI tool is included when you install Windows Server 2003 Support ... Microsoft CSS Online Newsgroup Support ... DST update for Exchange 2003 and Outlook 2003 ...
    (microsoft.public.exchange.admin)
  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP client is not a reserved client. ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)