Unmanaged devices on your network, no longer invisible.
Every network is full of devices that no network tool manages: PCs, servers, printers, IP cameras, phones, UPSs, BMCs, IoT boxes, a vendor appliance, a switch nobody has the password for, a box plugged in last week. ConnectMyAssets keeps everything that answers on your network. Network devices it can log in to become managed assets; everything else becomes an unmanaged device, with what it says about itself, its open ports, services and certificates, and the reason it is not managed. Shadow IT turns into an actionable list, and your network inventory stays complete.
Everything that answered on the network without becoming a managed device, with the reason for each.
USE CASES
Why unmanaged devices on the network matter
Shadow IT discovery
Devices that nobody declared still answer the scans. Each one is listed with its subnet, its asset group, its MAC address and vendor when a collected switch or router sees it, so you can find its owner and decide what to do.
Failed or missing credentials
A password changed on the device but not in the Vault, a new site without credentials: the list shows which hosts refuse which credentials, so you fix the cause instead of guessing why a device is missing.
A changed host key
A device that suddenly presents a different SSH host key may have been replaced, reinstalled or impersonated. ConnectMyAssets stops and tells you, instead of logging in blindly.
Audit completeness
Auditors ask what is on the network that you do not manage. The unmanaged devices list answers with facts: addresses, reasons, services and dates, exportable at any time.
CAPABILITIES
What ConnectMyAssets still gathers about unmanaged devices
No login does not mean no information. An unmanaged device gets its own page, with everything the network can tell about it.
01
The reason, explained
Credentials refused, no credential, vendor not supported, host key changed, collection not allowed by a scan rule, licence quota reached or transport error: each host says why it did not become an asset, with the message of the collection engine.
02
What the host says about itself
The SSH banner, the last prompt received and the vendor profiles tried, plus the names of the Vault credentials sent (never their values) for users allowed to see them.
03
Occurrences and history
First seen, last seen, the number of scans that found the host and the last run: tell a device that has been there for months from one that appeared yesterday.
04
Open ports, services and certificates
Unmanaged devices receive the same port audit as assets: each open port with its identified service, product and version, and the TLS certificate it presents. Expired and self-signed certificates can raise alerts here too.
05
Network context
The declared subnet that contains the address, linked to the IPAM, the asset group it is filed under, and the MAC address and vendor found in the ARP tables of your collected devices.
06
The host toolkit
Ping, TCP ping, continuous ping, traceroute, port test, certificate, HTTP request, DNS, path MTU and SSH negotiation, run from ConnectMyAssets with results shown live and kept 30 days. No credential is used.
07
Scan this host
Fixed the credential or the scan rule? Rescan the single address from its page. A host that authenticates and whose vendor is recognised becomes an asset, identified by its serial number.
08
A list that stays clean
A host leaves the list when it becomes an asset, or when consecutive scans find it silent. Soron can alert you on new unmanaged devices, filtered by reason, and every deletion is audited.
SEE IT IN ACTION
A printer that answers on the network: its open ports, services, versions and self-signed certificate, why it is not managed, and the tools to find out more.Filter by reason to fix causes in bulk.Everything known about a host you cannot log into.
HOW IT WORKS
What makes a device unmanaged
An unmanaged device is anything that answered on the network during a scan (a PC, a server, a printer, a camera, a network device that could not be collected) without becoming a managed device. Each reason points to a different action.
Credentials refused
The device rejected every credential bound to its group. Check the account on the device or update the credential in the Vault. Refusals are never retried blindly, which protects your AAA accounts.
No credential
No credential is bound to the asset group of the address or to its parents. Bind one and scan the host again.
Vendor not supported
The device answered over SSH, but none of the vendor profiles recognised it. It stays inventoried with its banner, ports and services.
Host key changed
The SSH host key differs from the one trusted on first use. Confirm the device was replaced or reinstalled before trusting the new key.
Collection not allowed by a scan rule
The address is in a range set to discovery only, or discovery and ports. Nothing beyond that level is sent: no SSH connection, no login.
Licence quota or transport error
The licence has no credit left for a new asset, or the SSH session failed on the way (timeout, reset, negotiation). The message of the engine says which.
A PRACTICAL WORKFLOW
From an unknown address to a managed asset
01
Scan
Every host that answers and cannot be collected is listed with its reason.
02
Sort
Filter by reason, subnet or group to find the causes that matter most.
03
Diagnose
Read the banner, the ports and services, and run the toolkit from the host page.
04
Resolve
Fix the credential or the rule and scan the host: it becomes an asset.
FAQ
Your questions, answered.
Prepare your project and define your scope.
What is an unmanaged device in ConnectMyAssets?
It is any address that answered on the network without becoming a managed device: a PC, a server, a printer, a camera, or a network device whose credentials were refused or whose vendor is not supported. ConnectMyAssets keeps it with the reason and, depending on what it answers, its SSH banner, its open ports, services and certificates, instead of silently ignoring it.
How do I find unmanaged devices on my network?
Scan your address ranges with ConnectMyAssets. Managed devices join the inventory; everything else that answers on the network appears in the unmanaged devices list with the reason. Soron can also alert on addresses that answer the scans and belong to no asset at all.
What information is available about a device I cannot log into?
The reason, the SSH banner, the last prompt, the vendor profiles tried, first and last seen, the number of occurrences, the declared subnet, the MAC address and vendor when an ARP table holds them, the open ports with their identified services and TLS certificates, and the results of the toolkit runs.
Why did a device that worked before become unsupported?
Usually because its password changed, its SSH host key changed after a replacement or reinstallation, or a scan rule now restricts its range. The reason shown on the host tells you which one, with the message of the engine.
How do I turn an unmanaged device into a managed asset?
Fix the cause (bind or update a credential in the Vault, adjust the scan rule, free licence credits), then click "Scan this host" on its page. If the host authenticates and its vendor is recognised, it becomes an asset identified by its serial number.
Can I run network diagnostics on an unmanaged device?
Yes. The Tools tab of the host page runs ping, TCP ping, traceroute, port test, certificate, HTTP, DNS, path MTU and SSH negotiation from ConnectMyAssets, without any credential. Scan rules still apply: a blocked address receives nothing.
How long do unmanaged devices stay in the list?
Until the host becomes an asset, or until consecutive scans find it silent (two by default). You can also delete hosts yourself; each deletion is recorded in the audit trail.
