In our environment we have SAN attached storage so the "Low Disk Space" Notification out of the box was just not cutting the mustard for us. We were getting returns on all mapped drives disk space and having to sift through that data each week.
Well, I call "enough's enough" on this one. But when I got down to the nitty gritty it was not that bad. The only issue I found was after defining the drive and determining at what point do I want a notification to go out regarding a servers c:\ drive space (we have it at 5 GB), it was determining if the system was a VM or not.
To address the VM systems (which is ever growing in our environment) I simply added a line into the SQL on each of my notification queries and created 2 notification policies. One for VM and one for physical machines.
Below is the SQL query for the physical machine low disk space.
The only change that needs to be made to check VMs only is remove the NOT from "AND SN.[system manufacturer] NOT LIKE 'VMWare%'"
SELECT Wrksta.Name as 'Name', t1.[Device ID] as 'Drive', t1.[Size in MBytes] as 'Disk Size', u1.[User] as 'Primary User', t1.[Free Space in MBytes] as 'Free Space', Wrksta.Guid as 'ResourceGuid' FROM Wrksta INNER JOIN AeXInv_AeX_HW_Logical_Disk t1 ON Wrksta.WrkstaId = t1.WrkstaId LEFT JOIN AeXInv_AeX_AC_Primary_User u1 ON Wrksta.Wrkstaid = u1.WrkstaId LEFT JOIN dbo.Inv_AeX_HW_Serial_Number SN ON Wrksta.GUID = SN._ResourceGUID WHERE u1.[Month] = DATENAME(mm, GETDATE()) AND t1.[Device ID] = 'C:' AND cast(t1.[Free Space in MBytes] as int) < 5120 AND SN.[system manufacturer] NOT LIKE 'VMWare%' ORDER BY Wrksta.[Name]
From tweaking the SQL just a little you can report on your own needs for low disk space. Also remember to turn on the notification as well as check the delivery option you would like. We have a separate Helpdesk server so this notification policy e-mails a harvested mailbox which then creates the incident.