Features removed or planned for replacement starting with Windows Server, version 1903 and 1909
Applies to: Windows Server, version 1903 and 1909
The following is a list of features and functionalities in Windows Server, version 1903 and 1909 that have either been removed from the product in that release or are starting to be considered for potential replacement in subsequent releases. It is intended for IT professionals who are updating operating systems in a commercial environment. This list is subject to change in subsequent releases and might not include every affected feature or functionality.
Features we're no longer developing
We're no longer actively developing these features and may remove them from a future update. Some features have been replaced with other features or functionality, while others are now available from different sources.
If you have feedback about the proposed replacement of any of these features, you can use the Feedback Hub app.
|Feature||Instead you can use|
|Hyper-V vSwitch on LBFO||In a future release, the Hyper-V vSwitch will no longer have the capability to be bound to an LBFO team. Instead, it must be bound via Switch Embedded Teaming (SET).|
|XDDM-based remote display driver (new)||Starting with this release the Remote Desktop Services uses a Windows Display Driver Model (WDDM) based Indirect Display Driver (IDD) for a single session remote desktop. The support for Windows 2000 Display Driver Model (XDDM) based remote display drivers will be removed in a future release. Independent Software Vendors that use XDDM-based remote display driver should plan a migration to the WDDM driver model. For more information on implementing remote display indirect display driver ISVs can reach out to email@example.com.|
|UCS log collection tool (new)||The UCS log collection tool, while not explicitly intended for use with Windows Server, is nonetheless being replaced by the Feedback hub on Windows 10.|
|Key Storage Drive in Hyper-V||We're no longer working on the Key Storage Drive feature in Hyper-V. If you're using generation 1 VMs, check out Generation 1 VM Virtualization Security for information about options going forward. If you're creating new VMs use Generation 2 virtual machines with TPM devices for a more secure solution.|
|Trusted Platform Module (TPM) management console||The information previously available in the TPM management console is now available on the Device security page in the Windows Defender Security Center.|
|Host Guardian Service Active Directory attestation mode||We're no longer developing Host Guardian Service Active Directory attestation mode - instead we've added a new attestation mode, host key attestation, that's far simpler and equally as compatible as Active Directory based attestation. This new mode provides equivalent functionality with a setup experience, simpler management and fewer infrastructure dependencies than the Active Directory attestation. Host key attestation has no additional hardware requirements beyond what Active Directory attestation required, so all existing systems will remain compatible with the new mode. See Deploy guarded hosts for more information about your attestation options.|
|OneSync service||The OneSync service synchronizes data for the Mail, Calendar, and People apps. We've added a sync engine to the Outlook app that provides the same synchronization.|
|Remote Differential Compression API support||Remote Differential Compression API support enabled synchronizing data with a remote source using compression technologies, which minimized the amount of data sent across the network.|
|WFP lightweight filter switch extension||The WFP lightweight filter switch extension enables developers to build simple network packet filtering extensions for the Hyper-V virtual switch. You can achieve the same functionality by creating a full filtering extension. As such, we'll be removing this extension in the future.|