Windows Server 2028 preview: Server Core starts locked down

Windows Server 2028 preview: Server Core starts locked down - Web Hosting Dorks

Microsoft used this week's Ignite 2026 conference to put Windows Server 2028, the successor to today's server OS, into public preview. BleepingComputer reported the news on November 18. The official write-up from Neil Hinnant, who leads Windows Server and I/O Fabrics product management at Microsoft, went up on the Microsoft Community Hub on November 17.

If you run Windows servers, or you host them for other people, the change that matters is not a new console. It is the starting state of Server Core. A fresh install of that edition now comes up already tightened, and a revised security baseline is there so you can loosen an individual control when a workload actually needs it.

For years the extra lock-down was a job you did after the box was already on the network. That gap is the part Microsoft is trying to close.

From "harden it later" to "open it only if you must"

Christina Curlette, writing for the Windows Server team on November 17, said the product used to ship compatible first, with the Security Baseline or local scripts applied afterwards. In the current Insider preview, beginning with build 29706, a Server Core setup turns on hundreds of those controls at first boot. Microsoft says the set lines up with CIS and DISA STIG benchmarks that many shops already have to meet. The post is here: Announcing Hardened Server Core for Windows Server Insiders.

Microsoft Learn's preview notes are explicit about the scope: the tighter defaults apply to new installations only. They are meant to blunt common attacks such as stolen credentials, sideways movement inside a network, and protocol downgrades, starting at first boot. Learn also flags the usual preview warning: this is pre-release software and can still change before it ships.

That is useful for a hoster or a sysadmin who images servers all day. It is also a migration trap. Curlette warns that older protocols, older authentication, and some management tools or scripts that still work on Windows Server 2025 may fail on 2028 until you test them and, if needed, relax a specific control. A lab image is mandatory, not optional.

What gets tightened, in practice

Microsoft groups the defaults into several layers (Learn lists seven). You do not need every registry name to see why a hosting rack will feel this. The layer descriptions below follow Curlette's post, which BleepingComputer also summarized, restated here for operators:

  • Sign-in and identity. Kerberos is preferred instead of NTLM, LSASS is protected, password and lockout rules are stricter, and consumer Microsoft accounts are out. Full NTLM blocking is not in this preview yet, which matters if you still have older file-share or application dependencies.
  • The network path. SMB is expected to be signed and encrypted, the host firewall is enabled in all profiles, and older name-resolution plus unauthenticated RPC are switched off. Shared storage and backup agents that still assume unsigned SMB, or leftover NetBIOS habits, are the first things to break in a colocation cabinet or a Hyper-V cluster.
  • Crypto. TLS is restricted to current cipher suites, key exchange includes a hybrid post-quantum option known as ML-KEM, and keys sitting on disk get stronger protection. Hinnant's announcement also flags automatic certificate management as a workstream, which any shop tired of expired IIS or WinRM certificates will want to watch.
  • Privilege. Elevation needs an administrator's approval, high-powered rights stay with the Administrators group, Guest logons are blocked, and setup programs cannot raise their own rights.
  • Platform integrity. The logon path is limited to code signed by Microsoft, signature checks are tighter, and the pagefile is encrypted. Encrypted pagefiles are a small but real I/O consideration on dense hosts.
  • Remote management and logging. Remote Desktop expects Network Level Authentication plus TLS. WinRM refuses Basic, Digest, and cleartext. Command-line auditing is on, PowerShell records script-block activity, and event logs are sized up.

The tighter values are stored as policy — in the policy hive, where the component allows it — so a local cmdlet or installer cannot quietly undo them. OSConfig, Group Policy, or another management tool can still change or extend the set. The firewall remains locally manageable on purpose. Curlette also notes a gotcha: gpresult and RSOP can show these built-in defaults as Not Configured, because there is no .pol file for those tools to read. The in-box MSHardenedPolicyEval module is the way to score, loosen, or put a category back: Get-MSHardenedPolicyScore, Restore-MSHardenedPolicy, and Set-MSHardenedPolicy. In the example Microsoft published, an overall result of 191 out of 237 policies (about 80.59 percent) is still treated as expected on this build, because some checks are unfinished.

If a management plane already owns the box, Microsoft says to use that tooling for changes and keep MSHardenedPolicyEval for scoring only, so the two do not fight.

What is not locked down yet

This is still a preview. Curlette's post, and BleepingComputer's summary, both say Microsoft is still working toward a full NTLM block, platform protections backed by hardware (Secure Boot and DMA requirements, plus kernel shadow stacks), tighter print and RPC controls including Windows Protected Print, and extras such as a logon banner.

Do not plan a 2028 cutover as if NTLM is already gone. Plan as if it soon will be, and inventory anything that still needs it.

Virtual machines, storage, and day-to-day operations

On the virtualization side, Hinnant says Trusted Launch is being extended so virtual machines can get boot-integrity coverage across a fleet, and that Confidential VM support starts a path toward runtimes whose integrity is protected, on confidential-VM hardware that supports it.

