KACE Product Support

You can use scripting to verify that a service is running and stop or start it based on its status. What exactly would you like to do to the service?

Sorry for the delay in replying.

I would like to have the ability to monitor, report, and remediate any registry and service settings. For instance, have the KBOX run a scheduled scan of a server's registry and service settings, generate and email a report of its findings and then remediate any deviance automatically (optionally will be for an admin to manually remediate).

I thought someone said this was possible at the KACE Konference, but I'm not finding anything that outlines how to do it.

Thanks,
Errin

You can use custom software inventory items to pull registry information for your machines. You can then create a custom SQL report to pull that information out of the KBOX database and email the report to you. As for Windows services, you could do the same thing. The limitation is that the data will only be accurate to the last inventory check-in of each client. So, if your check-in is set to 4 hours, your data may be outdated by up to 4 hours. To remediate any issues, you'll have to use scripting. You're really looking at two totally different aspects of the KBOX. For reporting, you'll have to use inventory data. And for monitoring and remediation, you'll have to use scripting.

If you had a small number of services you wanted to enforce then starting similar to what Andy is saying you could use a custom inventory item or the list of running processes / services as part of a SQL query that would be a report and / or a filter to automatically label that machine. You would have some online kscripts that run on a fairly frequent schedule to hit those machines and run the logic that you want to check that service against. I would avoid an online kscript if your schedule has to be really agressive for a large number of machines.

In the case of a large deployment you could have some polling mechanism deployed to the machine itself. While any problems and remediations would be localized you could still report on it. If your remediation efforst could be logged as file or registry entry then you could capture the most recent problem as a custom inventory item to machine inventory where it could be reported on.