Re: URGENT - Migration Strategy

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Thomas (tknetwork_at_adelphia.net)
Date: 10/27/04


Date: 27 Oct 2004 14:59:43 -0700

Rebecca:

I'm planning to install all existing servers on my NT 4.0 network as
member servers running Windows 2003 (90+ File, Database, Fax Servers).
While doing this, I plan on creating a new Windows 2003 domain
controller in each one of my locations. Use the migration tools to
move my users etc. to the new 2003 domain and set a cutover date, join
all "pre-Installed" windows 2003 servers on the NT 4.0 domain to the
new 2003 domain.

Reasons for choosing migration path as opposed to an upgrade include:

1. Clean Installation
2. Re-creating partitions on existing servers to a larger size than
the current 4-Gig for the OS.
3. Maintain my NT 4.0 Infrastructure in case a "Roll-Back" is
necessary
Etc.

Is this a method that stands to reason as each company's situation
differs from one another.

Thank You for your input.

v-rebc@online.microsoft.com (Rebecca Chen [MSFT]) wrote in message news:<UMAq3JfsEHA.3184@cpmsftngxa10.phx.gbl>...
> Hello,
>
> It is hard to say migration must be better than upgrade. Both of them have
> their own advantages. In-place upgrade will keep the original domain name,
> whereas migration will need a new domain NetBIOS name.
>
> Following are the good readings before you make any decision:
> White Paper: Migrating Windows NT Server 4.0 Domains to Windows Server 2003
> Active Directory
> http://support.microsoft.com/default.aspx?scid=kb;en-us;818623
>
>
>
> Why Upgrade from Windows NT 4.0 to Windows Server 2003
> http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4town
> et.mspx
>
> Solution Accelerator for Domain Server Consolidation and Migration: Windows
> NT 4.0 to Windows Server 2003
> http://www.microsoft.com/technet/itsolutions/techguide/msa/solacc/dmcnmg/dcm
> plg.mspx
>
> Windows NT Server - Upgrade/Migrate
> http://www.microsoft.com/technet/prodtechnol/winntas/deploy/upgrdmigrate/def
> ault.mspx
>
> If you decide to use migration, the process will go like this:
> 1. Setup a new Windows Server 2003 DC in the new domain.
>
> 2. Create the trust relationship between the two domains.
>
> 3. Use the ADMT to migrate data from the old domain to the new domain.
>
> Active Directory Migration Tool Overview
> http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.
> asp
>
> 4. Transfer FSMO from NT to win2k3 if you want to retain the original DHCP
> and DNS setting.
> Using Ntdsutil.exe to seize or transfer FSMO roles to a domain controller
> <http://support.microsoft.com/default.aspx?scid=kb;en-us;255504>
>
> 5. Remove the original NT 4 domain.
>
> Further questions, let us get in touch!
>
> Best regards,
>
> Rebecca Chen
>
> MCSE2000 MCDBA CCNA
>
>
> 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.
>
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.



Relevant Pages

  • Re: Please help...
    ... Install NetBEUI on Windows XP ... But> the problem is only on XP professional clients to which i> am not able to install NetBuei protocol(for RAS). ... We have file servers & exchange servers located> on different boxes than the RAS server. ...
    (microsoft.public.win2000.ras_routing)
  • Re: failed admin pak installation - w2k3
    ... The Windows Installer service cannot update one or more protected Windows ... Jabez stated: "Disable Windows File Protection." ... I can install this admin pak in my test environment w/o any issue. ... our production servers and the installation fails with "Windows File ...
    (microsoft.public.windows.server.setup)
  • Multiple problems with Win2003 SP2
    ... servers servers running Win2003 R2, but on a further two 32-bit member ... reboot = No, reboot required = No ... Content Install Installation Failure: Windows failed to install the ...
    (microsoft.public.windows.server.general)
  • Re: Multiple problems with Win2003 SP2
    ... servers servers running Win2003 R2, but on a further two 32-bit member ... reboot = No, reboot required = No ... Content Install Installation Failure: Windows failed to install the ...
    (microsoft.public.windows.server.general)
  • BITS 2.0 + Windows Installer 3.1 RC = Fail to load profile
    ... I recently installed a WSUS server which forced the install of the following ... Windows Installer 3.1 Release Candidate ... Now my Windows 2003 servers run fine after these install but my Windows 2000 ... "Windows cannot load your profile. ...
    (microsoft.public.windowsupdate)