Would it be possible to expand the number of API endpoints available for the RMM? While the API is useful for gathering information about systems, it doesn't have much in the way of being able to perform many built-in operations that exist in the web application, like check for and install patches, run single line commands on the system, being able to run scripts on a system and not just tasks, add tags to systems, etc.
This would be great for creating custom automation and would help with removing a lot of tedium in cleaning up small alerts.
i´m testing this RMM atm.
Is it possible to implement WOL on a Probe?
For example choosing the probe then the Machines Show up which are on the same Network or same Customer and Option to do WOL.
If you´ve many Machines to Manage You would Need to Edit Firewall Rules for each Machine and Edit the Settings of each machine.Would be way to much work.
I know this would be a major change in the reporting interface, but how about an option to interact with the results of a report.
Maybe one can choose an additional "Report Format" when editing a report and have an option for Interactive?
When this is enabled the output of the report is immediately displayed in web format with hyperlinks to automate certain tasks by sending a back-end task/script to the agent.
Report Interaction Script Task (Relayed to the agent)
Applications link next to each agent to uninstall the application
Assets link to create asset tag if none exist
OS Patching link to assign Policy / Update now
3rd Party Patching link next to each agent to update the application
Drive Usage link to run a temp files cleanup job
Anti-virus install AV / Run Scan / Update (not sure how this ties in to the existing Kaspersky deployment)
So I am really enjoying Pulseway, the systems are mostly well designed and work really well. They are simple and have no huge data entry overhead like other systems (Autotask).
However, there are some improvements to be made in consistency through out the application. For example some text boxes for paragraphs of text allow you to tab into and out of them. Others don't some places where I click on a ticket opens the ticket in another separate popup window, others a new tab.
The choices in made in some designs are really weird. For example, most save buttons are at the bottom of a dialog, a couple are at the top. That kind of change of process creates a headache when you just typed a novel on what was done and you miss the button and find the dialog is gone, and your masterpiece with it.
I don't have the time right now to show/point out each of these that I have found, but I will be adding each of them here as soon as I can. I would like to think that the Dev's can find these faults themselves, but then you would think that if they knew those problems should have been taken care of already.