Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Windows Server removed features

Full guidance and history · All guidance changes

Windows Server · Official Microsoft guidance

Observed content change

May need admin actionCheck your firewall and proxy allow lists; check whether new requirements apply to your setup; check whether a default changed for your tenant or devices.

Changed article references · 18 added · 0 removed
  • Added link: Windows Server 2028 (Preview)#tabpanel_1_ws28-preview
  • Added link: Windows Server 2028 (Preview)#tabpanel_2_ws28-preview
  • Added link: schtasks../administration/windows-commands/schtasks
  • Added link: BranchCache../networking/branchcache/branchcache
  • Added link: Configure VPN protocols../remote/remote-access/configure-vpn-protocols
  • Added link: Overview of the DirectAccess to Always On VPN migration../remote/remote-access/da-always-on-vpn-migration/da-always-on-migration-overview
  • Added link: Remote Desktop Services overview../remote/remote-desktop-services/overview
  • Added link: Should I create a generation 1 or 2 virtual machine in Hyper-V?../virtualization/hyper-v/plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v
  • Added link: Windows Server TAP teamhttps://aka.ms/WSTAP
  • Added link: .NET Framework 3.5 moves to standalone deployment in new versions of Windowshttps://devblogs.microsoft.com/dotnet/dotnet-framework-3-5-moves-to-standalone-deployment-in-new-versions-of-windows/
  • Added link: WINS removal: Moving forward with modern name resolutionhttps://support.microsoft.com/servicing/os/windows/docs/2025/11/wins-removal-moving-forward-with-modern-name-resolution
  • Added link: DirectAccess deprecation on future Windows Server releaseshttps://support.microsoft.com/servicing/os/windows/docs/2026/06/directaccess-deprecation-on-future-windows-server-releases-a-new-era-of-always-on-connectivity
  • Added link: Windows Deployment Services deprecation in the next Windows Server releasehttps://support.microsoft.com/servicing/os/windows/docs/2026/09/windows-deployment-services-deprecation-in-the-next-windows-server-release
  • Added link: L2TP and PPTP removalhttps://support.microsoft.com/servicing/os/windows/docs/2026/10/l2tp-pptp-removal-article
  • Added link: Stop using SMB1https://techcommunity.microsoft.com/blog/filecab/stop-using-smb1/425858
  • Added link: VBScript deprecation: Timelines and next stepshttps://techcommunity.microsoft.com/blog/windows-itpro-blog/vbscript-deprecation-timelines-and-next-steps/4148301
  • Added link: WMI command line (WMIC) utility deprecation: Next stepshttps://techcommunity.microsoft.com/blog/windows-itpro-blog/wmi-command-line-wmic-utility-deprecation-next-steps/4039242
  • Added link: Trusted Launch for generation 2 virtual machineswhats-new-windows-server-2028#trusted-launch-for-generation-2-virtual-machines
