November 18, 2026

Windows Server 2028 Arrives Locked Down by Default: The Spec Sheet and a Planning Checklist for Small IT Teams

Microsoft unveiled Windows Server 2028 at Ignite with a hardened Server Core configuration switched on from first boot, a new adjustable security baseline, Intune management for servers and native NVMe. Here is the spec sheet, what is still missing, and a checklist for planning your next server refresh.

A long data center aisle of black rack servers with rows of small blue and white status lights

Microsoft used its Ignite 2026 conference on Tuesday to announce Windows Server 2028, and the headline is security that is on before an administrator touches anything. Neil Hinnant, Microsoft’s Director of Windows Server and I/O Fabrics product management, said the hardened default configuration and a new baseline are meant to cut the effort of reaching a secure starting point from the first day. The details below come from BleepingComputer’s report on the announcement.

Spec sheet: what is switched on from first boot

Identity and sign-in

  • Kerberos preferred over NTLM
  • LSASS (the process that holds credentials) protected
  • Strong passwords and account lockout enforced
  • No consumer accounts

Network exposure

  • SMB signing and encryption
  • Firewall on in every profile
  • Legacy name resolution and unauthenticated RPC turned off

Cryptography

  • TLS restricted to modern cipher suites
  • Hybrid post-quantum key exchange (ML-KEM)
  • Strong protection for stored keys

Admin rights

  • Elevation requires administrator approval, and powerful rights stay with the Administrators group
  • Guest sign-in blocked
  • Installers cannot elevate themselves

Platform and code integrity

  • Only Microsoft-signed code runs in the sign-in process
  • Stricter signature validation
  • Encrypted paging file

Remote access and logging

  • RDP with Network Level Authentication and TLS
  • WinRM without Basic, Digest or unencrypted traffic
  • Advanced auditing with command lines, PowerShell script block logging and larger event logs

Spec sheet: everything else

  • Adjustable baseline: a new security baseline lets admins relax specific settings rather than starting from scratch.
  • Virtual machines: Trusted Launch for boot integrity across VMs, and the start of Confidential VM support on compatible hardware.
  • Management: Intune management for eligible, persistent servers, covering configuration, compliance, apps and updates.
  • Storage: native NVMe on by default, NVMe over TCP and RDMA, and booting from ReFS.
  • AI: tools to deploy inference environments and manage accelerator hardware, with support for open-weight and custom models through options such as Windows ML, Foundry Local, vLLM and Llama.cpp.

Not there yet

Microsoft says it is still working on NTLM blocking, hardware-backed platform protection, and print and RPC hardening, among other additions. BleepingComputer’s report does not give a general availability date. Testers can join the Windows Insider Program for Windows Server or apply to the Windows Server Technology Adoption Program for earlier access.

Planning checklist

  1. List the servers you run today and their versions, and flag any that are approaching end of support.
  2. Identify applications and devices that still depend on NTLM, unsigned SMB, Basic authentication over WinRM or older TLS. These are the ones most likely to break on a hardened default.
  3. Check your printers, scanners and multifunction devices that save to network shares, since older units often rely on legacy protocols.
  4. Ask your line-of-business software vendors whether they have tested on hardened configurations.
  5. Decide how servers will be managed. If you already manage laptops with an endpoint management tool, consider whether servers should join the same process.
  6. Stand up a test server through the preview programs before committing to a rollout date.

What this means for your company

For a small or midsize business, secure-by-default is good news: many breaches start with settings nobody got around to changing. The catch is compatibility. Older software, scanners and scripts that quietly rely on legacy protocols may stop working, and the temptation will be to switch protections off to make the problem go away. The better path is to find those dependencies now, fix or replace them, and relax only what is truly required, with a record of why. You can also adopt many of these same settings on the servers you run today, without waiting for a new version.

If you would like a clear picture of which of your systems would trip over a locked-down server, we can help you map them and plan the upgrade. Reach out to Layer 7 Data Solutions to discuss how we’ve helped companies similar to yours.

About The Author