You don't need that Windows Server.

Many businesses rely on Windows Server by default. Our infrastructure expert explains how to reduce cost and complexity by rethinking legacy choices.

June 17, 2026

By

Paul Wilk

,

Head of Infrastructure Practice

Challenging legacy infrastructure choices to reduce cost and complexity

That would have been a controversial statement in enterprise IT a decade or so ago. These days? Not so much.

I still walk into environments whereWindows Server is everywhere, but when you start digging into it, a lot of those systems are running on Windows simply because they always have been.Nobody revisited the design, nobody questioned the dependency, and over time it just became “the standard" - a textbook definition of technological debt.

Most modern infrastructure is now heavilyLinux-driven under the hood: cloud platforms, containers, Kubernetes, automation tooling, observability stacks, most (if not all) appliances, the list goes on.

To be clear, this is not “Microsoft bad,Linux good”. Some workloads absolutely belong on Windows. There are environments where Active Directory, Microsoft integrations, or specific enterprise apps genuinely make it the right choice.

That said, there are also plenty of environments carrying a much bigger Windows footprint than they actually need,and that comes with cost in more ways than you might think.

Licensing is an obvious one, but it’s also thehidden overhead: Every Windows VM means patching, reboots, monitoring, antivirus, management overhead, backup considerations, and usually a biggercompute footprint than the equivalent Linux service. With the rising cost of hardwareand delivery ETAs listed in months or quarters, every CPU thread, every GB ofRAM and every byte of space in the SAN could make a difference between straight forward hardware renewal quote and tension with finance over an exceeded budget.

A lot of services that traditionally defaulted to Windows can now run perfectly well as lightweight Linux services or containers. DNS and DHCP are obvious examples with things like BIND9 ordnsmasq. Even identity services don’t always have to mean Active Directory anymore as FreeIPA or OpenLDAP can do the job extremely well and integrate surprisingly well even with legacy software hardcoded to expect a traditionalAD.

Instead of spinning up multiple heavyWindows VMs, you can often consolidate services into a much smaller footprintwith lower resource usage, lower operational overhead, and far better density on existing hardware. It's not that uncommon to see organisations reduce both infrastructure costs and operational headaches just by questioning old assumptions.

In truth, technical migration is usually the easy part. The mindset shift is the difficult bit. People get comfortable with familiar platforms and stop asking why things are the way they are.

So here’s a simple test:  look at every Windows Server and ask: “Does this actually need to be Windows?

Sometimes the answer is an easy “yes”but surprisingly often it’s: “actually no".

The engineers who get comfortable workingacross platforms, and who are willing to challenge old assumptions, are theones who will be best positioned for what’s coming next.

Taken from Tech Insights Newsletter, May2026, a monthly briefing for IT leaders covering emerging regulations,technology shifts, resilience planning, and innovation.  

https://www.linkedin.com/pulse/top-mind-may-eir-business-f2tef/?trackingId=qnfqnJdpQN60wbtjLGMYuQ%3D%3D