The loss of monitoring alert occurs when devices are no longer communicating through either the SNMP or WMI protocols. If a device stops communicating over these protocols Barracuda RMM is unable to alert, monitor, or collect information on those devices.
The following scenarios guide you through issues that may have caused your devices to stop communicating through SNMP or WMI protocol.
Scenario 1: SNMP/WMI Enabled
- Check to see if your device is SNMP/WMI Enabled.
- If it is a domain, confirm that the account for MW Service is a Domain User, Domain Admin and Enterprise Admin in Active Directory.
- Confirm the correct account/password in the Configure Onsite Manager utility.
Scenario 2: DNS Issue
- Confirm that the DNS entries are correct for the devices.
- Log into the domain controller and check both forward and reverse lookup zones for these devices.
- Ensure that there is no discrepancy or duplicate entry.
- Flush our DNS settings after cleaning up to discover the devices as WMI enabled.
Scenario 3: Policy Module
The device is verified by the type of policy module applied. Therefore, if an SNMP based policy module is applied to a Windows device with no SNMP, the alert can be triggered when it is not valid.
- Check what policy modules are applied to these devices and ensure that none were added in error.
- If the policy modules are correct, check to see if the Windows Management Instrumentation Service is running.
- If the Windows Management Instrumentation Service is running, check to see if there are any WMI errors in the onboarding overview of the device.