Automatic discovery troubleshooting

Windows devices

Problem	Solution
WMI permissions not allowing probe to pull OS type and therefore device could not be classified.	Ensure Windows Firewall is turned off or configured as per the necessary Group Policy Changes to Windows Firewall.
The device is not part of the Domain (WMI permissions not allowing probe to pull OS type and therefore device could not be classified.	Ensure proper credentials are used that can access the `\Admin$` share of a device.
I don’t know why the device is not receiving an agent.	Try leveraging N-able N-central remote control – Remote Desktop after the device is imported into N-able N-central. Remote Desktop is accessible with an Essentials License. Remote Desktop does not require a local agent, but it does require the device to be configured for it along with a monitored probe.

These devices include Switches, Routers, Printers, Linux OS, macOS, and so on.

Problem	Solution
SNMP is not enabled on the device.	Ensure SNMP is enabled with read only access to the probe.
SNMP is enabled with a different SNMP community string than configured within the Windows Probe Asset Discovery Task.	Ensure the community string is defined in the discovery along with accepting packets from the probe. The timeout may need to be adjusted of the device is slower to respond.
I don’t know what this device is.	Try leveraging NN-able N-central remote control - web page after the device is imported into N-able N-central. The web page is accessible with an Essentials License.