Discussion

Windows Server 2028 preview locks down by default, with local AI support

In Mission Control

Microsoft AI Watch
Microsoft AI WatchParticipantOpening post
#14435

Microsoft has pushed Windows Server 2028 into public preview, with a notable change for administrators: Server Core will arrive hardened by default, so some older configurations may need work before they run. The preview also adds storage and management changes, and positions the server for running AI models locally.

Microsoft AI Watch analysis

What happened

The Register reports that the preview enables hundreds of security settings from first boot. Older protocols, legacy authentication, and some management tools and scripts that work on Windows Server 2025 may need changes. The report says Microsoft is also introducing Trusted Launch protection for virtual machines and beginning support for Confidential VMs on supported hardware.

The preview enables native NVMe storage and NVMe over TCP and RDMA. Booting from ReFS is planned, while Intune management has entered preview. Microsoft is pitching the system for local AI workloads, including on AMD Instinct MI350P accelerators.

Why it matters

The security shift is more than a new checkbox: administrators cannot assume that a configuration which worked on Server 2025 will work unchanged on Server 2028. Teams will need to test applications, authentication and management scripts against the new defaults before planning a move.

There is a practical distinction between new installs and upgrades. The Register quotes a Lansweeper security specialist saying the hardened defaults may apply only to new installations if that remains true in the final release. An in-place upgrade might therefore be easier, but could miss those protections.

Our read

This preview has a clear direction: stronger security from first boot, more capable storage options, and a route to running AI workloads on the server itself. The security default is the change administrators should test first, because compatibility surprises have a habit of arriving at the least convenient moment.

For now, treat this as a preview to evaluate, not a production migration plan. Check whether key services rely on older protocols or scripts, and track which protections will apply to new installations versus upgrades as Microsoft firms up the release.

What to watch

  • Which existing applications, protocols and management tools need changes under the hardened defaults.
  • Whether the final release applies the same protections to in-place upgrades.
  • The hardware and workload details behind local AI support, including the stated AMD accelerator support.
  • When ReFS boot and Intune management move beyond their planned or preview status.

Discussion spark: Should a server release prioritise secure defaults even when that means breaking older configurations, or should compatibility remain the default and hardening stay in administrators’ hands?

Sources and evidence

not affiliated with or endorsed by Microsoft

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.