RE: ADMT and Single Domain

From: Frances [MSFT] (v-franhe_at_microsoft.com)
Date: 02/03/05


Date: Thu, 03 Feb 2005 09:50:46 GMT

Hello,

Regarding your scenario, it is recommended to upgrade to a win2k3 domain.
You can perform a "not in place" upgrade. In this way, you don't have to
upgrade your PDC and BDC to win2k3 directly. Instead, you install BDC on
the new computer, promote it to be PDC, and then upgrade to win2k3. I will
give you the detailed steps to perform such an upgrade.

As a kind reminder, please backup the whole system before you take any
action. Also, it is best if you perform the upgrade process during a
non-business time such as the weekend.

Performing a "not in place" upgrade
======================

1.Install NT 4.0 BDC on the new box.
Please assign a static IP address to this server to install DHCP server and
DNS server.

2. Replicate DHCP to the BDC.
Is your PDC holding the DHCP server?

130642 How to Move a DHCP Database to Another Windows Server
http://support.microsoft.com/?id=130642

3. Replicate DNS from PDC to BDC.
        
        3.1 Manually create a secondary zone on the BDC to replicate for the zone
on the NT DNS server.

3.2 Transfer the zone over to the BDC.

3.3 Change the secondary zone on the BDC to a Standard Primary Zone.

        Refer to the following article for more information.

        DNS and MS Windows NT 4.0
http://www.microsoft.com/technet/archive/winntas/deploy/prodspecs/dnswp2.msp
x

        4.Promote the BDC to the PDC, which demotes the PDC to a BDC.

        5.Do a full backup of the former PDC and remove it from the network.

        6.Upgrade the new PDC to Windows Server 2003.
If you want to expand the boot partition, please refer to the following KB:

325857 How To Expand the Boot Partition During a Windows Server 2003 Upgrade
http://support.microsoft.com/?id=325857

        7.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.

        8.Run your new Windows Server 2003 domain controller with Active Directory
for a test period.

        9.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.

        10.Transfer all Flexible Single-Master Operation (FSMO) roles to the new
Windows Server 2003 domain controller.

        11.Verify all directory information has replicated.

        12.Demote the first domain controller to a member server, and remove from
the domain.

Regarding your questions, I would like to answer them in order.

Q1.Is there an upgrade path that will allow me to introduce a new W2K3 box
into my NT 4 domain and then set up AD within the domain?

A: You cannot introduce win2k3 DC into NT domain. Please use the "not in
place" upgrade to get the win2k3 domain you want.

Q2.Then demote the NT 4 servers to member servers?

A: There is no built-in tool to demote NT BDCs to member servers.

NT servers (BDCs) can be kept in a win2k3 domain when the domain level is
Windows 2000 mixed (default). However, I suggest that you use a third-party
tool (UPromote) to demote the BDCs to member servers and then raise the
domain level to enjoy more win2k3 domain features.

UPromote: Promote your NT Server to a Domain Controller
http://utools.com/UPromote.asp

Note: The third-party products that this article discusses are manufactured
by companies that are independent of Microsoft. Microsoft makes no
warranty, implied or otherwise, regarding the performance or reliability of
these products.

Hope this helps. If you have any further questions, don't hesitate to get
in touch!

Best regards,

Frances He

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: NT4-->W2K3 Upgrade, Domain Change Revisted
    ... The domain name can be changed in Windows NT4. ... Stop all BackOffice services such as Exchange, SQL Server, and IIS. ... is necessary for each BDC to successfully change to the new domain name. ... If the name can be changed during upgrade it would save ...
    (microsoft.public.windows.server.migration)
  • RE: 2 x DC, 2 sites and NT4 servers same domain HELP
    ... I understand you want to upgrade NT PDC and BDC to 2k3. ... Migrating Windows NT Server 4.0 Domains to Windows Server 2003 Active ...
    (microsoft.public.windows.server.migration)
  • Re: need to rebuild trust relationship b/w domain controllers
    ... If you are not interactively logged onto the server, ... i tried using netdom resetpwd on the old bdc that's ... this is just a test - i read that this is the correct way to upgrade an NT ... >> Reestablish the trust relationship. ...
    (microsoft.public.windows.server.active_directory)
  • Re: need to rebuild trust relationship b/w domain controllers
    ... If you are not interactively logged onto the server, ... i tried using netdom resetpwd on the old bdc that's ... this is just a test - i read that this is the correct way to upgrade an NT ... >> Reestablish the trust relationship. ...
    (microsoft.public.win2000.active_directory)
  • Re: Suggested reading nt4 to server2003
    ... If you add a new BDC in the current domain, promote BDC to PDC and then ... new domain name and migrate all information from NT to win2k3 domain. ... both upgrade and migration will be the option. ... Upgrading from Windows NT Server 4.0 to Windows Server 2003 ...
    (microsoft.public.windows.server.migration)

Loading