Windows Deployment Services deprecation set for next Server release

Microsoft has announced that the Windows Deployment Services (WDS) server role will be deprecated beginning with the next release of Windows Server, the version that will succeed Windows Server 2025. WDS is a revised version of Remote Installation Services (RIS), a tool that lets IT administrators remotely install Windows operating systems on fleets of dozens or hundreds of computers over a network. Once WDS is deprecated in that next version, Microsoft says it will stop active development of the role and plans to retire and remove it completely. No date for the eventual removal has been published, but the role will continue to work on all currently supported Windows Server releases until that time.

The company has already been winding down parts of WDS. It partially deprecated the role by removing boot.wim support in 2021 and later removed hands-free deployment in January 2026. Boot.wim is a Windows image file used to start a computer into Windows Setup or a recovery environment, and hands-free deployment let administrators run installations without manually answering prompts. That hands-free functionality is now disabled by default for all customers who installed the April 2026 Windows updates or any subsequent ones. After those changes, Microsoft stopped officially supporting the deployment of standard desktop operating systems using its native setup engine starting with Windows 11. WDS was restricted to deploying Windows Server or booting custom deployment environments.

In the early notice published this week, Microsoft described exactly what the deprecation covers. "This includes the inbox WDS role, WDS services, management tools and interfaces, and WDS-provided Preboot Execution Environment (PXE) boot functionality," the company said. The inbox role means the version of WDS that is built into Windows Server, rather than a separate download. PXE boot is the mechanism that lets a computer load a network-based installer before its own operating system starts. Microsoft added that deprecated products are supported until they are eventually removed from a future OS version, and that while deprecated, WDS will continue to work on all currently supported Windows Server versions according to their published servicing lifecycles. The announcement does not change WDS availability or support on those releases.

For organizations still using WDS, Microsoft stressed that the inbox WDS server role and related functionality remain available on all currently supported Windows Server releases, including Windows Server 2025 and earlier. Products from other vendors and independent PXE implementations that do not depend on WDS are not affected. Microsoft Configuration Manager operating system deployment is also not affected. However, the company warned customers to begin migrating Configuration Manager environments that still use WDS-backed PXE or WDS-dependent multicast away from those WDS dependencies. Multicast is a network feature that lets one server send the same image to many computers at once, reducing network load.

Microsoft advised customers to start planning their migration to alternatives such as Microsoft Configuration Manager, which the company says provides a more flexible experience for deploying Windows images. For IT teams managing Windows Server fleets, this is a long-term planning signal rather than an immediate outage. The current role keeps working on supported server versions, but new deployments should avoid building on a deprecated component. Businesses that rely on in-house Windows deployment workflows should audit which parts of their process depend on WDS and test replacements before the role is eventually removed. The next Windows Server release has not been named, but Microsoft's advance notice gives administrators time to prepare. The deprecation does not affect the underlying Windows Server operating system or other Microsoft deployment options; it is specific to the WDS server role and its associated PXE and multicast pieces.

Planning a migration from Windows Deployment Services can be complex because PXE boot and multicast touch the network, the server image store, and the client machines. AEU-I, the security-first IT and infrastructure consulting arm of AEU Group, offers help for teams assessing their current deployment workflows and preparing a controlled transition away from WDS dependencies. This kind of proactive planning reduces the risk of being caught short when Microsoft eventually removes the role from a future version of Windows Server.