KACE Product Support

You would need some sort snmp cleint on the workstations that watch for services being disabled and would let you know that was happening.  The kbox just thinks the machine was shut down when the client quits talking to it.

With 3.6 they now support agent-less protocol also, so they may be a way to detect this with version 3.6. of when the box goes from agent protocol to agent-less. 

Provisoining running may also fix this when they stop the service, that you would have to test.

You could also create a scheduled task and place that on your machines that will check at a certain interval and start the service if it is not running.  But as an admin they could just delete this task once they figured that out.

You should do some testing to see if they really need to be admins, We have found 99 percent of the time we just have to give extra rights to files/directories/registry key sets and that lets user do what they need without being an admin.

Not a clean way but you can write a batch file to check for the service being on, stopped, disabled...etc and turn it back on. Then put the batch file as a start up item. If your users are to savy you could use that to ensure that the service is always on. 

If they don't reboot alot, you could create a scheduled task to execute it daily as well. 

It would be nice if KACE password protected the uninstallation and added some service fault tolerance. 

Have you looked into creating a Notification in Kace?

You can schedule it to run every 15 minutes and email a list of all deiveces that are disconnected. You can customize it to specific OS or devices.