IT infrastructure
I look after infrastructure that has to keep working: servers, domains, backups and networks. I also take on the hard jobs, such as migrating an entire environment without downtime or rebuilding after a ransomware attack. Every stage has a rollback plan, and every project ends with documentation.
Moving whole environments to new platforms and system versions in stages, while users keep working.
A plan for losing the entire server room, proven by a recovery test.
Getting back to work quickly and removing the cause, so the attack does not happen again.
A failed server, storage array or link does not stop the ERP or line-of-business systems.
Secure connections between sites and a network divided so that an incident cannot spread across the whole organisation.
Choosing and supplying what is really needed, with offers prepared for public procurement.
A few typical situations and what I do about them.
“We still have servers running Windows Server 2012 or 2016.”
Version 2012 has not received security updates since October 2023, and 2016 loses them on 12 January 2027. I move roles, the domain and databases to a newer version in stages, so users do not notice the change.
“Our VMware renewal came in much higher than before.”
After Broadcom acquired VMware, perpetual licences were replaced with bundled subscriptions, and for many organisations the cost rose sharply. I work out what moving to Proxmox VE or Hyper-V would cost and help choose what suits the organisation: Proxmox has no licence fees, and Hyper-V is included in the Windows Server licence. Then I move the virtual machines along with their backups.
“We do have backups, but nobody has checked whether we can restore from them.”
I run a test restore in an isolated environment and measure how long it really takes to get back to work. If needed, I add immutable backups that withstand ransomware.
“Computers, servers and printers are all on one network.”
I divide the network into segments (VLANs) and set firewall rules so that an infected computer cannot reach the servers. I plan the work so that the office or company does not have to stop.
“Something has failed: a storage array, the domain or a server that won't boot.”
I diagnose the problem, restore data and services, then write down the cause and what to do so it does not happen again.
Systems and hardware I know from day-to-day work with clients.
I write down what I have done so that the next administrator, an auditor or an inspection can work with it.
Let's start with a review of what you have. After that it is clear what the risks are and where to begin.