Microsoft has announced plans to deprecate its Windows Deployment Services (WDS) server role, effective with the next release of Windows Server. This move marks a significant shift in how IT administrators will manage and deploy Windows operating systems on large networks. WDS allows for remote installation of Windows OS on dozens or hundreds of computers, making it an essential tool for many organizations.
The deprecation of WDS is not a sudden decision; Microsoft has been gradually phasing out its functionality over the past few years. In 2021, the company removed boot.wim support from WDS, and more recently, hands-free deployment was disabled by default for all customers who installed Windows updates in April 2026 or later. This change effectively restricted WDS to deploying only Windows Server or custom environments, rather than standard desktop operating systems.
The next step will be the complete removal of WDS from future versions of Windows Server. Although deprecated products are supported until they’re eventually removed, Microsoft is advising customers to begin planning their migration to alternative solutions. The company recommends using its Configuration Manager, which provides a more flexible experience for deploying Windows images. This transition is necessary because WDS will no longer receive active development or support.
It’s worth noting that the deprecation of WDS only affects the inbox WDS role and associated functionality. Microsoft Configuration Manager operating system deployment remains unaffected, but customers using WDS-backed PXE or dependent multicast should start migrating away from these dependencies. The availability and support for WDS on currently supported Windows Server versions will continue unchanged until their respective servicing lifecycles are completed.
This decision marks a significant shift in the way organizations manage and deploy Windows operating systems. As Microsoft continues to evolve its platform, it’s essential for IT administrators to stay up-to-date with these changes and plan accordingly. The recommended migration to Configuration Manager should be prioritized, especially for those currently using WDS-backed PXE or dependent multicast.
In practical terms, this means that IT teams should start exploring alternative deployment solutions and updating their strategies to accommodate the impending removal of WDS from future Windows Server releases.
Source: Bleeping Computer — 2026-09-25