News Security news
Windows Server 2028 arrives with Hardened Server Core: what changes in the defaults and what to test
On 17 November 2026 at Ignite, Microsoft unveiled Windows Server 2028. The biggest change for admins is that Server Core installs come hardened out of the box in the preview: SMB signing and encryption enforced, the firewall on in every profile, RDP only with NLA, WinRM without Basic. Microsoft has not given a release date, but you can try the preview now.
Key points
- Windows Server 2028 is in public preview; Microsoft has not announced a general availability date.
- In Insider build 29706, Server Core is hardened by default: SMB signing and encryption, firewall on in every profile, legacy name resolution and unauthenticated RPC off.
- Also: Kerberos preferred over NTLM, LSASS protection, TLS limited to modern cipher suites with hybrid ML-KEM key exchange, command-line auditing and PowerShell script block logging.
- Individual categories can be reverted with Restore-MSHardenedPolicy; Microsoft warns some legacy protocols, tools and scripts may stop working.
What happened
On 17 November 2026 at Ignite, Microsoft unveiled Windows Server 2028. It is in public preview and Microsoft has not given a general availability date. Security items on its list include a hardened Server Core configuration enabled by default, a new security baseline, Trusted Launch for virtual machines, expanded Confidential VM support, automatic certificate management and investment in post-quantum cryptography.
The more useful post for admins is a second Microsoft article from the same day: starting with Windows Server Insider build 29706, Server Core installs hardened. The old routine of "install, then lock down" becomes "locked down from the start, open up only what you need".
What changes in the defaults
Microsoft describes the settings by layer (the announcement does not name individual policies):
| Area | Default in the preview |
|---|---|
| Identity and authentication | Kerberos preferred over NTLM, LSASS protection, strong passwords and account lockout, no consumer Microsoft accounts |
| Network | SMB signing and encryption, firewall on in every profile, legacy name resolution off, unauthenticated RPC off |
| Cryptography | TLS limited to modern cipher suites, hybrid post-quantum ML-KEM key exchange, stronger protection for stored keys |
| Privilege | Admins approve elevation, powerful rights stay with Administrators, Guests cannot sign in, installers cannot self-elevate |
| Code integrity | Only Microsoft-signed code in the sign-in process, stricter signature validation, encrypted paging file |
| Remote access and auditing | RDP only with NLA and TLS, WinRM without Basic, Digest or unencrypted traffic, advanced auditing with command lines, PowerShell script block logging, larger event logs |
According to Microsoft, the preview does not yet include NTLM blocking, Secure Boot and DMA protection requirements, kernel shadow stacks, print and RPC hardening (including Windows Protected Print), or further settings such as a logon banner.
What it means for admins
At Kyberkit we see this as good news for defenders. Several items in the table are exactly what tends to be missing when you investigate an incident: unsigned SMB, RDP without NLA, WinRM accepting Basic auth, or auditing without command lines, which leaves gaps in the attacker's trail. Command-line auditing and script block logging on by default make investigations much easier.
The flip side is compatibility. Microsoft says plainly that some things that worked on Windows Server 2025 may not work: older protocols, legacy authentication, and some management tools and scripts. Expect trouble mainly from older devices and apps that cannot sign SMB, and from scripts that rely on WinRM with Basic auth.
What to do
- Try the preview in a test environment through the Windows Server Insider Program, with your own applications, backup, monitoring and management scripts.
- Check the hardening score with
Get-MSHardenedPolicyScore;Get-MSHardenedPolicyCategorieslists valid categories. They includeSMBAndFileSharing,RemoteManagement,RemoteDesktop,CryptographyAndTLSandAuditPolicy. - When something breaks, revert a single category rather than the whole server: run
Restore-MSHardenedPolicy -Category SMBAndFileSharing -WhatIffirst, then without-WhatIf.Set-MSHardenedPolicyre-applies the hardened values.MSHardenedPolicyEval.exein%SystemRoot%\System32offers the same functions from a command prompt. - If OSConfig or Group Policy manages your servers, Microsoft advises using the in-box tools for scoring only - applying or restoring with them can conflict with your management tool.
- Don't be surprised when
gpresultand RSOP show these settings as "Not Configured": the values are built into the image. Microsoft notes the cmdlet names may change in a later preview flight.
You can start today by finding where your current estate still runs unsigned SMB or WinRM with Basic auth. The same settings can be tightened on older Windows Server versions, which will make the move to 2028 far less painful.
Timeline
- 17 Nov 2026 - Microsoft announces Windows Server 2028 at Ignite, with Hardened Server Core in Insider build 29706.
- 18 Nov 2026 - trade press covers the announcement.
- General availability - not yet announced.
We verified these details on 18 Nov 2026 against two Microsoft posts on Tech Community.
FAQ
When will Windows Server 2028 ship?
As of 17 Nov 2026 Microsoft has not given a general availability date. The release is in public preview through the Windows Server Insider Program, and the Technology Adoption Program (TAP) offers earlier access.
Will Hardened Server Core break my applications?
It might. Microsoft itself says some things that worked on Windows Server 2025 may not work, including older protocols, legacy authentication and some management tools and scripts. Test the preview against your own environment.
Can I turn the hardening off?
Yes, category by category. Restore-MSHardenedPolicy -Category reverts one category (for example SMBAndFileSharing); without the parameter it reverts the whole server. Both write cmdlets support -WhatIf and a restart may be needed.
Why does gpresult show these settings as Not Configured?
Microsoft says this is expected: the hardened values are built into the image rather than set through Group Policy, so gpresult and RSOP do not report them as configured.
Sources
Spotted a mistake? Let us know and we will correct it openly.