Changed wording view
EditedFeatures removed or no longer developed in Windows Server
[removed: Note] Windows Server long-term servicing channel (LTSC) releases have a Fixed Lifecycle Policy that includes 5 years of mainstream support and 5 years of extended support for a total lifecycle of 10 years. To learn more, see: [removed: Fixed Lifecycle Policy Lifecycle Terms and Definitions]
Before: Note Windows Server long-term servicing channel (LTSC) releases have a Fixed Lifecycle Policy that includes 5 years of mainstream support and 5 years of extended support for a total lifecycle of 10 years. To learn more, see: Fixed Lifecycle Policy Lifecycle Terms and Definitions
After: Windows Server long-term servicing channel (LTSC) releases have a Fixed Lifecycle Policy that includes 5 years of mainstream support and 5 years of extended support for a total lifecycle of 10 years. To learn more, see:
NewFeatures removed or no longer developed in Windows Server
[added: Fixed Lifecycle Policy]
Before: No saved wording on this side.
After: Fixed Lifecycle Policy
NewFeatures removed or no longer developed in Windows Server
[added: Lifecycle Terms and Definitions]
Before: No saved wording on this side.
After: Lifecycle Terms and Definitions
NewFeatures no longer in development
[added: Windows Server 2028 (Preview)]
Before: No saved wording on this side.
After: Windows Server 2028 (Preview)
NewFeatures no longer in development
[added: Important Windows Server 2028 is in preview. The feature deprecations in this tab don't mean that the features are absent from current preview builds. The features might still be available in current preview builds, and the deprecation plans can change before release.]
Before: No saved wording on this side.
After: Important Windows Server 2028 is in preview. The feature deprecations in this tab don't mean that the features are absent from current preview builds. The features might still be available in current preview builds, and the deprecation plans can change before release.
NewFeatures no longer in development
[added: Feature Explanation BranchCache BranchCache is deprecated beginning with Windows Server 2028. Identify deployments that use BranchCache to cache content from file servers, web servers, or Background Intelligent Transfer Service (BITS), and plan a transition. For more information, see BranchCache. Windows Deployment Services (WDS) server role The WDS server role is deprecated beginning with Windows Server 2028, including its role services, management tools, interfaces, and WDS-provided Preboot Execution Environment (PXE) functionality. You should inventory your WDS dependencies and plan a migration. If you use WDS-backed PXE with Microsoft Configuration Manager, migrate to the Configuration Manager PXE responder without WDS. For more information, see Windows Deployment Services deprecation in the next Windows Server release. Windows PowerShell 5.1 Windows Server 2028 deprecates Windows PowerShell 5.1. Test existing scripts, modules, and management workflows with PowerShell 7, and use the results to plan your migration. Because PowerShell 7 and Windows PowerShell 5.1 have compatibility differences, assess dependencies before migrating. For guidance, see Migrating from Windows PowerShell 5.1 to PowerShell 7. Windows Sockets Direct Windows Sockets Direct is deprecated. Beginning with Windows Server 2028, system area network (SAN) endpoint creation is disabled by default, and the feature will be removed in a later release. This change doesn't affect NetworkDirect, SMB Direct, or other Remote Direct Memory Access (RDMA) functionality. For more information, see Windows Sockets Direct Architecture.]
Before: No saved wording on this side.
After: Feature Explanation BranchCache BranchCache is deprecated beginning with Windows Server 2028. Identify deployments that use BranchCache to cache content from file servers, web servers, or Background Intelligent Transfer Service (BITS), and plan a transition. For more information, see BranchCache. Windows Deployment Services (WDS) server role The WDS server role is deprecated beginning with Windows Server 2028, including its role services, management tools, interfaces, and WDS-provided Preboot Execution Environment (PXE) functionality. You should inventory your WDS dependencies and plan a migration. If you use WDS-backed PXE with Microsoft Configuration Manager, migrate to the Configuration Manager PXE responder without WDS. For more information, see Windows Deployment Services deprecation in the next Windows Server release. Windows PowerShell 5.1 Windows Server 2028 deprecates Windows PowerShell 5.1. Test existing scripts, modules, and management workflows with PowerShell 7, and use the results to plan your migration. Because PowerShell 7 and Windows PowerShell 5.1 have compatibility differences, assess dependencies before migrating. For guidance, see Migrating from Windows PowerShell 5.1 to PowerShell 7. Windows Sockets Direct Windows Sockets Direct is deprecated. Beginning with Windows Server 2028, system area network (SAN) endpoint creation is disabled by default, and the feature will be removed in a later release. This change doesn't affect NetworkDirect, SMB Direct, or other Remote Direct Memory Access (RDMA) functionality. For more information, see Windows Sockets Direct Architecture.
NewFeatures removed
[added: Important Windows Server 2028 is in preview. The feature removals in this tab aren't confirmation that the features are absent from current preview builds. The features might still be available in current preview builds, and the removal plans can change before release.]
Before: No saved wording on this side.
After: Important Windows Server 2028 is in preview. The feature removals in this tab aren't confirmation that the features are absent from current preview builds. The features might still be available in current preview builds, and the removal plans can change before release.
NewFeatures removed
[added: Feature Explanation Windows Internet Name Service (WINS) server role WINS is removed in Windows Server 2028 after being no longer developed since Windows Server 2022. Migrate WINS-dependent clients and services to DNS-based name resolution. For more information, see WINS removal: Moving forward with modern name resolution. DirectAccess DirectAccess is removed from Windows Server 2028. Migrate existing DirectAccess deployments to Always On VPN by using a side-by-side migration. For more information, see Overview of the DirectAccess to Always On VPN migration and DirectAccess deprecation on future Windows Server releases. Point-to-Point Tunneling Protocol (PPTP) and Layer 2 Tunneling Protocol (L2TP) remote access Remote access through PPTP and L2TP is removed from Windows Server 2028. Migrate remote access connections to Internet Key Exchange version 2 (IKEv2) or Secure Socket Tunneling Protocol (SSTP). For more information, see Configure VPN protocols and L2TP and PPTP removal. Server Message Block version 1 (SMBv1) Windows Server 2028 no longer includes SMBv1. Update dependent clients, servers, and devices to use SMBv2 or SMBv3. For more information, see Stop using SMB1. VBScript Windows Server 2028 removes VBScript, so scripts and apps that depend on it stop working. Migrate administrative scripts to PowerShell and web scripts to JavaScript. For more information, see VBScript deprecation: Timelines and next steps. Windows Management Instrumentation command-line utility (WMIC) Windows Server 2028 removes the Windows Management Instrumentation Command-line (WMIC) utility, not Windows Management Instrumentation (WMI). Replace WMIC commands with PowerShell or programmatic WMI queries. For more information, see WMI command line (WMIC) utility deprecation: Next] …
Before: No saved wording on this side.
After: Feature Explanation Windows Internet Name Service (WINS) server role WINS is removed in Windows Server 2028 after being no longer developed since Windows Server 2022. Migrate WINS-dependent clients and services to DNS-based name resolution. For more information, see WINS removal: Moving forward with modern name resolution. DirectAccess DirectAccess is removed from Windows Server 2028. Migrate existing DirectAccess deployments to Always On VPN by using a side-by-side migration. For more information, see Overview of the DirectAccess to Always On VPN migration and DirectAccess deprecation on future Windows Server releases. Point-to-Point Tunneling Protocol (PPTP) and Layer 2 Tunneling Protocol (L2TP) remote access Remote access through PPTP and L2TP is removed from Windows Server 2028. Migrate remote access connections to Internet Key Exchange version 2 (IKEv2) or Secure Socket Tunneling Protocol (SSTP). For more information, see Configure VPN protocols and L2TP and PPTP removal. Server Message Block version 1 (SMBv1) Windows Server 2028 no longer includes SMBv1. Update dependent clients, servers, and devices to use SMBv2 or SMBv3. For more information, see Stop using SMB1. VBScript Windows Server 2028 removes VBScript, so scripts and apps that depend on it stop working. Migrate administrative scripts to PowerShell and web scripts to JavaScript. For more information, see VBScript deprecation: Timelines and next steps. Windows Management Instrumentation command-line utility (WMIC) Windows Server 2028 removes the Windows Management Instrumentation Command-line (WMIC) utility, not Windows Management Instrumentation (WMI). Replace WMIC commands with PowerShell or programmatic WMI queries. For more information, see WMI command line (WMIC) utility deprecation: Next …
EditedFeatures removed
… Server Core. If you need to enable the print components, you can do so by running the following cmdlet: Install-WindowsFeature Print-Server Remote Desktop Connection Broker and Remote Desktop Virtualization Host in a Server Core installation Most Remote Desktop Services deployments [removed: have] [added: colocate] these roles [removed: colocated] with the Remote Desktop Session Host (RDSH), which requires Server with Desktop Experience. To be consistent with RDSH, [removed: we're changing] [added: Microsoft changed] these roles to also require Server with Desktop Experience. These RDS roles [removed: are no longer] [added: aren't] available 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 with Desktop Experience. These roles are also included in the Desktop …
Before: … Server Core. If you need to enable the print components, you can do so by running the following cmdlet: Install-WindowsFeature Print-Server Remote Desktop Connection Broker and Remote Desktop Virtualization Host in a Server Core installation Most Remote Desktop Services deployments have these roles colocated 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. These RDS roles are no longer available 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 with Desktop Experience. These roles are also included in the Desktop …
After: … Server Core. If you need to enable the print components, you can do so by running the following cmdlet: Install-WindowsFeature Print-Server Remote Desktop Connection Broker and Remote Desktop Virtualization Host in a Server Core installation Most Remote Desktop Services deployments colocate these roles with the Remote Desktop Session Host (RDSH), which requires Server with Desktop Experience. To be consistent with RDSH, Microsoft changed these roles to also require Server with Desktop Experience. These RDS roles aren't available 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 with Desktop Experience. These roles are also included in the Desktop …

Source: Microsoft source · © Microsoft · CC BY 4.0.

Read the current Microsoft source · Link to this observation · Compare any two versions

Observation details
Observed by ChangeIntel
17 Nov 23:52 UTC
Source update metadata
17 Nov 18:35 UTC
First observed on this installation
5 Oct 17:20 UTC
Last successful check
17 Nov 23:52 UTC
Next check due
today 05:52 UTC

Observation time is not publication time, and a comparison does not establish an effective date. Full source bodies are not published; this page holds generated summaries, section headings and, as the page's license allows, Microsoft's changed wording. A documentation edit does not confirm feature availability in an environment. Article references show literal targets and labels, including relative addresses; image bytes are not captured or compared.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 01:21 UTC · 273 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current