Microsoft Learn is more cautious about the current Trusted Launch preview on Generation 2 Hyper-V guests. It uses Secure Boot, a virtual TPM, and encrypted guest state, but this flight does not yet support moving that kind of virtual machine to another host, failover clustering, Hyper-V Replica, or boot-integrity verification. That is a hard stop for many production clusters. Test it, but do not promise customers live migration of those guests until Microsoft says those gaps are closed.

On the storage side, the built-in NVMe stack is enabled out of the box, NVMe over Fabrics is in the preview over both TCP and RDMA, and the operating system can start from a ReFS volume. Learn dates the NVMe-oF initiator to Insider build 29550 (March 12, 2026) and notes that the current initiator is command-line only, with no multipathing and limited recovery in some network failures. ReFS Boot arrived in build 29531 (February 12, 2026). It can use ReFS features such as metadata checksums and online scrubbing on the system volume, and ReFS supports volumes and files up to 35 petabytes, but it needs UEFI firmware and does not support Generation 1 virtual machines.

For anyone still building or renting bare-metal boxes, the operational lesson is familiar: a tighter default is only useful if you also know how to harden the rest of the stack yourself. Thexyz's walk-through of building a custom storage server is a practical example of that work on a self-managed machine — firewall, remote access, and the rest — which is the same discipline Windows Server 2028 is trying to bake into Server Core.

Management at scale is also shifting. Intune support for Windows Servers is in preview, so endpoint-style workflows for configuration, compliance, apps, and updates can reach eligible, persistent servers. Learn adds important limits: Intune server enrollment is off by default in this preview and is intended for non-production evaluation. Servers can also join Microsoft Entra ID and sign in with Entra accounts, and Azure Arc can coexist in the supported scope. Hinnant also says Windows Admin Center Virtualization Mode is generally available.

There is an AI chapter as well: deploying inference environments, managing accelerators, and running open-weight or custom models through stacks such as Foundry Local, Windows ML, Llama.cpp, and vLLM. Hinnant says AMD's Instinct MI350P card is due to enter preview in the first half of 2027, for in-market supported Windows Servers as well as 2028. That is a product direction, not something most hosting panels need to support tomorrow.

How to try it, and what to test first

If you want a copy, Microsoft points administrators to the Windows Server Insider Program, or to its Technology Adoption Program (TAP) if you want access sooner and a closer loop with the product group. Hinnant's post says hybrid-intelligence features are limited to an early-access program and have hardware requirements. Feedback on the hardened defaults belongs on the Windows Server Insiders forum; Curlette asks specifically which setting broke a real workload, and what you had to change to get it working.

A sensible test plan for a host or a sysadmin looks like this:

  • Build a Server Core 2028 preview virtual machine or lab host from a new install. Learn says the tighter defaults apply to new installations only.
  • Score it with MSHardenedPolicyEval and keep a note of the overall figure Microsoft showed — well below 100 percent is normal on this build.
  • Point your current backup agents, monitoring, remote-management tools, and SMB clients at it. Unsigned SMB, Basic WinRM, leftover NTLM, and older RPC are the usual breakage points.
  • If you virtualize for customers, try Trusted Launch only with the documented preview limits in mind.
  • Do not loosen a whole category unless a real workload needs it, and put the control back when you are done.

Hosting know-how, minus the hype: the interesting part of Windows Server 2028 is not the version number. It is that a new Server Core box is no longer assumed to be wide open until somebody remembers to lock it.

Sources

Sergiu Gatlan, BleepingComputer, November 18, 2026 report on the Windows Server 2028 preview and its tighter defaults: https://www.bleepingcomputer.com/news/microsoft/microsoft-announces-windows-server-2028-with-hardened-security/

Neil Hinnant, Microsoft Community Hub, Windows Server 2028: A trusted foundation for an evolving enterprise, November 17, 2026: https://techcommunity.microsoft.com/blog/windowsservernewsandbestpractices/windows-server-2028-a-trusted-foundation-for-an-evolving-enterprise/4574112

Christina Curlette, Microsoft Community Hub, Announcing Hardened Server Core for Windows Server Insiders, November 17, 2026: https://techcommunity.microsoft.com/blog/windowsservernewsandbestpractices/announcing-hardened-server-core-for-windows-server-insiders/4574239

Microsoft Learn, Windows Server 2028 Preview: New features: https://learn.microsoft.com/en-us/windows-server/get-started/whats-new-windows-server-2028

Windows Experience Blog, Microsoft Ignite 2026: Building Windows for the next era of work, November 17, 2026: https://blogs.windows.com/windowsexperience/2026/11/17/microsoft-ignite-2026-building-windows-for-the-next-era-of-work/

Thexyz Blog, Building a custom Storage Server with the PowerEdge T150, Ubuntu, and Nextcloud: https://www.thexyz.com/blog/building-a-custom-storage-server-with-the-poweredge-t150-ubuntu-and-nextcloud/