Technical Anshu
Tutorials Blog
🖥︎ Before You Install

Before You Install Windows Server 2025 Hardware Checks That Decide Everything Later

The install wizard takes half an hour, but the decisions around it — disks, RAID, firmware, the old server's backup — decide whether this server is a pleasure or a regret for the next five years. Check these before the ISO even boots.

✍️ Technical Anshu🪟 Windows Server 2025⏱️ Pre-install checklist
🎥 Watch the complete Server 2025 setup in the video — install, roles and hardening, step by step

People treat hardware checks as the boring preamble to a server setup. In truth they are the setup. Windows can be reinstalled in an afternoon; a wrong RAID layout, a dying old server whose data was never verified, or a licence surprise in month seven cannot. Work through these five checks before you install Windows Server 2025 and the rest of the project becomes routine.

Minimums on paper vs what an office actually needs
RAM2 GB min
RAM practical16 GB +
System disk32 GB min
Disk practical200 GB SSD +
FirmwareUEFI + TPM
Microsoft's documented minimums install Windows. They do not run an office. The practical column is the honest starting point.
1

Read the Documented Minimums, Then Aim Higher on Purpose

Microsoft documents Windows Server 2025 minimums of a 1.4 GHz 64-bit processor, 2 GB RAM for Desktop Experience (512 MB for Server Core) and 32 GB of disk. Those numbers mean "setup will complete", nothing more. A domain controller that also serves files and runs updates wants 16 GB RAM or more and a fast SSD for the system volume — and if the server will host virtual machines, RAM and cores should be planned per VM, not guessed.

  1. Count the jobs first: DC + DNS + DHCP + files is one load; add Hyper-V guests and the maths changes completely
  2. An SSD for the system drive is the cheapest performance decision you will ever make on a server
  3. Leave headroom. A server bought "exactly enough" is a server replaced early
2

Decide RAID and the Disk Layout Before Setup Starts

If the machine has a hardware RAID controller, the array is created in the controller setup before Windows Setup ever runs — Windows simply sees the finished volume. Changing your mind afterwards means wiping and reinstalling, so decide now: mirrored pair for the system, a separate volume or array for data, and a plan for the backup disk.

  1. RAID protects against one disk dying. It is not a backup — it happily mirrors deletions and ransomware too
  2. Put the RAID controller battery or cache health on your checklist; a degraded array is a bad foundation
  3. Write the layout down. Future you, adding a disk at midnight, will be grateful
3

Back Up the Old Server First — That Is Where the Risk Lives

Honest truth: there is nothing to back up on the new server — it is empty. Every byte at risk in this project sits on the old machine you are replacing or migrating from. Before you touch anything, take a full backup of the old server and verify it by restoring a few files. A backup that has never been test-restored is a rumour.

  1. Export or note the old server's shares, permissions, printer list and any line-of-business app data locations
  2. Keep the old server intact and powered off — not wiped — until the new one has run production for at least a week
  3. If users store files on their own PCs instead of the server, this migration will not move those files. Say so early, in writing
4

Choose Evaluation or Licensed Media Deliberately

The free evaluation edition of Windows Server 2025 runs for 180 days and is genuinely useful for a lab or a trial. The trap is forgetting the clock: an office that builds production on evaluation and discovers the expiry during a busy week has created its own emergency.

  1. Lab or learning? Evaluation is perfect, and the video series' practice setups often start there
  2. Production? Buy the licence first and install from licensed media — and keep the invoice with the server documents
  3. If evaluation is already in use, note the expiry date in the handover document and in your calendar, not just in your memory
5

Set the Firmware Up for the Features You Will Want Later

Five minutes in the UEFI setup now can save a reinstall later. Set the boot mode to UEFI, enable Secure Boot, and switch on the TPM and virtualization support in firmware. These switches matter beyond installation: the reboot-less hotpatching option for Server 2025 needs Virtualization-Based Security (VBS), which itself needs this firmware foundation.

  1. Enable the CPU virtualization option (VT-x or AMD-V) even if Hyper-V is "later" — enabling it now costs nothing
  2. Confirm the machine boots from the install media in UEFI mode, not legacy mode
  3. Update the server firmware itself if the vendor offers a stable newer release — before Windows, not after
🔴 Honest bottom line: the two regrets that follow a server for years — a cramped disk layout and a licence surprise — are both decided before the install. The installer is the easy part. Give this checklist one careful hour and the rest of the setup is just following steps.

🎥 See the Hardware Checks in the Setup Video

Watch how the machine is prepared before Windows Server 2025 goes on — disks, RAID and the first boot, live.

▶️ Watch Full Video
❓ Common Questions (FAQ)

What are the real minimum requirements for Windows Server 2025?

Microsoft documents a 1.4 GHz 64-bit CPU, 2 GB RAM for Desktop Experience and 32 GB of disk as minimums. Those are install minimums, not working specs. For a small office server running AD, DNS, DHCP and file shares, plan on 16 GB RAM and an SSD as the honest starting point.

Should I configure RAID before or after installing Windows?

Before. A hardware RAID array is created in the controller's own setup, and Windows Setup then installs onto the finished volume. Creating or restructuring an array afterwards means wiping the disks — which means reinstalling Windows and restoring everything.

Can I build my office server on the free evaluation edition?

You can install and learn on it — it is fully featured for 180 days. But production deserves a planned licence, not a countdown. If you do start on evaluation, record the expiry date in writing and buy the licence well before it arrives.

This guide is based on Technical Anshu's Windows Server 2025 complete setup video • Stuck on any step? Ask in the video comments — you will get help there 🙏