Monitoring & remote ops
1,800 sensors from servers to printers, remote management and scheduled patching — so we hear about a fault before the user does.
- Role
- Head of IT Infrastructure
- Period
- 2025 —
- Company
- Minta Gépgyártó Kft.
1. What I walked into
Faults arrived by phone: someone rang to say the printer, the network or the system was down or slow. Updates were installed by hand, whenever there was time.
- there was no view of capacity
- remote help was a free tool, a different one on each machine
2. What I changed or built
One monitoring view from the servers to the printers, with alert rules that only speak up when something is really wrong. Remote management on every machine, and scheduled patching with a test group first.
- thresholds taken from real load, not guesses
- an on-call rota and an escalation chain
- a monthly capacity report
3. The numbers
1,800 sensors, 93% of machines patched within seven days. Outages reported by users fell by 40%, because most faults are fixed before anyone notices them.
4. The tools, and why these
PRTG for the infrastructure, because the network and the servers show up in one place; NinjaONE for the endpoints and remote help; PDQ for deployments, because in a Windows estate it runs with the least friction.
5. What it meant for the business
IT comes up in conversation less often, which is a good sign. Planned maintenance stays planned, and capacity grows from the numbers rather than from complaints.
- Stack
- PRTG
- NinjaONE
- PDQ
- Grafana