3.1.1. OS Installation Methods
💡 First Principle: Installation methods exist on a spectrum from most manual (GUI from local media) to most automated (scripted network deployment). As scale increases, manual methods become bottlenecks—automation is how you maintain consistency across dozens or hundreds of servers.
Installation Method Reference
| Method | Description | Best For |
|---|---|---|
| GUI (Graphical) | Standard wizard-based installation | Single server, initial setup |
| Core (Server Core) | Command-line only, no GUI | Security-hardened servers, reduced attack surface |
| Bare metal | Installing directly on physical hardware | Physical server deployment |
| Virtualized | Installing into a VM | Development, test, flexible deployment |
| Remote | Installing via OOB management virtual media | Servers without physical media access |
| Unattended/Scripted | Automated installation with answer files | Large-scale deployments, consistency |
| Network (PXE boot) | Boots from network, installs from server | Centralized deployment, diskless environments |
| Optical/USB/Embedded | Traditional physical media | Small environments, recovery scenarios |
Scripted/Unattended Installations
Unattended installations use answer files (Windows: unattend.xml via Windows System Image Manager; Linux: Kickstart or Preseed) that pre-answer all installation prompts. Combined with WDS (Windows Deployment Services) or similar tools, this enables:
- Consistent, repeatable deployments (every server gets identical base configuration)
- Additional drivers injected at installation time
- Additional applications and utilities installed automatically
- Patches applied during initial setup
- Bootstrap scripts that configure the server after OS installation completes
PXE Boot
PXE (Preboot Execution Environment) allows servers to boot from the network rather than local media. The server broadcasts a DHCP request, receives network boot parameters, downloads a bootstrap image, and begins installation. Requirements: a PXE-capable NIC, a DHCP server configured with PXE options, and a deployment server hosting the OS image.
⚠️ Exam Trap: Server Core is not a stripped-down version of the OS—it has nearly the same functionality as the full GUI version without the graphical shell (only a few shell-dependent roles, such as Remote Desktop Session Host, are unavailable). You manage it via command line (PowerShell, cmd) or remotely via tools like Server Manager or RSAT. The reduced attack surface comes from having fewer components installed, not reduced capability.
Reflection Question: An IT team needs to deploy 200 identical servers for a new data center. Each must have the same OS version, configuration settings, and initial software packages. Which installation method is most appropriate, and why?
