Re: NT 4 Migration ( PDC & BDC )

From: SL Alagappan (lalagappan_at_hotmail.com)
Date: 09/20/04 

Date: Mon, 20 Sep 2004 11:31:21 +0530

Hi Rebecca,

Thanks for your quick tips.

1) The problem with Scenario 1 is that, the new server which propose to
procure ( Compaq ML370 G4 ) is not supported under Windows NT 4.0. Hence,
may not be able to install Windows NT 4.0 in the new server due to driver
non-availability,etc.

2) any idea on how to migrate DNS, DHCP and Wins from Win NT 4.0 to W2K3? 

-- 
With Regards,
SL Alagappan,
"Rebecca Chen [MSFT]" <v-rebc@online.microsoft.com> wrote in message 
news:YT0Vs0snEHA.3096@cpmsftngxa06.phx.gbl...
> Hi Alagappan,
>
> There are two scenarios regarding to your question.
>
> Scenario 1: Remain the same domain name
> ==================================
> If you would like to remain the same domain name as NT domain, you need to
> do the following:
> - Install Windows NT as a BDC on a new server
> - Promote a Windows NT 4.0 BDC to the PDC, which demotes the PDC to a BDC.
> - Do a full backup of the former PDC and remove it from the network.
> - Upgrade the new PDC to Windows Server 2003.
> - Use the Windows Server 2003 Active Directory wizard to turn on the 
> Active
> Directory service. The Active Directory service imports the existing user
> accounts, groups, and other settings from the PDC.
> - Run your new Windows Server 2003 domain controller with Active Directory
> for a test period.
> - If desired you can do a clean installation of Windows Server 2003 on the
> former PDC, and bring it online as an Active Directory domain controller.
> - Transfer all Flexible Single-Master Operation (FSMO) roles to the new
> Windows Server 2003 domain controller.
> - Verify all directory information has replicated.
> - Demote the first domain
>
> More details could be found:
> Why Upgrade from Windows NT 4.0 to Windows Server 2003
> <http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tow
> net.mspx>
>
>
> Upgrading from Windows NT Server 4.0 to Windows Server 2003
> <http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tow
> s03-2.mspx>
>
> Scenario 2: Create a new domain
> ========================================
> If you prefer to create a new domain, please use the steps below:
>
> 1. Install Windows 2003 on a new server.
> 2. Use Active Directory wizard to promote your Windows 2003 machine to be 
> a
> new forest root domain.
>
> 3. Create the trust relationship between the two domains.
>
> 4. Use the ADMT to migrate data from the old domain to the new domain.
>
> 5. Transfer FSMO from NT to win2k3 if you want to retain the original DHCP
> and DNS setting.
> 6. Using Ntdsutil.exe to seize or transfer FSMO roles to a domain 
> controller
> <<http://support.microsoft.com/default.aspx?scid=kb;en-us;255504>>
>
> 7. Remove the original NT 4 domain.
>
> Before you migrate, I strongly suggest that you download and read the
> following documents about migrating from Windows NT 4.0 to Windows 2003:
>
> Migrating from Windows NT Server 4.0 to Windows Server 2003
> <http://www.microsoft.com/downloads/details.aspx?FamilyID=e92cf6a0-76f0-4e25
> -8de0-19544062a6e6&DisplayLang=en>
>
> Further question, 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: 2003 Migration
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: i got 6 server in company which contains NT4 , windows 2000 , windowser 2003
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: Urgent Advise - [WildPacket]
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: Connection to a SAMBA Active Directory
    ... I built a new Windows 2003 Server in a brand new domain. ... I am able to define a 2 way Realm trust using the Active Directory ... There is a bit of confusing on the SAMBA side. ...
    (microsoft.public.exchange.connectivity)