"Deprecated products are supported until they are eventually removed from a future OS version," Microsoft said.
Microsoft's deprecation decision and scope
Microsoft has announced it will deprecate the Windows Deployment Services (WDS) server role beginning with the next Windows Server release. The company said that after deprecation it will stop active development of WDS and "plans to retire and remove it completely." The announcement, published earlier this week, specifies that the deprecation covers the inbox WDS server role and associated functionality on future Windows Server versions.
What WDS is, and the changes that led here
WDS is a revised version of Remote Installation Services (RIS) that "lets IT administrators remotely install Windows operating systems on fleets of dozens or hundreds of computers over a network." The product has already been partially deprecated over several years: Microsoft removed boot.wim support in 2021 and removed hands-free deployment in January 2026. The hands-free capability is now disabled by default for all customers who installed the April 2026 Windows updates or any subsequent ones.
Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleWhat WDS will and will not do going forward
Microsoft says the deprecation includes "the inbox WDS role, WDS services, management tools and interfaces, and WDS-provided Preboot Execution Environment (PXE) boot functionality." The company also notes that, following earlier changes, it stopped officially supporting the deployment of standard desktop operating systems using its native setup engine starting with Windows 11, and has restricted WDS to deploying Windows Server or booting custom deployment environments.
Microsoft emphasized that while WDS is deprecated it will "continue to work on all currently supported Windows Server versions according to their published servicing lifecycles." Specifically, the inbox WDS server role and associated WDS functionality remain available on all currently supported Windows Server releases (Windows Server 2025 and earlier).
Impact on Microsoft Configuration Manager, non‑Microsoft products, and PXE
Microsoft stated plainly that "Microsoft Configuration Manager operating system deployment is not being affected." At the same time the company advised a migration path: "However, begin migrating Configuration Manager environments that still use WDS-backed PXE or WDS-dependent multicast away from those WDS dependencies." The vendor also noted that non‑Microsoft deployment products and independent PXE implementations that don't depend on WDS are not affected by this deprecation.
What this means for IT administrators, Configuration Manager operators, and independent PXE vendors
- IT administrators: If your environment still uses the inbox WDS role to image desktops or servers, the deprecation means you should plan now for alternatives because Microsoft will eventually remove WDS from a future OS version. Existing WDS installations will continue to function on supported Windows Server releases until those operating systems reach end of servicing.
- Configuration Manager operators: Your operating system deployment tools are not being disabled, but Microsoft has explicitly advised beginning migrations for Configuration Manager environments that rely on WDS-backed PXE or WDS-dependent multicast.
- Independent PXE and third‑party deployment vendors: Your products are unaffected provided they do not depend on WDS. The deprecation does not apply to non‑Microsoft deployment products or independent PXE implementations that do not rely on WDS functionality.
Timing, practical next steps, and the final word
The deprecation begins with the next Windows Server release; Microsoft has not attached a specific OS-version date for the removal beyond saying deprecated products "are supported until they are eventually removed from a future OS version." Practically, organizations using WDS-backed PXE or WDS-dependent multicast should inventory deployments, validate whether they rely on inbox WDS components (services, management tools, or WDS-provided PXE), and plan migrations to alternatives such as Microsoft Configuration Manager or independent PXE solutions that do not depend on WDS.
Microsoft's guidance is concrete: "begin migrating Configuration Manager environments that still use WDS-backed PXE or WDS-dependent multicast away from those WDS dependencies." For many administrators that sentence converts the announcement from advisory to action item. The clock for change is set by operating‑system servicing timelines and the unspecified future release where WDS will be removed; organizations that still depend on the inbox WDS role will need to move before that removal to avoid disruption.
Source: BleepingComputer — Microsoft plans to deprecate Windows Deployment Services
