Microsoft has announced the public preview of Window Server 2028, and of course, the announcement is a useless jumble of buzzwords and slop, so I’m not going to spend any time decoding it. However, there is one major change coming in Server 2028 that everyone working with this platform really ought to be aware of – a massive hardening of Server Core that will definitely break things that used to work fine on Server 2025. It even got its own detailed blog post that’s a lot more interesting than the actual public preview announcement.
Up to and including Windows Server 2025, a stock installation was insecure, unhardened by default, with the expectation and norm being that administrators applied their own hardening scripts and settings post-installation. With Server 2028, that’s changing, and Server Core will now be secured and hardened out of the box, with administrators having to explicitly relax any settings their workloads might require.
Starting with Windows Server Insider Preview build 29706, Server Core installs hardened. Hundreds of security settings are on from first boot. They’re aligned with the industry benchmarks you’re already measured against, such as CIS and DISA STIG. The secure configuration is the starting state, not a project you run after setup. That closes the window where a newly deployed server sits exposed while it waits to be hardened.
↫ Christina Curlette
Things like identity and authentication, cryptography, privilege and admin access, remote access, and more, are all locked down and use only the most up-to-date features, cyphers, best practices, and so on. I’m no system administrator, but it seems kind of wild to me that this hasn’t always been the norm. I’m glad they’re at least moving to it now, starting with Insider Preview build 29706

This is all great and such, however…
and
look at this one:
More or less the entire blog post is written by an LLM. These patterns of “fact, hence corollary”, “the design decision, so… the negative does not exist…” are pretty difficult to not recognize.
(Just to be clear, I’m not making a value judgement, but an observation)
Microsoft’s true business model is to sell uncrapifying services for their crappy products to their IT management clientele. This explains why their products are laborious to use (we need more people and more software), complex (we need training), incompatible (better? not for our critical accounting system from 2004) and insecure (certified admin or ransomware, you choose).
They only sometimes inject some common sense to maintain the frustration level below the tipping point, and this is an example of such action.