Microsoft has announced Windows Server 2028 and made it available in preview, with Server Core hardened by default — a significant shift from Windows Server's previous compatible-by-default approach. For UK infrastructure teams still running older estates, that means testing compatibility gates long before any production rollout.
View the data behind this chart
| Server 2019 | Server 2025 | |
|---|---|---|
| Install base share | 33% | 7% |
Windows Server 2028 breaks compatibility by default — what changed
Microsoft has announced Windows Server 2028 and made it available in preview, and the headline change isn't a feature — it's a posture shift. New Server Core installations in the preview use hardened defaults, starting from Windows Server Insider Preview build 29706, according to The Register.
Senior Product Manager Christina Curlette put it plainly: for years, Windows Server "shipped compatible by default," leaving admins to apply security baselines or their own hardening scripts afterwards. That assumption no longer holds. Microsoft says hundreds of settings are active from first boot, alongside Trusted Launch protection for virtual machines and initial Confidential VM support on supported hardware.
Why hardened defaults hit legacy workloads hardest
The practical risk for UK admins is straightforward: configurations that run perfectly on Windows Server 2025 are not guaranteed to work on Windows Server 2028 without changes. Curlette specifically flagged older protocols, legacy authentication, and some management tools and scripts as potentially affected workloads under the new baseline.
Esben Dochy, Principal Technical Evangelist for SecOps at Lansweeper, told The Register that the hardening direction is correct but that it "will add work for teams moving to Server 2028." For organisations running workloads dependent on legacy authentication, protocols, or permissive security settings, that work needs to start during the preview phase — not after a production decision has already been made.
Clean install vs in-place upgrade: the distinction that matters
One detail buried in Microsoft's preview messaging could shape migration strategy significantly. Dochy noted Microsoft has indicated the hardened defaults apply to new installations — meaning if the preview policy remains in the final release, in-place upgrades from Windows Server 2025 may be less disruptive.
The catch, as Dochy pointed out, is that servers upgraded in place may miss out on the new security defaults entirely. That's a genuine trade-off for UK buyers: a faster, less disruptive upgrade path that leaves you short of the hardening Microsoft is pitching as the whole point of the release. Decisions here should feed directly into refresh budgeting rather than being treated as a pure technical afterthought.
Storage, AI acceleration and Intune — the parts beyond security
Hardening dominates the headlines, but Windows Server 2028 brings other changes worth planning around. Microsoft plans to enable native NVMe storage by default and add NVMe over TCP and RDMA support, with booting from ReFS also planned — all of which demand firmware, driver, backup and recovery validation before go-live, since preview behaviour may change before general availability.
On the hardware side, Microsoft is positioning the release for running AI models locally, being positioned to support accelerators including AMD's Instinct MI350P. That's a new sizing conversation for teams evaluating Dell, HPE or Lenovo platforms for 2027–2028 refreshes, pending vendor compatible-platform documentation. Management is broadening too, with Intune entering preview for eligible persistent Windows Servers alongside the existing Azure Arc workflows.
Building a compatibility test plan before you commit
The sensible move for UK infrastructure teams is to treat Windows Server 2028 as a compatibility-led project, not a routine version bump. That means inventorying which systems still rely on legacy authentication or older protocols, building representative test images against the preview, and validating management tooling separately from application behaviour.
Crucially, success on Windows Server 2025 is not sufficient evidence of Windows Server 2028 readiness under the new baseline — it has to be tested directly. Teams weighing whether to stay on current infrastructure a while longer, migrate workloads off ageing virtualisation stacks, or explore alternatives to their existing hypervisor, should fold that work into the same planning cycle rather than treating each as a separate project.
What the adoption curve tells UK buyers about urgency
Lansweeper's October 2026 figures, as reported by The Register, put Windows Server 2019 at 33% and Windows Server 2025 at 7% of the measured install base. Dochy's read is that adoption is driven primarily by lifecycle events, not feature appeal, and he doesn't expect meaningful Windows Server 2028 uptake until more widely used versions approach end of life.
Windows Server 2025 itself remains under extended support until 2034, so there's no forced migration clock yet. For most UK organisations, the realistic approach is to start compatibility testing now, while the preview is still evolving, rather than waiting for a production release and discovering legacy dependencies the hard way. If you're unsure where your estate currently stands, talk to a Servnet engineer about mapping dependencies ahead of the eventual production build.
- 01The Register — Windows Server 2028 won't be compatible by default · 18 November 2026
- 02BleepingComputer — Microsoft announces Windows Server 2028 with hardened security · 18 November 2026
- 03BleepingComputer — Windows Server 2028 tag · 18 November 2026
- 04theregister.com
- 05theregister.com
- 06theregister.com
- 07theregister.com
- 08theregister.com
- 09Microsoft — Windows Server 2028 Preview and Insider Announcement
