The Scenario
A 100-person SA SME runs three on-premise Windows Servers (file, print, application). Each was built differently, and only one technician remembers how. You are asked to document a "gold" Windows Server build that any new technician could replicate exactly.
The Brief
Produce a complete Windows Server build documentation pack. Cover OS configuration, security baseline, patching, monitoring agents, backup agent, and post-build validation.
Deliverables
- A pre-build checklist covering: hardware/VM specs, IP plan, naming, storage layout, license keys, joining the domain, and required pre-installed roles
- A configuration document covering: time sync, regional settings, firewall rules, services hardening (disable SMBv1, disable Telnet), antivirus install, and remote management posture
- A post-build validation checklist showing exactly how a peer reviewer confirms the build matches standard (ports, services, agents, security baseline, AD integration)
- A short change-control note describing how updates to the build standard are reviewed and rolled out
Submission Guidance
A good build document is the one where two technicians produce identical servers without talking to each other. Test that hypothesis as you write: every step should be deterministic, not "configure as appropriate".
Submit Your Work
Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.