A lot of the useful machines we look after are Linux. Web apps, internal tools, RADIUS, the odd firewall companion, monitoring. Ubuntu is the one we see most. CentOS-family boxes still turn up in cupboards and need a plan, not a lecture.
ECOMX manages those servers for clients in Pretoria, Centurion, Sandton and further out over SSH. The work is patching, disk, failed services, and a backup that restores. It is not a standing offer to rewrite your application.
A named patch window. Surprise updates on a Friday are how small sites lose a weekend.
Logs you can read when something stops. If the disk fills with logs, that is its own incident.
Accounts for people, not a shared root password in a spreadsheet.
ECOMX manages those servers for clients in Pretoria, Centurion, Sandton and further out over SSH.
So is a small physical box if that is what the site has power and space for. We care more about whether it comes back after a power cut than about the hypervisor logo. If the host dies when the power drops and the guests are not set to start, the 'cloud' in the brochure was a PC under a desk.
If the business lives in a Windows line-of-business app with a vendor who only supports Windows Server, we will not force Linux into that role. We run what the application needs, then put Linux where it is the simpler, clearer machine: the web tier, the backup server, the RADIUS box, the jump host.
Ubuntu in production is the common one. We also inherit older Enterprise Linux boxes and will tell you if they are still patchable.
Sometimes there is a small API or integration. Day-to-day Linux management is not a software build. Custom work is scoped on its own.
Yes. We read what is there, document it, and change the risky bits first. We do not rebuild a working system to make it match a diagram.
Usually. If the machine will not boot after a kernel update, someone has to stand in front of it or use a remote console. We say which one before the window.