Microsoft wants Windows Server 2028 locked down from the moment it starts. That may be welcome news for security teams, but less so for administrators keeping older applications and management tools running.
The company introduced Windows Server 2028 in public preview at Ignite on Nov. 17, 2026. Starting with Insider Preview build 29706, new Server Core installations automatically enable hundreds of security settings previously left for administrators to configure.
An authentication method that worked under previous configurations or a script that ran without complaint may need attention under the new defaults. IT teams can test the changes now, but the preview is not supported for production use.
Windows Server 2028’s new security defaults
Microsoft’s hardened Server Core configuration replaces an approach that required administrators to apply security baselines or custom scripts after installation. The defaults align with Center for Internet Security (CIS) benchmarks and Defense Information Systems Agency Security Technical Implementation Guides (DISA STIGs).
The configuration favors Kerberos over NTLM authentication, protects the Local Security Authority Subsystem Service (LSASS), and enables SMB signing, encryption and Windows Firewall across all profiles. It also tightens TLS requirements, introduces hybrid post-quantum key exchange and disables Basic authentication for Windows Remote Management.
Remote Desktop now requires Network Level Authentication, adding another consideration for administrators managing older connections. Separate Windows 11 changes have already disrupted Remote Desktop access on some enterprise-managed devices, highlighting the importance of testing security policies against existing workflows.
Not every planned protection is active. NTLM blocking and additional hardware-backed safeguards are slated for later previews. Microsoft’s build 29706 release notes also warn that hybrid TLS key exchange can crash LSASS under certain conditions.
Other Windows Server 2028 improvements include native NVMe storage enabled by default, NVMe over Fabrics support and planned ReFS boot support. Intune-based server management is also entering preview.
Compatibility risks and upgrade planning
Administrators can assess the hardened configuration using the built-in Get-MSHardenedPolicyScore command. Microsoft also provides tools to adjust settings but cautions against modifying policies already controlled by Group Policy or other management software.
Microsoft’s planned feature removals include Windows Server Update Services (WSUS), SMBv1, VBScript, WMIC and legacy BIOS boot support. Windows Deployment Services and Windows PowerShell 5.1 are slated for deprecation. Microsoft says these plans could change before release.
Legacy scripts deserve particular attention. Microsoft has also removed WMIC from a Windows 11 beta, underscoring the need to identify automation that still depends on the command-line utility.
Existing installations raise another concern. Esben Dochy, principal technical evangelist for SecOps at Lansweeper, told The Register that hardening currently applies to new installations. If that remains true at release, in-place upgrades might not inherit the protections.
Microsoft has not confirmed a final production upgrade path or general availability date. The preview expires Oct. 15, 2027, while Windows Server 2025 remains under extended support through 2034.
September’s Remote Desktop and Hyper-V update failures showed how Windows changes can disrupt enterprise workloads. Before planning a move to Server 2028, administrators should find out which applications, scripts and server roles still depend on the settings Microsoft is tightening. The place to discover those problems is a test environment, not a production server.
Read more: Microsoft’s October Windows Server updates also disrupted on-premises Exchange services, requiring affected administrators to evaluate a temporary workaround.