It’s easy to get caught up in the monitoring aspect of the RMM business, but there is a lot of management to be done too. Moreover, you really don’t want to start a remote session just to delete or move files, start or stop services, log out users, pull system information, and so on.
It’s a huge help to create scripts for your most common tasks for two reasons.
First, you won’t have to start a remote session. Instead, you’ll simply be able to launch the script from your RMM console.
Second, you’ll be able to schedule these tasks, either through your RMM software or through the Windows Task Scheduler, so you’ll be able to run them at the most convenient time for you and your users. Depending on your RMM software, you may find the Windows Task Scheduler has more settings for triggers, repeats, delays, expiration, etc. In either case, after the tasks are set up, you only need to set up a notification to check the status of your tasks.
So it’s definitely to your advantage and to the advantage of your users that you learn some Batch, Visual Basic, or PowerShell scripting to automate your management.
Finally, more sophisticated RMM software has more powerful task execution capabilities, more specifically conditional automation. This means not only that you can set up conditions to trigger tasks, but also subsequent and different actions to be taken if the issue recurs again. This basically creates the ability for your RMM software to auto-remediate the problem and then, if needed, only send the notification after various auto-remediation attempts fail.
If you invest the time in writing the needed scripts and configuring the tasks and workflows of tasks, this kind of RMM automation saves you a lot of time chasing after notifications.