Features removed or planned for replacement starting with Windows Server, version 1709
Applies To: Windows Server, version 1709
The following is a list of features and functionalities in Windows Server, version 1709 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 removed from Windows Server, version 1709
Windows Server, version 1709 contains the same features present in Windows Server 2016. However, this release does offer different installation options than Windows Server 2016 does:
- As a Semi-Annual Channel release, Windows Server, version 1709 offers only the Server Core installation option. For details, see Windows Server Semi-Annual Channel overview.
- Starting with this release, Nano Server is not available as an installable host operating system. Instead, Nano Server is available as a container operating system. See Changes to Nano Server in Windows Server, version 1709.
- Starting with this release, Server Message Block (SMB) version 1 is no longer installed by default. For details, see SMBv1 is not installed by default in Windows 10 Fall Creators Update and Windows Server, version 1709 and later versions.
Features being considered for replacement starting with subsequent releases
The following features and functionalities are being considered for replacement starting with releases after Windows Server, version 1709. Eventually, they may be completely removed from the installed product image and replaced by other features or functionality (or installable from other sources), but they are still available in this release, sometimes with certain functionality removed. You should begin planning now to employ alternate methods or the future replacement for any applications, code, or usage that depend on these features.
If you have feedback to share about the proposed replacement of any of these features, you can use the Feedback Hub app. Even though this app runs on Windows 10, you can use it to send us feedback about the Windows Server product (and documentation) as well.
IIS 6 Management compatibility
Specific features being considered for replacement are:
- IIS 6 Metabase Compatibility (Web-Metabase)
- IIS 6 Management Console (Web-Lgcy-Mgmt-Console)
- IIS 6 Scripting Tools (Web-Lgcy-Scripting)
- IIS 6 WMI Compatibility (Web-WMI)
Instead of IIS 6 Metabase Compatibility (which acts as an emulation layer between IIS 6-based metabase scripts and the file-based configuration used by IIS 7 or newer versions) you should start migrating management scripts to target IIS file-based configuration directly, by using tools such as the Microsoft.Web.Administration namespace.
You should also start migration from IIS 6.0 or earlier versions, and move to the latest version of IIS, which is always available in the most recent release of Windows Server.
IIS Digest Authentication
This authentication method is planned for replacement. Instead, you should start using other authentication methods such as Client Certificate Mapping (see Configuring One-to-One Client Certificate Mappings) or Windows Authentication (see Application Settings).
Internet Storage Name Service (iSNS)
iSNS is being considered for replacement. The Server Message Block (SMB) feature offers essentially the same functionality with additional features. See Server Message Block Overview for background information on this feature.
RSA/AES Encryption for IIS
This encryption method is being considered for replacement because the superior Cryptography API: Next Generation (CNG) method is already available. To learn more about CNG encryption, see About CNG.
Windows PowerShell 2.0
This early version of Windows PowerShell has been superseded by several more recent versions. For the best features and performance, migrate to Windows PowerShell 5.0 or later. See PowerShell Documentation for plenty of information.