Connecting The Dots Seeing things past it's face value

K6 Countdown..

Although I love the idea in upgrading to K6, its a nightmare to think about as well.

For thoes of you who dont know, Kaseya runs everything off of scripts.
Recently Kaseya has taken away a variable that allows you to run SQL queries and use them to better your service offering.

Here is an example:
Say you have monitor sets that monitor the CPU of a workstation.
Currently: You have to rely on your RMM to inform you that the workstation is running on High CPU... SO WHAT. Now you spend 20-30 min remoting into the machine because of High CPU, you may not get in) then trying to run task manager... bla bla you know the story.

What Kaseya SHOULD do: (and actually I have it working on my system)
You should run a script that runs a program to check what task is running and send this info back to you, but here is the next issue... what if you already know that 3DStudio Max may use 100% CPUfor a long time... You would like to create a table in SQL of Trusted APPS, and blacklisted APPS. Based on this info you can DO something like:
Hello User, we notice your running FISH screen saver and it is reccomended that we shut this off as it causes your machine to run HOT and could fail your Cooling Fans sooner. Would you like us to turn this off for you? YES NO.

WOW what have we done here ladies and Gents? We have Proactivly taken care of something.

But with the recent hot fixes Kaseya has stripped out the commands that allow me to do this.
And I know there are a bunch of people doing this, WARNING. K6 will whipe all that hard work you spent in differentiating your company.

The Arguement is this from what I understand of it:
We have to close this cause loop hole as it could be too powerful for the IT companies to use.
So paraphrasing this means you would open up pandoras box having this power, EEEHHum.
Here is my Arguement:
IF you own Kaseya you have already opened up Pandora's box. Here is how:
Scripting by itself is scarry if you dont use it right.
Case in point... if you dont know that a machine (your about to run a delete all contents of this directory script) that is currently not logged in with a user, your script will assume the account of SYSTEM. System's home directory folks is c:\windows\system, you run this script and you will delete all contents of the system directory.... here is the scarry thing, you will do this on ALL machines you manage.

GUYS this is why I choose Kaseya as an RMM solution... NOBODY can do this today, and why I am willing to look for someone who can. Kaseya is shutting the doors on my being an innovator, when that happens I need to find somthing else, and is why I have thrown the challenge for all RMM tools. Show me that you can do this sort of thing and I will be interested in knowing more about your product...

People who work for Kaseya should know that Kaseya is the Innovators Toolbox, when you do things like this you kill the innovators.