A smarter way to handle Kaseya Low Disk Space Alerts for PCs

Written by Tullibo

Topics: Featured, Kaseya


It still amazes me the volume and number of alerts and events that MSPs are handling “manually” or with human labour when Kaseya can in many instances auto-heal or auto-resolve the problem.

One area where this is really evident is around disk space monitoring on workstations or end user PCs. I’ve seen many MSPs handle each and every alert for low PC or workstation disk space. The machine runs out of disk,  the technician calls the client, tells them they have low space and asks them to cleanup their files and so forth. The number of times workstations run out of disk space and the sheer number of workstations MSPs manage can make this a massive real dollar cost to an MSP business. On the flipside, ignoring low workstation disk space is likely to cause you to breach SLA or your monitoring obligations.

Here’s how I handle workstation low disk alerts and maybe how you should be handling it too!

  • I monitor for 750MB free or less for more than 2 hours – I do this using a monset instead of the inbuilt disk space alert. The inbuilt alert pulls its data from the last audit and is not realtime. Therefore not really reliable to use in a monitoring sense. It’s also based on % free, on a 500gb disk 5% free is a lot more than on a smaller disk, say 40gb so again you’ll get big variances in the quality of your monitoring with this approach.
  • Instead of alerting/alarming where a human has to intervene, I automatically trigger a script that generates a popup telling the user they have low disk space and that we’ve queued a disk cleanup for them. It also advises them that they need to cleanup their files as they’re out of disk and if they need help in doing this, then to call the helpdesk.
  • Kaseya will then trigger a series of scripts that runs Windows Disk Cleanup, Clears IE History and runs Windows chkdsk
  • After the scripts are done, they then write an information event to the Windows Event Log recording that the machine ran out of disk (so that a technician that may be troubleshooting an unrelated problem for the user knows Kaseya has worked on the machine) and I also write an event to the Kaseya agent log.
  • I then have a weekly report that shows all machines that have run out of disk space in the last week – this enables you to keep an eye on the status of workstation low disk alerts without investing a massive amount of time. You can also use this to show low disk space activities on your Executive Reports.

I really love this approach as it’s totally automated once setup, it’s still proactive, it delivers real value to your client and they actually see this value, it’s easy to report on and most of all it removes the majority of the cost associated with monitoring workstation disk space thresholds.

If you need help getting your Kaseya monitoring back on track I’m available to help – head to the Contact Us page and drop me a line and we can talk further.