Windows Server support and migration
Servers watched, migrations that finish by Monday.
A server that fails quietly is worse than one that fails loudly. Monitoring, patching, tested backups and a plan for the day the hardware dies — plus honest advice about what belongs in the cloud and what genuinely does not.
What it costs
Server and migration projects quoted fixed-price after an assessment. Ongoing oversight sits in the $650/month retainer; ad-hoc work at $185/hr scheduled or $145/hr remote.
The failure nobody sees coming
Servers rarely die all at once. A drive in the RAID array fails, the array carries on with no visible symptom, and nobody notices because nobody was watching. Months later a second drive goes and the whole thing is gone — along with, very often, backups that had been failing quietly for the same period.
It is the most common serious incident we get called into, and it is entirely preventable by monitoring that costs a fraction of the recovery.
Cloud, on-premise, and the honest middle
Not everything belongs in the cloud, and the people telling you otherwise usually sell cloud. Applications with heavy local file access, systems with hardware dongles, and anything a regulator expects you to point at often still make sense on-premise.
Email, file sharing and collaboration, on the other hand, have very little business living on a server in your comms closet in 2026. Microsoft 365 does it better and cheaper with far less to go wrong — see Office 365 and Microsoft 365 migration for how that move is run.
Downtown you at least have the connectivity to make cloud viable — most Loop and West Loop buildings carry several carriers, so a genuinely diverse second circuit is obtainable, which is not true everywhere.
Migrations without the weekend from hell
Server replacements and Windows Server migrations are planned, staged and run outside working hours, with the old system kept alive until the new one is verified. Shared drives keep their permissions, applications are checked on the new server before anyone depends on it, and staff get a page describing what changed rather than a surprise on Monday.
Migrations are quoted fixed-price. Hourly billing on a migration puts the risk of the unexpected on you, which is backwards — anticipating it is the job.
Moving email off an Exchange server or out of Google Workspace is its own job with its own pitfalls, covered in detail on the Office 365 migration page.
Windows Server 2016 support ends in January 2027
Microsoft ends extended support for Windows Server 2016 on 12 January 2027. After that date there are no more security updates, and a server that cannot be patched is exactly what cyber-insurance questionnaires ask about. Windows Server 2012 and 2012 R2 already went out of support in October 2023, and a surprising number of downtown offices are still running one.
If your server is on either version, the time to plan the move is now rather than the week before. The options are a new server on a current version of Windows Server, moving the workload to Azure or Microsoft 365, or a mix of the two — and the right answer depends on what the server actually does, which is the first thing the assessment works out.
Windows Server repair when something has already gone wrong
A server that will not boot, a RAID array reporting a failed drive, Active Directory refusing logins, a file share that has vanished, or an update that left the machine stuck in a restart loop. The first step is always the same: stop anything that could make it worse, confirm what the backups actually hold, and only then start the repair.
Where the hardware is past saving, the data gets recovered onto temporary hardware so the business can work while the replacement is planned properly rather than in a panic. Urgent server work is billed at the published short-notice rate; everything that can wait for an evening or weekend is scheduled then.
Azure, and when a cloud server makes sense
Some workloads do belong on a server, just not one in your office: an accounting or practice-management application that several sites need to reach, or a system that has to keep running when the office internet goes down. A virtual server in Azure handles that well, with the costs worked out before the move rather than discovered on the first monthly bill.
Others are cheaper and faster on a small server on-premise, especially anything moving large files around the office all day. Neither is the default here; the recommendation follows what the workload needs.
Microsoft 365 administration
Starters set up before their first day, leavers disabled the hour they go with the mailbox preserved, licences audited so you stop paying for people who left in 2023, and multi-factor authentication actually enforced rather than merely available.
Worth saying plainly: Microsoft does not back up your 365 data the way most people assume. Their remit is service availability, not your recovery, and retention windows are short. Separate 365 backup is inexpensive — see backup and recovery.
FAQ
Questions we get asked
Should we move our server to the cloud?
Some of it, probably. Email and file sharing belong in Microsoft 365 for almost everyone. Applications with heavy local file access, or anything that must survive your internet going down, often still make sense on-premise. The answer is usually a split.
How old is too old for a server?
Five years is where replacement gets planned, six is where it gets pushed. Not because it stops working, but because out-of-warranty failure turns a four-hour incident into a four-day one while a part is hunted down.
Does Microsoft back up our 365 data?
Not as most people assume. Microsoft protects the service; recovering your data after an accidental deletion, a departed employee's mailbox purge or ransomware is your responsibility, and retention windows are short. Third-party 365 backup is cheap and worth having.
Can you take over a server somebody else built?
Yes, and it is common. It gets documented first — frequently for the first time — and anything urgent is flagged before agreeing what ongoing support looks like.
When would a server migration actually happen?
Evenings or a weekend, with the old system running until the new one is verified. That is the normal pattern here rather than an out-of-hours premium.
When does Windows Server 2016 support end?
Extended support for Windows Server 2016 ends on 12 January 2027. Windows Server 2012 and 2012 R2 ended in October 2023. A server on either needs a migration plan, because it will no longer receive security updates.
Do you do emergency Windows Server repair in Chicago?
Yes. Urgent work is billed at the published short-notice rate of $245/hr. The first job is protecting the data and confirming the backups; the repair or replacement comes after that, not before.
Should our server move to Azure?
Sometimes. Applications that several locations need to reach, or that must keep running when the office internet fails, often suit a virtual server in Azure. Workloads that move large files around the office all day are usually cheaper and faster on-premise. The costs of each are set out before you decide.
Ready when you are.
Ring and describe it in plain English. You will get a number before anyone drives anywhere.