A strange thing happens when managed IT is done well: nothing happens. The computers start in the morning, email arrives, the files are where they should be, and nobody thinks about IT at all. That is the goal, but it can make an owner wonder what exactly they are paying for.
The short answer is that most of the work happens before you would ever see a problem. Here is what a managed IT provider (often called an MSP, for managed service provider) actually does on an ordinary day.
Watching everything, around the clock
Every computer, server, firewall and backup system we manage runs a small monitoring program called an agent. The agent reports health information back to our central platform all day and all night: disk space, failing hardware, services that have stopped, backups that did not finish, security software that is out of date.
Most of those reports say “all is well,” and that is fine. The value is in the few that do not. A hard drive that starts reporting errors on Tuesday can be replaced on Wednesday, during a planned window, instead of failing on a Monday morning with a full office waiting.
Monitoring also catches slow problems that nobody would notice by eye: a server gradually filling up, a backup that has been quietly skipping one folder, a laptop that has not checked in for weeks.
Patching: timely, not rushed
Software vendors release security fixes constantly. Microsoft, for example, publishes its monthly Windows security updates on the second Tuesday of each month, according to its own release schedule, with emergency releases in between when needed. Browsers, PDF readers and dozens of other programs have their own schedules.
Keeping up by hand is a losing battle, so we automate it. But automation does not mean installing everything the moment it appears. Our approach is to hold new patches briefly, test them, and then deploy them selectively, system by system. That way a faulty update gets caught before it reaches your accounting PC. We explain the thinking in Windows updates: timely, not rushed.
Backups, checked every day
Backups run on a schedule, both on-site (for fast recovery) and to the cloud (in case the building itself is the problem). The part people forget is checking them. Every day, someone needs to confirm that last night’s backups completed, and every so often someone needs to prove that a restore actually works. A backup that has been failing for a month is only discovered in two ways: by monitoring, or by disaster.
Security watch
Firewalls, antivirus and email filtering all produce alerts. On their own, those alerts are just noise in a log file. The work is in reading them, spotting the ones that matter, and acting: isolating an infected laptop, blocking a suspicious sign-in, or asking a staff member whether they really meant to log in from another country at 3 a.m.
Security tools reduce risk; they do not remove it. What makes the difference is that somebody is watching and responds quickly when something looks wrong.
Routine maintenance and consistent setup
Much of the day is small, dull, important work. Clearing out old temporary files. Renewing certificates before they expire. Checking that every new laptop is set up the same way, with the same security settings, so that nothing is forgotten. Replacing a firewall’s aging firmware. Automation handles the repetitive parts so our engineers can spend their time on the parts that need judgment.
Documentation
Every change we make is written down: which computer is where, how the network is laid out, which software licenses you own, how a particular system is configured. It sounds like paperwork, and it is. It is also the reason a problem at 7 p.m. can be solved by whoever is on call, not only by the one person who happens to remember how things were set up.
The help desk
This is the part you do see. Someone cannot print, a password needs resetting, a new employee starts Monday. Every request is logged as a ticket and tracked until it is resolved, so nothing gets lost in someone’s inbox. Tickets also build a history: if the same printer fails every month, the pattern shows up and we can fix the cause instead of the symptom.
Planning ahead
Finally, a good provider looks forward. Which computers are getting old? Which software is approaching the end of its support life? Is your Internet connection keeping up with how you work now? These questions turn into a plan, so replacements are budgeted rather than emergencies.
What to ask your provider (or yourself)
- Who is alerted if a server or disk starts to fail on a Saturday night?
- When did your backups last complete, and when was a restore last tested?
- How are security updates tested before they are installed?
- Where is your network documented, and could someone new find it?
- Is every support request tracked from start to finish?
If the answers are vague, the work is probably not happening. Our guide on how to choose a managed IT provider goes further.
How FTI does it
Our managed IT services are built on Kaseya for monitoring, automation, patching, on-site and cloud backup and documentation, and secured with Sophos across firewalls, endpoints, email and Wi-Fi. An AI layer connected to our monitoring, security logs, tickets and documentation reads across all of it, all the time, and puts the full picture in front of our engineers. The engineers decide and act. Behind it all is our 24/7 help desk, with senior engineers on call.
When it works, you should hardly notice us. That is the point.
