Server & Infrastructure

Sometimes. It depends on the workload, your connectivity, the licensing, and what the application actually supports — some line-of-business software still runs badly anywhere but a local server. The honest answer usually involves moving some things and keeping others, and anyone giving you a confident yes or no before looking at your environment is guessing.

Urgent enough to plan for now rather than react to later. Out-of-support means no security updates, so newly discovered vulnerabilities simply stay open. It also tends to fail cyber insurance questions and customer security reviews. That said, it is a planning problem rather than an emergency — the sensible response is a sequenced upgrade, not a panic replacement.

Reviewing who holds administrative rights and reducing it to who genuinely needs it, separating privileged accounts from everyday ones, cleaning up accounts belonging to people who have left, reviewing Group Policy for rules nobody can justify, and making sure authentication is configured to current standards rather than defaults set a decade ago.

Yes, and most of what we support we didn't install. The first piece of work is usually documentation — establishing what is actually there, what it does, and what has been configured by hand along the way. That review often turns up more value than any change we make afterwards.

How quickly you can carry on. A single server failure with tested backups and a recovery plan is a bad morning. The same failure with untested backups and no plan is a business interruption. The hardware event is identical — the outcome is decided by preparation.