# Server hardware and Windows Server: ECC, NIC teaming, iSCSI and IPMI

> The hardware features that actually change how Windows Server behaves, and where consumer hardware stops being adequate.

**Tested on**

- Build: 26100.33650
- Edition: Server 2025 / 2022
- Architecture: x64
- Evidence: E1
- Verified: 2026-10-29

## The short answer

Windows Server installs on consumer hardware. What it will not do on consumer hardware is behave like a server:

- **ECC memory** — silently corrects bit errors that would otherwise corrupt data;
- **redundant NICs** — a team survives a cable or switch port failure;
- **out-of-band management** — you can fix it without being in the room;
- **hot-swap bays + battery-backed RAID** — replace a disk without a shutdown;
- **redundant PSUs** — a power supply failure is an event, not an outage.

None of these are required. All of them are why servers cost more.

## ECC, briefly

ECC memory requires a platform that supports it: server CPUs/boards for RDIMM, some workstation boards for ECC UDIMM. Windows gives no toggle — the correction happens in hardware.

On Windows Server, corrected errors can surface through WHEA and the vendor's management tool. Do not expect a consumer board to report them. See [ECC and WHEA](https://winbook.fyi/en/hardware/ram/ecc-whea/).

## NIC teaming

Two physical NICs in a team provide either **failover** (one dies, traffic continues) or **aggregation** (more throughput), depending on the mode and the switch configuration.

```powershell
Get-NetAdapter | Select-Object Name,Status,LinkSpeed,MacAddress
Get-NetLbfoTeam -ErrorAction SilentlyContinue
```

Key operational points:

- **Switch-independent** teaming needs no switch config; **LACP** does, and both sides must agree.
- Teaming does not make a single TCP stream faster; it raises aggregate throughput and resilience.
- Virtual switch + teaming + Hyper-V has its own rules — do not stack them without reading the Hyper-V networking guidance.

## iSCSI and storage networking

Windows Server can be both an iSCSI target and initiator:

- **iSCSI Target Server** role turns a Windows box into a SAN for other hosts.
- **iSCSI initiator** connects a server to a SAN LUN.

Practical requirements: dedicated NICs or VLANs, jumbo frames consistently configured end to end, and MPIO if you want redundancy. A single-path iSCSI LUN is a single point of failure regardless of RAID underneath.

## IPMI / iDRAC / iLO

Out-of-band management is the difference between "I drove to the office" and "I rebooted it from my phone".

- It has its own network interface (often shared or dedicated).
- **Put it on a management VLAN**, never exposed to the internet.
- Change default credentials before the machine sees a network.
- Firmware updates for the BMC are separate from BIOS updates.

> **Danger: Never expose a BMC to the internet**
>
> Baseboard management controllers have a long history of vulnerabilities and are frequently unpatched. They also sit below the OS, so host firewalls do not protect them. Management VLAN or VPN only.

## Where consumer hardware is fine

- **Lab and test** servers, especially ephemeral ones.
- **Single-role file/print** boxes with backups.
- **Hyper-V lab hosts** where you accept the risk.

Where it is not fine: anything holding the only copy of data, anything with an uptime commitment, anything where a silent bit flip matters.

## Minimum server-class build

| Part | Server-class | Consumer equivalent | Risk |
|---|---|---|---|
| RAM | ECC RDIMM/UDIMM | non-ECC | silent corruption |
| NIC | 2× server NICs | 1× Realtek | single point of failure |
| Storage | HBA/RAID + hot swap | SATA + single SSD | no redundancy |
| PSU | 2× redundant | 1× | outage on failure |
| Management | IPMI/iDRAC/iLO | none | on-site required |

## Related

- [Used servers for a homelab](https://winbook.fyi/en/hardware/homelab/used-server/)
- [ECC and WHEA](https://winbook.fyi/en/hardware/ram/ecc-whea/)
- [Server evaluations](https://winbook.fyi/en/downloads/server/)

## Lab boundary

E1. Requirements are documented by Microsoft; nothing here was measured on server hardware. The lab has no ECC or BMC to test.

## Sources

- [Microsoft Learn — Windows Server hardware requirements](https://learn.microsoft.com/en-us/windows-server/get-started/hardware-requirements)
- [Microsoft Learn — iSCSI Target Server](https://learn.microsoft.com/en-us/windows-server/storage/iscsi/iscsi-target-server)
- [Microsoft Learn — Hyper-V host hardware requirements](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/host-hardware-requirements)

---

Source: https://winbook.fyi/en/hardware/homelab/server-hardware/