Microsoft officially unveiled Windows Server 2028 at its Ignite 2026 conference on Wednesday moving to a "secure by default" deployment model.
The new operating system includes hundreds of hardened security settings enabled from the first boot, departing from the previous practice of relying on administrators to apply custom security scripts, Neowin reported.
The hardened configuration applies to Server Core, effectively limiting the server’s attack surface by restricting network traffic to signed and encrypted channels, as reported by Neowin. Microsoft has enforced stricter platform integrity, ensuring only signed code can run during the sign-in process. While these changes aim to improve security, they may cause compatibility issues with legacy protocols, older authentication methods, and existing management scripts, according to The Register.
"We want to hear where a hardened default gets in the way of a real workload: which setting, which application, and what you had to change to get it working," the Windows Server Team stated in a blog post. Microsoft encourages administrators to use the preview build, specifically build 29706, as a test bed to identify where these new defaults conflict with production environments.
The transition to a locked-down environment is not yet complete. While Kerberos is now the default preference over NTLM, full NTLM blocking remains a feature for a later preview release, according to the Microsoft Blog. Hardware-backed protections, such as Secure Boot and DMA requirements, are also slated for inclusion in future updates.

Administrators can evaluate their current security posture using the MSHardenedPolicyEval tool. Microsoft cautioned that users should expect a score below 100% during the preview phase because the tool is still undergoing refinement and does not yet account for all security conditions, Neowin noted.
The current build includes a known issue where a race condition in the TLS hybrid key exchange can cause the LSASS service to crash. Microsoft recommends disabling hybrid-key exchange groups until a fix is deployed.
Beyond hardening, Windows Server 2028 introduces native support for NVMe storage, which was previously available in Windows Server 2025 only if manually enabled by administrators. The redesign eliminates NVMe translation through a SCSI stack, resulting in improved speeds and reduced overhead. The platform is also being positioned for local AI model execution, with native support for hardware accelerators like AMD’s Instinct MI350P, according to The Register.
Will my existing scripts and management tools work on Windows Server 2028?
Not necessarily. Because the operating system is now hardened by default, legacy protocols and unauthenticated RPC calls are disabled, which may break older scripts and management tools that functioned on Windows Server 2025, The Register reported.
How can I test the new security configurations before a full rollout?
System administrators can register for the Microsoft Windows Insider Program to download the preview build 29706. Microsoft advises using this build specifically as a test environment to identify and report compatibility issues before the software reaches general availability.
Is this hardened configuration mandatory for all deployments?
While the settings are enabled by default, Microsoft notes that customers can relax specific security configurations if their workloads require it. The company intends for these defaults to be refined based on user feedback provided during the preview period.
"That is how the defaults get better before general availability," the Windows Server Team stated.
Keep reading