Skip to main content
IT KORR
IT KORRKeeping Organizations Reliable & Resilient

Infrastructure & Networking · Resource

Server Build Checklist

A checklist for provisioning a new server consistently — from pre-build planning through OS build, post-build configuration, and validation.

IT KORR Knowledge Center

Server Build Checklist

A checklist for provisioning a new server consistently — from pre-build planning through OS build, post-build configuration, and validation.

Pre-Build

  • Naming convention is followed and the name does not conflict with an existing or reserved name.
  • IP address and DNS record are reserved and documented in IPAM before the build begins.
  • Hardware or virtual resource allocation (CPU, memory, storage, network) is confirmed appropriate for the intended workload.
  • Approval or change ticket exists for the new server where change management applies.

OS Build

  • Operating system is patched to the current baseline before the server is placed into service.
  • Security hardening baseline is applied (e.g., CIS benchmark or internal standard) — unnecessary services and default accounts disabled.
  • Monitoring agent is installed and confirmed reporting to the central monitoring system.
  • Time synchronization (NTP) is configured against an internal or trusted external source.

Post-Build

  • Backup job is configured and a first backup is run and verified successful before go-live.
  • Documentation is updated — device inventory, IPAM record, and any relevant runbook reflect the new server.
  • Access and permissions are configured per least privilege — only the accounts and groups that need access have it.
  • Antivirus/endpoint protection (where applicable) is installed and reporting.

Validation

  • Network connectivity is tested from the expected client/application paths, not just a local ping.
  • Monitoring is confirmed actively reporting metrics and alerting correctly for the new server.
  • Application or service running on the server is smoke-tested before handoff.
  • The build is logged in the change log with date, purpose, and owner.

Related Resources

  • Virtualization Fundamentals — /knowledge-center/infrastructure/infrastructure-networking/virtualization-fundamentals
  • Infrastructure Monitoring Fundamentals — /knowledge-center/infrastructure/infrastructure-networking/infrastructure-monitoring-fundamentals

This document is a starting-point resource, not legal or compliance advice. Review it against your organization's actual systems before adoption — see the full Infrastructure & Networking Hub for the reasoning behind each recommendation, or browse the full Resource Library.

If you would rather not do this by hand

Most teams fill a template like this in once and never again.

Documentation decays the day after it is written. The work is keeping it true as the network changes, which is usually what an internal team has no time for.

Or talk about splitting this with your team — the enquiry form opens with “Co-Managed IT” selected, and you can change it.

Infrastructure & Networking

Need Your Environment Documented and Maintained — Not Just a Template?

IT KORR can assess your infrastructure documentation, network architecture, and operational readiness, and take on the ongoing maintenance a template alone can't provide.

No commitment required — a person reads every enquiry and replies directly, or call (848) 200-9669 now.