Allow users to define multiple probes and bundle the service in the agent. With more networks going to Azure AD (Office 365), we are needing a solution that does not require servers. This will open up to more site assignments without adding network complexity. 1) Create a group heatbeat that checks the probe status directly between local devices on a schedualble interval. 2) On each Probe a small xml type document ...more »
On older Mac versions, there was the ability to run Manual Maintenance Tasks on the local device. This functionality seems to have been taken away in the latest Mac Agents, and I would like this to be brought back for Mac Agents.
Have the ability to configure and send notifications based on the last time an agent has communicated with the NCentral server. The purpose would be to review this on a monthly basis and connect with clients about devices that are offline to help keep NCentral more organized.
I know there are filters and dashboards that can be created, but the ability to generate a PSA ticket would also be nice.
Right now Log Level can be set per Device or across the board.
Log Level should be an option from the All Devices view as well
It would be good if we could see which devices have agents and probes installed. Mostly probes.
So maybe add a symbol in the Features column under All Devices view that tells you if a Probe has been installed.
I would like more redundancies in place to restart the Advanced Monitoring Agent. I set the Advanced Monitoring Agent to restart if stopped via Windows Services and the regular check. Service does not restart client reports there are no dependencies for the service to restart and am forced to manually restart it. This seems to happen all the time, so I would like to have other redundancies in place to automatically ...more »
I want to determine whether the logged in user is a Microsoft Azure, AD, Workgroup account in used by an agent. This would be most importantly when deploying agents, when auto-discovery-and-probe finds a windows device and can't install the agent due to credential mismatch, because this device is on the network but is part of some other domain controller, Azure, AD, or Workgroup. This is specially problematic with windows ...more »
This is to request better wording for error messages when attempting to move a device from one customer/site to another. Referring to the attached example, the probe on this site was out-of-date. While the bold text indicates such, it's alleged that the font without any styling could lead the user to believe that the device has been mis-identified as containing a probe, or that the device being moved is, itself out of ...more »
The ability to call Custom Details into variables during automation policies would be very helpful when you are tying to filter options
Since KES 11 is release since a few days, it would be nice that RMM can support virus database check on KES 11
ATM, KES 11 is not detected by RMM.
The monitoring service connectivity exists on each windows device, but the default windows firewall blocks incoming ICMP request.
During installation of the agent, is it possible to create a firewall rule to allow this traffic so that this service isn't in error by default.
Enable column with Agent version installed on Device to make it easier to control agent versions in Dashboard
Habilitar coluna com versão do Agent Instalado no Dispositivo para facilitar controle de versões dos agentes no Dashboard