Managing Checks FAQs
To run checks in the N-sight RMM Dashboard, you must be using the Mac, Linux, and/or Windows Agents.
You can continue to configure Checks via the Windows Agent and any Agent side changes take precedence over Dashboard modifications. Where changes are performed on both the Dashboard and Agent simultaneously, the updated Agent configuration is used.
Any changes you make to the 24x7 or Daily Safety Checks using the N-sight RMM Dashboard are downloaded to the Agent and applied the next time the Agent reports in, Checks run etc.
All communication between the Monitoring Agent and our central servers is initiated outbound using HTTPS over TCP. No additional firewall port configuration is required.
However, if the network’s firewall or Virtual Private Network (VPN) incorporates Deep Packet Inspection (DPI), an intelligent firewalling feature designed to examine all network traffic (including SSL) that passes through the firewall.
DPI examines all elements of these data packets and depending on the aggressiveness of this inspection, it may potentially interfere with the operation and performance of our Agent and associated modules by blocking of delaying communication with our systems.
To avoid DPI interfering with our systems, we recommend you add a rule to exclude or disable DPI for our traffic (if DPI is enabled on the firewall).
These configuration settings vary from vendor to vendor and are documented in their support material.
Web Protection and Packet Inspection
Despite the duplicate inspection of each packet, the use of two packet inspectors (including Web Protection) on the same network should not significantly impact on performance if the inspectors use different drivers.
However, conflicts will occur if both inspectors attempt to use the same driver to examine the packets. Due to the potential performance issues, we would recommend disabling Web Protection on those networks where the DPI component leverages the same driver as Web Protection.
Where an issues is experienced downloading the files, the Agent will attempt to redownload the files during the next communication cycle.
Monitored computers are not browsable from the N-sight RMM Dashboard when add a Check, so rather than search for the elements when configuring the Check, you must enter the information to query. Where problems are experienced with the entered information, i.e. the Check fails, it can be amended via Checks, Edit Check.
Examples of the Check types that require specific information include the File Size and the Bandwidth Monitoring Checks.
Where you have opted for one of our remote access solutions (Take Control or Remote Background Management) you can directly connect to the device from the Dashboard to check the required details when configuring the Check.
Checks are immediately removed from the N-sight RMM Dashboard and deleted from the Agent after the next communication cycle.
Check deletion is a non-recoverable action. Once you confirm the deletion, all information for the Check is removed, including history.
You can run all checks at once or run specific checks using the N-sight RMM Dashboard.
- On the N-sight RMM Dashboard North-pane, multi-select the target Devices (use Shift and left-click to choose a range or Control and left-click for specific machines)
- Right-click one of the selection and select Run Checks
- On the N-sight RMM Dashboard North-pane, select the target device
- Go to its South-pane Checks tab
- Multi-select the target Checks (use Shift and left-click to choose a range or Control and left-click for specific Checks)
- Right-click one of the selection and select Run Check(s)
Any configured and active Check appears on the N-sight RMM Dashboard and depending on how you use the tool, there may be multiple versions of the same Check, but with different thresholds. For example, two Disk Space Checks, one with a 15% alerting threshold (warning) and the second with a 10% alerting threshold (critical).
Updated configurations are not applied if the Agent console is open, as you may be in the process of managing the Checks. The configuration update only takes effect when the Agent console is closed.
As part of the check update process, the Agent writes the status of the downloaded configuration file to the update.log contained in the Agent installation folder, C:\Program Files (x86)\Advanced Monitoring Agent.
If the Agent upload contains incomplete Check results, an Agent Problem Alert is generated to notify you of the issue on this specific computer. The N-sight RMM Dashboard displays the last successful upload time.