3.1. Installing Server Operating Systems
💡 First Principle: How you install a server OS determines your deployment speed, consistency, and recovery options. A manual GUI installation is fine for one server; it's completely impractical for fifty. The installation method you choose is an architectural decision with long-term consequences for operational scalability.
The exam tests installation methods not as trivia but as scenario decisions: "given a scenario, which installation method is most appropriate?" The answer depends on scale, network access, the target environment (physical vs. virtual), and whether you need repeatability.
⚠️ Common Misconception: VM cloning and template deployment are equivalent. They are not. Cloning creates an exact copy of a VM including its computer name, machine-account state, and activation—deploying multiple un-sysprepped clones into a Windows domain produces duplicate machine identities, which causes domain-join conflicts and inconsistent Group Policy behavior. Template deployment uses a sysprepped image that strips machine-specific identity so each deployment gets a unique computer name (and SID) at first boot.
