Said It Here

How do solo sysadmins handle endless ad-hoc software and system requests?

Management constantly drops drive-by requests for custom workflows, phone system changes, and random integrations on solo administrators. Hacking together these quick fixes leaves admins stuck maintaining half-baked solutions forever while actual infrastructure rots.

What people tried

Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.

  1. 1
    Pushing back case-by-case until burnout occurs
  2. 2
    Hacking together quick solutions to satisfy immediate leadership demands
  3. 3
    spin the old software up in a virtual machine
  4. 4
    isolate the software by cutting back or eliminating internet access
  5. 5
    clone the hard drive and keep the old machine running
  6. 6
    refuse requests based on cyber insurance policy requirements

In their words

Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.

r/sysadmin3 people · September 2026

How do other solo admins handle the endless stream of "quick CRM/phone system tweaks"?source ↗

Curious how fellow solo sysadmins survive this, because I'm drowning.source ↗

Management loves to drop drive-by requests for custom workflows in our CRM, weird IVR routing changes in the phone system, or random third-party integrations.source ↗

I hack together a solution so they get their shiny new toy, and then I'm stuck maintaining someone else's half-baked workflow forever while actual infrastructure rots.source ↗

SlowkayCoomer · r/sysadmin · 21 upvotes

If it’s not supported anymore by the maker, I don’t support it. We find alternatives that are. End of story.source ↗

trborgan · r/sysadmin · 1 upvotes

I got asked to build gcc 2.x (32bit) for aarch64. That's where I drew the line.source ↗

New-Perception-7209 · r/sysadmin · 1 upvotes

Where this came up

People with this problem also raised