Microsoft announced Windows Server 2028 at Ignite 2026 on November 17, 2026, and put the release into public preview the same day as Windows Server Insider Preview build 29706. Two decisions define the release for administrators. Server Core now installs in a hardened state, with hundreds of security settings active from first boot. Microsoft has also listed the features that leave the platform, including the WSUS server role, SMBv1, VBScript, WMIC, DirectAccess, and legacy BIOS boot.
Both decisions point the same way. Protocols, authentication methods, and scripts that work on Windows Server 2025 may need changes before they run on the new release. Microsoft has not published a general availability date, and the preview builds are not intended for production use.
1- Public Preview Arrives as Build 29706
Build 29706 is a preview of the next Long-Term Servicing Channel (LTSC) release of Windows Server and the first build to carry the Windows Server 2028 name. It includes the Datacenter and Standard editions, each with the Desktop Experience and Server Core installation options, and an Azure Edition image for virtual machine evaluation only. The preview expires on October 15, 2027.
Microsoft does not support upgrades from preview builds older than 29531 and recommends a clean installation. Organizations that want earlier access and direct contact with the engineering team can apply to the Windows Server Technology Adoption Program (TAP).
2- Server Core Now Installs Hardened
Until now, Windows Server shipped with compatibility as the default, and hardening was a task administrators completed after setup by applying the security baseline or their own scripts. A newly deployed server stayed in a weaker state until that work was done. Windows Server 2028 reverses the order. A new Server Core installation starts from the hardened configuration, and administrators relax only the settings a workload requires.
Microsoft says the settings align with the CIS Benchmarks and the DISA STIG, the two hardening standards that many organizations are audited against. They cover authentication, network exposure, cryptography, administrative access, code integrity, and remote management. In practice, Kerberos is preferred over NTLM, SMB signing and encryption are on, TLS is limited to modern cipher suites, and WinRM rejects Basic authentication and unencrypted traffic. According to Microsoft Learn, the hardened defaults apply only to new installations. The announcement describes Server Core and does not describe equivalent defaults for the Desktop Experience option.
The defaults are delivered as policy, which takes precedence over local configuration, so a script or an installer cannot quietly weaken them. An in-box PowerShell module named MSHardenedPolicyEval reports how much of the configuration is in effect and lets administrators remove or reapply the hardened values one category at a time. Microsoft notes that gpresult and RSOP show these settings as Not Configured, because the defaults are built into the image.
The work is not finished. Microsoft lists NTLM blocking, hardware-backed protections such as Secure Boot and DMA protection requirements, and Windows Protected Print as planned for later previews. Build 29706 also has a known issue in which a race condition in the TLS hybrid key exchange can crash the Local Security Authority Subsystem Service (LSASS), the process that holds credentials in memory. Until a fix ships, Microsoft advises disabling the affected hybrid groups.
3- WSUS, SMBv1, VBScript, and Legacy BIOS Boot Leave the Platform
Microsoft has published the list of features that Windows Server 2028 removes. The list comes with a caveat. A feature on it may still be present in the current preview builds, and the plans can change before release.
The removal with the widest reach is the WSUS server role. It is removed from Windows Server 2028 only. WSUS stays supported on earlier releases, including Windows Server 2025, and those servers can continue to update supported clients and servers, including Windows Server 2028.
Legacy BIOS boot is also on the list, which makes UEFI a requirement. A Windows Server 2028 guest needs a Generation 2 virtual machine in Hyper-V, while Generation 1 virtual machines that run earlier guest operating systems are not affected.
Older protocols and tools go as well. SMBv1 is no longer included. VBScript is removed, so scripts and applications that depend on it stop working. The WMIC command-line utility is removed, although Windows Management Instrumentation itself stays. The WINS server role, DirectAccess, and PPTP and L2TP remote access are removed, with DNS, Always On VPN, and IKEv2 or SSTP named as the replacements. Shielded VMs are removed too.
A second group still ships and remains supported, but Microsoft has stopped developing it. It includes Windows PowerShell 5.1, the Windows Deployment Services server role, and BranchCache.
4- What Else Is in the Preview
The preview includes PowerShell 7 in the operating system, side by side with Windows PowerShell 5.1. A server can now join Microsoft Entra ID and, in tenants that opt in, enroll in Microsoft Intune. Microsoft describes Intune server enrollment as intended for nonproduction evaluation. Storage gains native NVMe enabled by default, a built-in NVMe over Fabrics initiator, and optional boot from a ReFS volume. Hyper-V adds Trusted Launch for Generation 2 virtual machines, which is not yet supported with failover clusters or Hyper-V Replica.
AI inference on customer infrastructure is the least mature part of the announcement. It is available to a limited number of customers through an early access program, and the AMD Instinct MI350P accelerator enters preview in the first half of 2027.
What Administrators Need to Do
-
Install build 29706 Server Core in a lab with a clean installation and test applications, agents, and management scripts against the hardened configuration.
-
Look first at anything that depends on NTLM, unsigned or unencrypted SMB, WinRM with Basic authentication, or older TLS cipher suites.
-
Confirm that target hardware boots with UEFI and that planned virtual machines are Generation 2.
-
Search scripts and scheduled tasks for VBScript and
wmic.exe, and move them to PowerShell.
-
Plan update management without a WSUS role on Windows Server 2028, and plan migrations away from DirectAccess, WINS, PPTP, and L2TP.
-
Send findings to the Windows Server Insiders forum while the defaults and the removal list can still change.
Conclusion
Windows Server 2028 changes the starting point of a deployment. Security is the default state, compatibility is the exception that an administrator grants on purpose, and a group of long-standing features is on its way out. The release is still a preview, with no general availability date and with parts of the hardening still to come. The months before the preview expires on October 15, 2027 are the time to find out which workloads depend on what the new release turns off or removes.
References
Introduction
π Windows Server 2028: A trusted foundation for an evolving enterprise
1- Public Preview Arrives as Build 29706
π Announcing Windows Server vNext Preview Build 29706
2- Server Core Now Installs Hardened
π Announcing Hardened Server Core for Windows Server Insiders
π What's new in Windows Server 2028 Preview
π Announcing Windows Server vNext Preview Build 29706
3- WSUS, SMBv1, VBScript, and Legacy BIOS Boot Leave the Platform
π Features removed or no longer developed in Windows Server
4- What Else Is in the Preview
π What's new in Windows Server 2028 Preview
π Windows Server 2028: A trusted foundation for an evolving enterprise
What Administrators Need to Do
π Announcing Hardened Server Core for Windows Server Insiders
π Features removed or no longer developed in Windows Server
This news story is original work based on my own research and has been prepared using the official Windows Server announcements on Microsoft Community Hub and the Microsoft Learn documentation. Windows Server 2028 is in preview, so features, defaults, and the removal list may change before release. Confirm the current state against the latest Windows Server Insider Preview announcement before planning a deployment.