You must preinstall, configure, and test Windows 2000 Server on 15 computers, then ship them so branch users can enter each computer’s name and product key on first boot. Which deployment method best meets this requirement?

Introduction / Context:
Windows 2000 supports two primary automated deployment paths: unattended setup (using Unattend.txt and optional UDF files) and disk imaging with Sysprep (using sysprep.inf and Mini-Setup on first boot). When you need to fully preinstall and test systems in a lab, then hand off last-mile identity details—like product key and computer name—to remote users, Sysprep with Mini-Setup is the right tool.

Given Data / Assumptions:

• All 15 machines will be installed, configured, and tested before shipping.
• Branch users will enter the computer name and product key upon first startup.
• Desire: identical image with per-machine identity finalized at Mini-Setup.

Concept / Approach:
Sysprep generalizes an installation and prepares it for imaging. A sysprep.inf file controls Mini-Setup prompts. If you omit ProductKey and ComputerName (or use prompts), Mini-Setup will ask the receiving user for those values. While the -noidgen switch is not generally recommended for mass deployment (unique SIDs are preferred), classic exam practice associated the combination “Sysprep + sysprep.inf + prompt for identity on first boot” with this choice. Unattended setup with Unattend.txt and UDF is better when you are installing fresh at the remote site, not when shipping preinstalled, tested images.

Step-by-Step Solution:

Verification / Alternative check:
Confirm that Mini-Setup runs on first boot and prompts for values. Validate that the deployed machines join the intended workgroup/domain configuration as required afterward.

Why Other Options Are Wrong:

• Unattend.txt is used for fresh installs, not for preinstalled images.
• Hard-coding names does not meet the requirement for users to enter names/keys.
• None of above is incorrect because Sysprep with sysprep.inf fits the scenario.

Common Pitfalls:
Confusing Unattend.txt with sysprep.inf; forgetting to test Mini-Setup prompts; duplicating SIDs if improper Sysprep usage is chosen (ensure best practices in real deployments).

Final Answer:
Install Windows 2000 Server; use Setup Manager to create sysprep.inf for Sysprep and run sysprep -noidgen.