- Linux (all major distributions)
- Windows Server
- Proxmox VE
- VMware ESXi / vSphere
- Ceph
- and more...
Subscribe to GEN
Login to GEN
Most problems that cause outages, breaches, or data loss were preventable. Unpatched software, unchecked logs, disks filling quietly, backups that stopped working weeks ago. These are the things that bite. GEN's Preventative Maintenance service runs a structured, scheduled programme of work across your estate to make sure none of them do.
Our PM platform maintains an asset registry of your systems and drives maintenance activity on two tracks: scheduled work at defined intervals, and condition-triggered work in response to events such as new CVE disclosures, vendor advisories, or threshold breaches detected by monitoring. When a task is due, an engineer connects, works through the checklist for that asset type, and logs the outcome. Nothing is marked complete until it has been verified.
Preventative maintenance runs across the full technology stack: servers, desktops, storage, virtualisation, network, and hardware. Each platform has its own specific maintenance checklist reflecting what matters for that type of asset.
Each maintenance visit, whether scheduled or triggered, follows a structured checklist for that asset type. The engineer connects, works through every item, and records the outcome. The result is a verified record, not a presumption.
Security & Patching
Logs & Health
Backup Verification
Network & Hardware
Every managed asset has a YAML profile that describes exactly what is expected on that system. Before an engineer begins a maintenance visit, they have a complete picture of the asset: what should be running, what should not, and what normal looks like. The job is then straightforward: verify everything matches the profile, and investigate anything that does not.
The profile is the baseline. An unexpected open port, an unfamiliar user with sudo access, a service that should not be running, or resource usage outside the expected range; all of these are immediately visible because the engineer knows precisely what the system should look like.
We have tooling that takes the profile and automates much of the comparison work: checking open ports against the expected list, detecting new or removed user accounts, flagging unusual file ownerships, identifying services not in the profile, and spotting excessive log file generation. The tooling produces a diff of what has changed or drifted since the last visit, and the engineer's focus goes straight to the things that need investigation rather than manually working through the whole checklist from scratch.
That is what makes the process fast. An experienced engineer can complete a full PM of a Linux server running a LAMP stack in around ten minutes, not a half-day exercise. Ten minutes weekly, monthly, or on whatever schedule suits the asset.
Maintenance work runs on two tracks. Scheduled work fires at defined intervals, daily, weekly, or monthly, depending on the asset type and criticality. Condition-triggered work fires when something changes: a significant CVE is published against software you run, a vendor releases a critical advisory, or monitoring detects a threshold that warrants investigation before it becomes an incident.
Every maintenance visit produces a written record: what was checked, what was found, what was done, and whether any items require customer attention or follow-up. Reports are held in the platform and accessible at any time.
The majority of serious incidents are not caused by sophisticated attacks or freak hardware failures; they are caused by things that were known about and not acted on. A patch that sat in the queue for three months. A backup that silently stopped running. A RAID array that had been degraded for weeks. A log directory that filled the root filesystem overnight.
Preventative maintenance closes those gaps systematically. The estate is not assumed to be healthy; it is checked, verified, and kept that way. For organisations that need to demonstrate due diligence around security and availability, the maintenance log also provides an auditable record of the work that has been done.