Virtual server maintenance
Control of allocated resources, guest system updates and snapshots before changes.
Eight services, from a one-off OS reinstall on a workstation to ongoing maintenance of the domain and the virtual environment.
Windows and Linux on workstations: a clean install, transfer of the profile and documents, drivers and working software.
Cleaning up startup items, disinfecting the system and replacing the bottleneck in the configuration. Often cheaper than buying a new machine.
Configuring roles and services, updates, resource monitoring, log review and preventive work before a failure.
The domain, group policies, access rights and tidy accounts: anyone who has left no longer has access.
Control of allocated resources, guest system updates and snapshots before changes.
Several servers on one machine: savings on hardware, fast rollback and migration between nodes.
Update failures, a corrupted database, slowdowns at quarter end, licence and session problems.
Turnkey commissioning of a new server or storage system, from rack mounting to handover into service.
The dullest part of administration is what prevents outages. The work runs to a schedule, not whenever someone remembers.
Daily. Prevents a node failing unnoticed and being discovered a week later.
Daily. Prevents the database stopping because a disk is completely full.
Monthly. Prevents the biggest surprise: a backup that will not restore.
Monthly. Prevents exploitation of already known vulnerabilities.
Quarterly. Prevents former employees from accessing systems.
We document the infrastructure first and administer it second. A diagram, a list of services, where everything sits and what depends on what: this is a document that stays with you. Without it, administration becomes one person knowledge.
A common situation. We start with an assessment: we find every server and service, work out what does what and produce a diagram. That takes one to four weeks depending on size. After that we administer from the documentation.
Before updating we take a snapshot or a backup, roll out to a test environment first if there is one, and do the work in an agreed window, usually at night or at the weekend. If something goes wrong, we roll back before the working day starts.
With both, including the Russian Linux distributions used for import substitution. A mixed setup, with the domain on Windows and some services on Linux, is normal for us.
If the company has many internal systems and constant change, an in-house specialist is valuable: they know the business better. In that case we take the infrastructure, the on-duty cover and the narrow specialisms, while they handle application-level work.
How many servers you have, what runs on them and who supports them now. We will run an assessment and show what needs attention first.
Request received
We can already see it. We will reply within one business day, and for urgent matters we will bring in the on-duty engineer right away.
City not found. Please check the spelling.