UAEN

cd ~servicesserver-support.md

Server administration and support

I take your server on for support: I watch its health, backups and security, update it on time and respond to failures. So the office keeps working, and you don’t have to call the admin over every little thing. Basic tasks you can do yourself, from a panel in Telegram.

For
offices with a server, companies without an in-house admin
Format
remote
Under the hood
PowerShell, monitoring, a Telegram bot
ls ./cases/

When you need support

There’s no in-house admin, and the server is the heart of the office: without it, work stops.

Someone else set the server up, there’s no documentation, and nobody knows exactly what’s on it.

Small tasks — adding an employee, changing a password, restarting the server — keep waiting until someone has time.

What’s included

  • Monitoring: disks, memory, services, logins, licences, with alerts in Telegram.
  • Backup checks and regular test restores.
  • Security: change control, permission audits, closed ports.
  • Planned updates, with a state snapshot and a rollback.
  • Staff and access: new people, VPN keys, passwords, offboarding.
  • Help with programs on the server: access, printing, scaling, launch errors.
  • A Telegram panel for the owner: who’s working, login blocks, restarts, server status.

How I work

  • A watchdog compares the server with a baseline every hour and reports any unexpected change.
  • An audit before changes, and every change is agreed with you.
  • Changes are made with scripts, with a state snapshot and a separate rollback script.
  • Everything goes into a log: what, when and why it was changed.

Examples from my projects

cat ./server-office.md19 workstations under control from the owner's phone

The office owner called the admin over every little thing. Now he has a Telegram bot with a Mini App panel: he sees who's working, shuts off logins, adds people and restarts the server himself, from his phone.

read the development story →cat ./remote-office.mdA remote office for 19 workstations

In about a week, fully remotely, I brought up a new terminal server for an office: 19 people work through their own VPN, the server is invisible from outside, and nightly copies come with a tested restore.

read the development story →

How the work goes

  1. 01
    Brief

    We dig into the task and agree on what counts as “done”.

  2. 02
    Prototype

    I show a mockup or a demo on a test bench before the main code.

  3. 03
    Build

    In small stages. A backup before every change, a rollback for each.

  4. 04
    Testing

    First on a copy of your environment, then on the live one.

  5. 05
    Handover

    A guide, I explain how to use it, and I stay in touch.

Questions

Can you take on a server someone else set up?

Yes. First an audit without any changes: what’s installed, what the risks are, what’s worth fixing. Then a plan agreed with you.

Can I do basic things myself?

Yes. A Telegram panel lets you see who’s working, block logins, add people and restart the server from your phone. That’s how it’s done in the “Office server” case.

How fast do you respond to a failure?

Server alerts arrive in Telegram immediately. Specific response terms are fixed in our agreement.

How much does support cost?

It depends on the number of servers and the scope of work. I quote after the audit, once it’s clear what exactly needs supporting.