Integrating Windows 2000 Server into an existing Windows NT 4.0 domain: You need the new computer to be a domain controller in the current NT 4.0 domain. What is the correct upgrade sequence to introduce Windows 2000 Active Directory?

Introduction / Context:
In a Windows NT 4.0 domain, only the Primary Domain Controller (PDC) holds the writable SAM database. To introduce Windows 2000 Active Directory into an NT domain, you must first upgrade the NT PDC to Windows 2000; this server becomes the first Windows 2000 domain controller and creates the AD forest/domain.

Given Data / Assumptions:

• Existing single NT 4.0 domain with multiple NT servers as DCs.
• Goal: add Windows 2000 Server as a domain controller for that domain.
• No disruption of domain accounts and trusts.

Concept / Approach:
The supported path is to install a new NT 4.0 server as a Backup Domain Controller (BDC) in the existing domain. Then promote that BDC to become the PDC (so you do not touch the original PDC). Finally, in place, upgrade that promoted PDC to Windows 2000 Server and run the Active Directory Installation Wizard (DCPROMO) as part of the upgrade, bringing the domain into AD.

Step-by-Step Solution:
Install the new server as NT 4.0 BDC and let it fully synchronize.Promote the new BDC to PDC (now it holds writable SAM).Upgrade that PDC to Windows 2000 Server, installing Active Directory.Add additional Windows 2000 DCs as needed and decommission old NT DCs.

Verification / Alternative check:
After upgrade, validate logons, replication, and policies. Ensure the domain functional state is consistent and clients continue to authenticate.

Why Other Options Are Wrong:
Creating a new domain with the same name: Causes conflicts; not supported.

Shutting down PDC and creating a new AD domain: Disruptive and invalid approach.

Installing Windows 2000 as a replica in NT domain: Replica DCs only exist after AD is established by upgrading the PDC.

None of the above: Incorrect because option A is the standard sequence.

Common Pitfalls:
Upgrading the production PDC directly without a fallback, skipping full synchronization before promotion, or not planning DNS integration required by AD.

Final Answer:
Install NT 4.0 as a BDC in the existing domain, promote it to PDC, then upgrade that server to Windows 2000 Server