Microsoft Is Deprecating Its PXE Server. Does Your Wipe Floor Need a Server at All?

On September 21, 2026, Microsoft announced it is deprecating Windows Deployment Services (WDS), including "WDS-provided PXE boot and network bootstrap functionality." WDS is the network boot server built into Windows Server. Some erasure setups are built on it: one vendor's published PXE guide lists it as a requirement.

Nothing breaks today, and network boot isn't going away. But if your floor boots from WDS, a migration is now on your roadmap. It's also a good moment to ask a bigger question: why does wiping a drive need a server room in the first place?

---

1. What Microsoft actually announced

PXE (Preboot Execution Environment) is the firmware feature that lets a PC boot from the network instead of a disk. It needs a PXE server on the network to answer. WDS is one such server, the one that ships free with Windows Server. The deprecation covers WDS, not PXE.

If your floor boots from WDS, you have three ways forward:

1. Stay on Windows Server 2025. It's supported into the 2030s. You'll still have to move one day.
2. Swap the PXE server. Linux-based PXE servers, your erasure vendor's own PXE server if it has one, or Microsoft Configuration Manager, which can run "a PXE responder on a distribution point without Windows Deployment Service."
3. Move to HTTP(S) Boot. Newer PCs can boot over a web connection instead of PXE. Microsoft says it "may be an alternative for applicable deployment solutions." It depends on your firmware and network supporting it.

Each of these keeps network boot running. None of them removes the server.

2. Where the infrastructure comes from

Wiping or testing one machine needs nothing but that machine. The infrastructure appears when you want to manage a whole floor: start jobs, see progress, and keep every record in one place. The traditional setup has three parts:

• A way to boot the tool. Either a USB stick per bench, or a PXE server so machines boot the tool over the network.
• A management server. It collects results, stores reports, and gives supervisors one view of the floor.
• The network in between. Switches, cabling, DHCP, and often a separate network segment for the benches.

Network boot gets rid of the USB sticks, and it asks for the most in return. One erasure vendor's published PXE guide lists:

That's before licensing, backups, patching, and the person who knows how it all fits together.

3. Why it turns into a bottleneck

Infrastructure is a fixed cost that doesn't flex with volume, and ITAD volume is anything but steady.

Volume arrives in waves. Ahead of Windows 10's end of support in October 2025, Canalys estimated it "could result in about 240 million personal computers (PCs) being disposed." A refresh wave means more benches, now. On a network-boot floor, every new bench is also a port on the boot network and one more machine for the server to serve.

Second sites copy the stack. A boot server in your building only serves your building. A second location, or a job at a customer's site, means another server, another boot network, or a VPN back to the first one.

It has to be kept safe. Microsoft's own PXE guidance is blunt: "The PXE protocol isn't secure." It tells you to keep the PXE server and its clients "on a physically secure network." The server itself needs patching too. In April 2026, Microsoft turned off a WDS automation feature (hands-free deployment) by default after a vulnerability, CVE-2026-0386: its setup file, which can hold credentials, was sent over an unauthenticated channel that an attacker on the same network could intercept.

The tools underneath keep moving. Microsoft retired its Deployment Toolkit (MDT) in January 2026, and now it's deprecating WDS. If your boot chain depends on either, a platform change is coming whether you planned one or not.

4. How floors deal with it today

Broadly, operators take one of three routes:

Microsoft's own direction for Windows deployment leans the same way. Its MDT retirement notice tells customers to consider "Windows Autopilot, which provides cloud‑driven, zero‑touch provisioning."

5. How reCore does it

By default, reCore takes the third route. Here's what that means in practice, checked against the code.

The machine is the station. You don't need a dedicated wipe PC. The device you're processing boots from a reCore USB stick into a Linux environment that runs from the stick. Nothing is installed on the machine. It boots on newer and older PCs alike, including ones with Secure Boot turned on.

It goes online like a web browser. Once a technician signs in, the station opens an encrypted connection to reCore's cloud, the same way a browser opens a website. If a computer on your network can browse the web, the station can usually connect, over cable or Wi-Fi. There's nothing to change on your firewall and no VPN. After first setup, a saved PIN signs in automatically at boot.

The work happens on the machine. Diagnostics, stress tests and wipes run on the device's own hardware. The cloud receives results; it doesn't do the work. If the internet drops mid-wipe, the wipe carries on. Results are saved in an encrypted local database and uploaded when the connection comes back.

The floor is a web page. Every signed-in station shows up live on the dashboard. From there you can:

• start diagnostics or a stress test on one machine or many;
• start a wipe on a single drive, or on drives across the whole floor;
• grade devices from the office while technicians work the benches;
• approve wipe certificates, with a rule that the approver can't be the person who ran the wipe.

Remote data wipe is included in every plan.

Sticks are registered, and you can cut one off. The first time a stick is set up, an admin from your organization signs in on it. If a stick goes missing, revoke it from the dashboard and its next sign-in is refused. The dashboard also shows which version each station runs. Stations check for updates at boot and apply them on the next boot.

Network boot, if you want it. Some floors would rather not handle USB sticks at all, and some sites can't connect to the internet. For them, reCore offers network boot on Linux or Windows, on request. It can stay connected to reCore's cloud, or run as a completely offline setup with no internet at all. Either way that means equipment on your site, which we set up with you. It's an option for floors that want it, not a requirement to get started.

6. What you still need

"No infrastructure" only means something if we list what's left. For the default setup:

What you don't need: a boot server, a management server, a separate boot network, a VPN, or anyone to patch them. A second site is another box of USB sticks, not another server.

Network boot and offline setups are different: they run on equipment at your site, and we size that with you.

Conclusion

Microsoft deprecating WDS won't stop anyone's floor this year, or for years. Floors that rely on it will move to another PXE server, and that's fine. But a boot server is something you maintain, secure and eventually migrate for as long as you run it. The wipe itself only ever needed the drive and the machine it sits in. Everything else is about seeing and proving the work, and that part no longer has to live in your building. If you'd still rather network-boot, or keep a site fully offline, that's your choice to make, not a cost you pay to get started.

See cloud management and remote wipe, or read how reCore chooses and verifies a wipe method per drive.

---

Sources

• Microsoft, Windows Deployment Services (WDS) deprecation in the next Windows Server release, September 21, 2026.
• Microsoft Learn, Windows Deployment Services (WDS) boot.wim support, updated September 2026.
• Microsoft Learn, Windows Server 2025 lifecycle.
• Microsoft Learn, Use PXE for OSD over the network (Configuration Manager).
• Microsoft, WDS Hands-Free Deployment Hardening Guidance related to CVE-2026-0386.
• Microsoft Learn, MDT release notes (retirement notice).
• Canalys estimate of 240 million PCs, as reported by Reuters in The Irish Times, December 21, 2023.