Discovered Assets

In Discovered Assets, you can see a list of available devices on a network. These devices can be discovered either by a discovery job or an asset scan, though in most cases an asset scan auto-imports devices to the All Devices view.

Devices will end up in Discovered Assets if a device is deleted from the All Devices view and Set device as unmanaged is selected or from agent/probe discoveries that are not set to auto-import. Note that if a device's asset data has not been updated in more than 30 day, it will delete the device instead of sending it to Discovered Assets.

Devices in Discovered Assets are maintained, regardless of original source, until the asset data for that device has not been updated in more than 30 days. Recurring discovery jobs and asset scans from an N-central agent will update and refresh this timer.

Navigate to Discovered Assets

To access Discovered Assets:

In the left-hand navigation menu, click Configuration.
Click Asset Discovery.
Click Discovered Assets.

Known Assets

The Discovered Assets section has two tabs: Discovered Assets and Known Assets. Under the Known Assets tab, you can find any Discovered Assets that were marked as Ignore. The next time a discovery job or asset scan is run, devices under Known Assets will be ignored.

You can add an ignored device later by running a discovery job and selecting Show Ignored Devices.

Probe-based discovery jobs cannot find a full list of asset data on Mac devices, so Mac device should not be part of recurring asset jobs if you are expecting asset data. After discovering Mac devices, allow the Mac agent to provide the asset data based on its daily asset scan.

Error Codes

Below is a list of common error messages returned during asset discovery:

Type	Error Codes	Exception	Parsed message	Resolution steps
WMI	AG_ERR_WMIREG_001	UnauthorizedAccessException	Unauthorized access when connect to Host	Verify that the probe credentials have the appropriate group memberships: Windows probe required privilege levels. If changing the probe username or password, make sure you reinstall probe with corrected credentials and run the discovery job again. Re-install a Windows probe with activation key.
WMI	AG_ERR_WMIREG_002	COMException	Access denied when connecting to	Verify that the probe credentials have the appropriate group memberships: Windows probe required privilege levels. If changing the probe username or password, make sure you reinstall probe with corrected credentials and run the discovery job again. Re-install a Windows probe with activation key.
WMI	AG_ERR_WMI_056	WMIAccessDenyException	Access denied when connecting to	Verify that the probe credentials have the appropriate group memberships: Windows probe required privilege levels. If changing the probe username or password, make sure you reinstall probe with corrected credentials and run the discovery job again. Re-install a Windows probe with activation key.
WMI	AG_ERR_WMI_028	InvalidParameterException	Invalid matrix implementation method. Key =	Please rebuild WMI and run discovery again. (this needs a link to a good set of steps for modern Windows OS)
WMI	AG_ERR_DEF_001	InvalidParameterException	Invalid parameters	Please rebuild WMI and run discovery again. (this needs a link to a good set of steps for modern Windows OS)
WMI	AG_ERR_CMN_005	WMIAccessDenyException; GenericException	Exception caught when execute task	Please raise a support ticket in N-ableMe, and include the following device information: Customer, Site, Device Name, and Device ID.
ADMIN Share	AG_ERR_WMI_042	GenericException	Unable to connect to remote network resource.	Ensure the environment satisfies the checklist for the deployment type: N-able N-central deployment checklist (Domain) N-able N-central deployment checklist (Workgroup)
ADMIN Share	AG_ERR_CMN_003	GenericException	Exception	Please raise a support ticket in N-ableMe, and include the following device information: Customer, Site, Device Name, and Device ID.
Registry Query	AG_ERR_CMN_010	Issue with root key / sub key / value name/ method	Is Null(or)Empty	The registry key (provide path) does not contain the required information. Please verify that the registry key is properly populated.
Registry Query	AG_ERR_CMN_006	WMIAccessDenyException	Access Denied	Ensure the environment satisfies the checklist for the deployment type: N-able N-central deployment checklist (Domain) N-able N-central deployment checklist (Workgroup)
Registry Query	AG_ERR_WMIREG_002	WMIUnreachableException	Access denied when connecting to	Ensure the environment satisfies the checklist for the deployment type: N-able N-central deployment checklist (Domain) N-able N-central deployment checklist (Workgroup)
Registry Query	AG_ERR_WMI_028	WMIAccessDenyException	Invalid matrix implementation method. Key =	Ensure the environment satisfies the checklist for the deployment type: N-able N-central deployment checklist (Domain) N-able N-central deployment checklist (Workgroup)
Registry Query	AG_ERR_WMI_036	InvalidParameterException	Invalid matrix processing method	Please raise a support ticket in N-ableMe, and include the following device information: Customer, Site, Device Name, and Device ID.
Registry Query	AG_ERR_WMI_056	WMIAccessDenyException	Access denied when connecting to	Ensure the environment satisfies the checklist for the deployment type: N-able N-central deployment checklist (Domain) N-able N-central deployment checklist (Workgroup)
Registry Query	AG_ERR_CMN_002	InvalidParameterException	Invalid	Please raise a support ticket in N-ableMe, and include the following device information: Customer, Site, Device Name, and Device ID.
Registry Query	AG_ERR_REME_011	GenericException	Exception caught while processing WMI Request	Ensure the environment satisfies the checklist for the deployment type: N-able N-central deployment checklist (Domain) N-able N-central deployment checklist (Workgroup)
NetBIOS	NETTransport scan failed		UDPScan failed; An existing connection was forcibly closed by the remote host ErrorCode: ConnectionReset;	Verify that the probe credentials have the appropriate group memberships: Windows probe required privilege levels. If changing the probe username or password, make sure you reinstall probe with corrected credentials and run the discovery job again. Re-install a Windows probe with activation key.
SNMP	SNMP not accessible		Failed to scan OID 1.3.6.1.2.1.1.2.0	Verify that the probe can reach the specified port. Ensure the discovery job specifies the correct version of SNMP (v1, v2c, v3) to be used. Confirm that data from the specified device (IP) on the OID (list OID) is available to the probe using SNMP Walk and SNMP Get. SNMP troubleshooting.
SSH	SSH port 22 not accessible			The probe is unable to reach the device at (IP address) on port 22. Please verify that the firewall settings are correct and allow SSH over port 22 on the device.