Features removed or planned for replacement starting with Windows Server, version 1803
Applies to: Windows Server, version 1803
Each release of Windows Server adds new features and functionality; we also occasionally remove features and functionality, usually because we've added a better option. Here are the details about the features and functionalities that we removed in Windows Server, version 1803.
- You can get early access to Windows Server builds by joining the Windows Insider program - this is a great way to test feature changes.
- Have questions about other releases? Check out Features removed or planned for replacement in Windows Server.
The list is subject to change and might not include every affected feature or functionality.
Features we removed in this release
We've removed the following features and functionalities from the installed product image in Windows Server, version 1803. Applications or code that depend on these features won't function in this release unless you use an alternate method.
|Feature||Instead you can use...|
|File Replication Service||File Replication Services, introduced in Windows Server 2003 R2, has been replaced by DFS Replication. You need to migrate any domain controllers that user FRS to DFS Replication with SYSVOL.|
|Hyper-V Network Virtualization (HNV)||Network Virtualization is now included in Windows Server as part of the Software Defined Networking (SDN) solution, which also includes the Network Controller, Software Load Balancing, User-Defined Routing, and Access Control Lists.|
Features we're no longer developing
We are 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.
Please note that some of the features and roles described below are not included in the Server Core installation option, which is provided in Windows Server, version 1803. They are present in the Server with Desktop Experience installation option, which we last released with Windows Server 2016 and will release again in Windows Server 2019.
If you have feedback about the proposed replacement of any of these features, you can use the Feedback Hub app.
|Feature or role||Instead you can use...|
|Business Scanning, also called Distributed Scan Management (DSM)||The Scan Management functionality was introduced in Windows Server 2008 R2 and enabled secure scanning and the management of scanners in an enterprise. We're no longer investing in this feature, and there are no devices available that support it.|
|IPv4/6 Transition Technologies (6to4, ISATAP, and Direct Tunnels)||6to4 has been disabled by default since Windows 10, version 1607 (the Anniversary Update), ISATAP has been disabled by default since Windows 10, version 1703 (the Creators Update), and Direct Tunnels has always been disabled by default. Please use native IPv6 support instead.|
|MultiPoint Services||We're no longer developing the MultiPoint Services role as part of Windows Server. MultiPoint Connector services are available through Feature on Demand for both Windows Server and Windows 10. You can use Remote Desktop Services, in particular the Remote Desktop Services Session Host, to provide RDP connectivity.|
|Offline symbol packages (Debug symbol MSIs)||We're no longer making the symbol packages available as a downloadable MSI. Instead, the Microsoft Symbol Server is moving to be an Azure-based symbol store. If you need the Windows symbols, connect to the Microsoft Symbol Server to cache your symbols locally or use a manifest file with SymChk.exe on a computer with internet access.|
|Remote Desktop Connection Broker and Remote Desktop Virtualization Host in a Server Core installation||Most Remote Desktop Services deployments have these roles co-located with the Remote Desktop Session Host (RDSH), which requires Server with Desktop Experience; to be consistent with RDSH we're changing these roles to also require Server with Desktop Experience. We're no longer developing these RDS roles for use in a Server Core installation. If you need to deploy these roles as part of your Remote Desktop infrastructure, you can install them on Windows Server 2016 with Desktop Experience.
These roles are also included in the Desktop Experience installation option of Windows Server 2019. You can test them in the Windows Insider build of Windows Server 2019 – just be sure to choose the LTSC image.
|RemoteFX vGPU||We're developing new graphics acceleration options for virtualized environments. You can also use Discrete Device Assignment (DDA) as an alternative.|
|Software Restriction Policies in Group Policy||Instead of using the Software Restriction Policies through Group Policy, you can use AppLocker or Windows Defender Application Control to control which apps users can access and what code can run in the kernel.|
|Storage Spaces in a Shared configuration using a SAS fabric||Deploy Storage Spaces Direct instead. Storage Spaces Direct supports the use of HLK-certified SAS enclosures, but in a non-shared configuration, as described in the Storage Spaces Direct hardware requirements.|
|Windows Server Essentials Experience||We're no longer developing the Essentials Experience role for the Windows Server Standard or Windows Server Datacenter SKUs. If you need an easy-to-use server solution for small-to-medium businesses, check out our new Microsoft 365 for business solution, or use Windows Server 2016 Essentials.|