Unlock the true value of your RMM investment by leveraging the capabilities of Kaseya using the below recommendations and best-practices for automation.
- Customize Reports - Real-Time & Accurate:
In Kaseya, reports are published from report sets. Report sets are the default settings and formats based on the data extracted out of the database with certain defined parameters. You might have observed that sometimes these reports are inaccurate, due to gaps in audit conducted, leftover files, or traces and cached data.
In order, to fix that you can customize these and run a report validating the data real-time at the machine level using the agent procedure/scripts.
Example: Validating an application install status, version details or any OS information/configuration settings based on the registry values and publish it directly on the manage agents tab using the custom fields to create a dashboard.
- Auto-Fix Alerts/Issues:
Lot of alerts are generated by RMM’s on which we follow a defined process and out of these some of the redundant tasks can be automated through scripts. Those can be applied in Kaseya as auto fixes on the alert itself (Alert, Monitor Set or Event Log Alert). This can assist in remediating various issues like low drive space, service restart, Windows agent updates etc. and saving lot of time for the engineers.
Example: Kaseya identifies a machine with low drive space and a script can be created and applied to remove temporary files, logs, software distribution folder and recycle bin etc.
Example: Attempting to restart the stopped services multiple times at a defined interval.
- Troubleshoot Without Accessing Machine:
Using features like Live Connect manage and troubleshoot issues like Services, Processes, Registries, File transfers, running CMD or PowerShell commands, scripts etc., you can troubleshoot issues without taking a remote session of the machine with even user working actively on the machine.
Example: Use Live connect on demand to have a temporary agent installed on the machine for 0-12 hours. Troubleshoot and the agent would be automatically removed post defined period.
- Automate Client/Machine Onboarding:
- Install a Kaseya agent on the Domain controller
- Create an agent package for the group/organization
- Run the discovery with option “By Agent” from the DC and attached the defined agent package
- Create configuration policies – Patching, alerting etc.
Example: With above steps, Kaseya would automate the entire on-boarding cycle. First, it would install an agent on all the discovered endpoints and based on the applied policies it would have the global settings and customized group configuration implied on these machines.
- Pre- & Post-Patching Procedures:
Based on your need, define pre- & post-patching procedures, especially suspending and unsuspending alarms during this aforesaid period. Generating maintenance notifications to start informing users about the maintenance activity and recommending keeping the system available/online so that the patching process can complete.
Example: Using pre & post-reboot procedures to ensure certain application/services are running or specific user is logged in etc.