Our server is past its end of support
A 2012 R2 (or older) box still serving files, running a database, or hosting a line-of-business app, with no security patches arriving any more.
Upgraded onto a supported version
Working with Windows Server?
Most Windows Server boxes that come to us were installed by someone who has long since left, and the business is nervous about rebooting them. We take stock of what each one actually does and move it forward without surprises.
What it is
Windows Server is Microsoft's server operating system family, first released in 1993 as Windows NT 3.1 Advanced Server and carrying the Windows Server name since the 2003 edition. The releases still in support are 2016 (extended support to January 2027), 2019, 2022 and 2025.
It hosts the core plumbing of most office networks: Active Directory, DNS, DHCP, file and print, Hyper-V virtualisation, Remote Desktop Services and IIS. It is also what SQL Server, Exchange, SharePoint and countless in-house line-of-business applications are built to run on.
Licensing is per-core, with Client Access Licences for each user or device that touches it. The same editions run on physical hardware, in Azure, and on AWS or GCP instances.
The honest version
No technology is all upside. This is where Windows Server earns its place and where it tends to cause trouble.
Sound familiar?
The Windows Server problems that bring people to us, and what you have once each one is fixed.
A 2012 R2 (or older) box still serving files, running a database, or hosting a line-of-business app, with no security patches arriving any more.
Upgraded onto a supported version
Failed logons flooding the logs, replication between controllers lagging, or Group Policy no longer applying to a site.
AD healthy and replicating
Nobody has the domain admin password, documentation is thin, and the hosting bill goes to an email address nobody can open.
Every account back in your hands
WinSxS has grown for years, WSUS is holding every update it ever downloaded, and nobody dares delete anything.
Space reclaimed, growth watched
Volume Shadow Copy errors in the event log, a backup product that still reports success, and no restore tested in months.
Backups verified by restore
CALs expired, a licensing server that lost its activation, or a session host running out of memory at peak.
RDS stable through the workday
Guests pausing on shutdown, storage running thin, or a cluster that no longer fails over cleanly.
Virtualisation back under control
The database is too large for the cleanup wizard, approvals are stuck, and clients haven't reported in for weeks.
Patching flowing again
What we do
Call us for one server, or hand us the whole estate.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes. We inventory what the box actually does, build a replacement on a supported release (2022 is the usual choice, 2025 where it fits), move services across with a tested cutover, and keep the old server ready to roll back to until the new one has proven itself.
Yes. We start by regaining control of every account, recording what each server does, and finding the gaps in backups and patching. Only after that do we propose changes, so nothing important gets touched before it is understood.
Not in-place as a rule. We build 2022 servers alongside the existing ones, migrate roles such as AD DS, DNS, DHCP, file shares and RDS across with Microsoft's supported procedures, and decommission the old ones only after a quiet period on the new ones.
Only where it genuinely fits. For Active Directory, Exchange, SharePoint and most commercial Windows applications, staying on Windows Server is the sensible call. For a web stack or container workload, Linux often costs less to run and we will say so.
Yes. Slow logons, a full C: drive, a WSUS database that will not shrink, or a Hyper-V host that is thrashing all have known causes. We diagnose with Performance Monitor and the event log, then clear the real problem rather than throwing more hardware at it.
Estimates are free. Describe the servers and what is going wrong and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: