Windows Deployment Services (WDS) is Microsoft’s server-side role for installing Windows over the network, using PXE boot and server-hosted images instead of CD or DVD media. Whether it still works for a given job depends on the Windows version and the boot image you use. Microsoft’s current support page blocks some WDS workflows outright, so the answer is no longer a single yes or no.
What Windows Deployment Services is
Microsoft Learn defines WDS in its About the Windows Deployment Services API page (last updated 2023-04-04) as: “Windows Deployment Services (WDS) is a suite of components that enable the deployment of Windows operating systems, particularly Windows Vista and later and Windows Server 2008 and later.” The same documentation describes WDS as a way to set up new computers through network-based installation. Source: About the Windows Deployment Services API.
As an Amazon Associate I earn from qualifying purchases.
Microsoft’s WDS overview describes the service as the revised version of Remote Installation Services (RIS). The practical benefit it names is that an administrator does not have to visit each computer or install from CD or DVD media. WDS is therefore best understood as the successor to RIS within Microsoft’s own deployment lineup, not a separate product category.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What WDS does in practice
In day-to-day terms, WDS supplies two things on the server side:
#1 Best Overall
- 3.5 Inch Hot Plug Hard Drive PowerEdge T340 Tower Server Chassis
- Microsoft Windows Server 2019 Standard Operating System
- Processors: Intel Xeon E-2124 Quad-Core 3.3GHz 8MB CPU, Up To 4.3GHz Turbo
- Memory: 32GB (2 x 16GB) DDR4 PC4-21300 2666MHz Unbuffered Memory
- Hard Drive: 8TB (4 x 2TB) 7.2K RPM 6Gb/s SATA 3.5 Inch HDDs in RAID
- Network installation of Windows images. Client computers boot over the network and receive a Windows installation from a server-hosted image store.
- PXE boot services. WDS provides the network boot side of the process, so a PXE-capable client can start into a boot image that the server offers.
Microsoft also documents programmatic APIs for some WDS components and for custom PXE providers. These are specialized development interfaces, and most administrators deciding whether WDS fits their environment will not need them.
Current support: which boot workflows still work
The key distinction is between the WDS role and the boot image used to start Windows Setup. Microsoft’s Windows Deployment Services (WDS) boot.wim support page (last updated 2026-09-21) classifies workflows as follows.
Rank #2
- Windows server license is not included
| Scenario | Status per Microsoft’s support page | Alternative path Microsoft names |
|---|---|---|
Windows 11 deployed with the installation-media boot.wim through WDS |
Unsupported and blocked | Custom boot image over PXE, or Windows Setup run from a network share |
Windows Server 2022 deployed with the installation-media boot.wim |
Deprecated; shows a nonblocking warning | Custom boot image over PXE, or Windows Setup run from a network share |
Later Windows Server releases deployed with the installation-media boot.wim |
Blocked in the documented scenarios | Custom boot image over PXE, or Windows Setup run from a network share |
| WDS PXE boot with a custom boot image (for example, MDT or Configuration Manager) | Microsoft states these workflows can continue | Not applicable |
The blocked case is narrow. It concerns using the boot.wim file from Windows installation source media to launch Windows Setup in WDS mode. It does not mean all PXE booting is blocked, and it does not mean every imaging workflow built on WDS has stopped working. Because the support status depends on the operating system and the boot image, avoid describing WDS with a blanket “works” or “does not work.”
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Deprecation of the WDS role
Separate from the workflow restrictions above, Microsoft states that WDS is deprecated beginning with the Windows Server release after Windows Server 2025. The notice covers the inbox WDS role, its services, management tools and interfaces, and WDS-provided PXE boot functionality. Microsoft recommends planning a migration to alternatives such as Configuration Manager.
Rank #3
- MODEL P74439-005: Compact and affordable HPE ProLiant MicroServer Gen11 powered by Intel Pentium Gold G7400 3.7GHz processor, ideal for file sharing, NAS, and basic business workloads
- READY OUT OF THE BOX: Includes 16GB DDR5 UDIMM memory (expandable to 128GB), one 1TB SATA 6G Business Critical HDD, embedded Intel VROC SATA, dedicated iLO-M.2 port kit, 180w external power adapter and 1/1/1 warranty for dependable plug-and-play server operation
- WHISPER-QUIET & SPACE-SAVING: Ultra-compact mini tower design fits easily in small office spaces; supports wall, flat, or vertical placement for deployment flexibility
- INTEGRATED REMOTE MANAGEMENT: Comes with HPE iLO 6 and embedded TPM 2.0 for secure, license-free remote server administration through shared port access
- EXPANDABLE DESIGN: Two PCIe slots (including PCIe 5.0) and four LFF-NHP drive bays provide robust options for storage and component scalability. Features new MR408i-p controller support for enhanced storage performance
Hands-free deployment change
Microsoft’s page also says that starting with the April 2026 release, hands-free deployment functionality is no longer supported by default across supported platforms. It directs administrators to separate hardening guidance related to CVE-2026-0386. This change applies to the documented hands-free scenario and should not be extended to every unattended installation method.
Prerequisites for a WDS deployment
Microsoft’s Windows Server 2012 WDS Getting Started Guide lists the following requirements for the integrated configuration of Deployment Server plus Transport Server:
Rank #4
- This Certified Refurbished product is tested and certified to look and work like new. The refurbishing process includes functionality testing, basic cleaning, inspection, and repackaging. The product ships with all relevant accessories, a minimum 90-day warranty, and may arrive in a generic box. Only select sellers who maintain a high-performance bar may offer Certified Refurbished products on Amazon.com.
- Dell Optiplex 3050 SFF Desktop computer PC, Intel Quad Core i5-6500 up to 3.6GHz, 16GB DDR4, 256GB SSD
- Includes: USB Keyboard & Mouse, USB WiFi adapter, Microsoft office 30 days free trail.
- Port: Front: USB 3.0(2), USB 2.0(2); Rear: DP, HDMI, USB 3.0(2), USB 2.0(2), RJ-45.
- Support 4K (3840x2160) Dual display, makes it easy to connect two monitors at the same time, and you can expand working Windows, mirror content, or expand a single window across multiple monitors.
- Membership in Active Directory Domain Services, or the server acting as a domain controller.
- A working DHCP server with an active scope.
- Working DNS.
- An NTFS volume for image storage.
The same guide also describes a Transport Server-only configuration and a standalone WDS setup, which have different requirements. Treat the list above as the requirements for that integrated Windows Server 2012 layout, not as universal rules for every role arrangement or current server version.
WDS within a larger deployment stack
Microsoft’s OSD infrastructure requirements for Configuration Manager explains that WDS can perform PXE boot for Configuration Manager distribution points. It also states that Configuration Manager can enable PXE without WDS. WDS is therefore one possible component in an imaging and management stack, not necessarily the whole solution.
Alternatives and migration checkpoints
For installation-media boot.wim workflows that are blocked, deprecated, or unsupported, Microsoft recommends deployment tools such as Configuration Manager, or a non-Microsoft solution that uses a custom boot image. MDT appears in Microsoft’s WDS guidance as an example of a custom-boot-image workflow. No single alternative fits every organization, so compare the following before deciding:
- Boot workflow: whether the chosen tool uses installation-media
boot.wim, a custom boot image, or a network-share setup path. - Target OS support: the exact Windows client and Windows Server versions you deploy, checked against Microsoft’s blocked, deprecated, and supported cases.
- PXE implementation: WDS-backed PXE versus a Configuration Manager PXE responder that does not depend on WDS.
- Management scope: a basic network installation service versus a broader deployment-management platform. Confirm the feature set of the product you choose rather than assuming equivalence.
- Infrastructure and migration effort: directory, DHCP, DNS, image storage, and existing deployment investments.
Start with the operating system versions and boot images you actually use. Those two inputs determine whether a WDS workflow is still supported, and they set the scope of any migration.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
