Overview
If a device does not appear in the Automox console, the cause is usually either a failed agent installation or a device identity issue. Automox identifies devices using a generated fingerprint rather than hostname alone, which can sometimes result in devices appearing under an unexpected name or not appearing at all. For further reading: Automox UUID Generation Guide
Common Causes
When the Agent Failed to Install
A device will not appear in the console if the Automox agent did not install successfully. Common reasons include:
The installer failed or was interrupted
The wrong organization or zone installer was used
Network connectivity issues during installation
Proxy or firewall restrictions blocking outbound HTTPS (port 443)
Insufficient permissions to complete installation
In this case, the device will not generate a fingerprint and cannot appear in the console. This would be the first place to check if it has not yet been done so!
When the Agent Installed Successfully but the Device Is Missing
If the agent installed without errors, the device may still be missing due to one or more of the following:
The device has not checked in recently
Network connectivity or proxy restrictions are blocking communication
The device was deleted or archived
The device belongs to a different organization or zone
The device hostname changed after enrollment
The device shares identifying attributes with another system
Checking the Device Fingerprint in amagent.log
Automox generates a device fingerprint during agent startup. This fingerprint can be found in the amagent.log file and is the most reliable way to understand how Automox is identifying the device.
Look in amagent.log for an entry similar to (it will be one line, separated for readability):
time=YYYY-MM-DDTHH:MM:SS.mmmZ level=INFO msg="generated instance fingerprint"
uuid="<automox-generated-uuid>"
memory-hash="<memory-hash>"
system-hash="<system-hash>"
hostname-info=<hostname>
ipaddress-info=<ip-address>
processor-hash="<processor-hash>"
bios-hash="<bios-hash>"
disk-info="<disk-hash>"
macaddr-info=<mac-address>
device_uuid=<device-uuid>This entry includes:
The hostname detected at the time of fingerprint generation
Hardware and system identifiers
An internally generated device identity used by Automox (
device_uuid)
This information helps determine whether the device is being identified as expected or is matching another system. You can use the device_uuid as a searchable key in the Device Explorer to return better results.
Why the Hostname May Look Wrong or “Flip”
Automox does not identify devices by hostname alone. Instead, it generates a fingerprint using multiple hardware and system attributes, such as BIOS, memory, processor, disk, MAC address, IP address, and hostname.
If two devices share 40% or more of these attributes, Automox may not be able to reliably distinguish between them. When this happens, you may see:
A device appearing under another device’s hostname
A hostname reverting to an older value
A newly installed device not appearing as expected
This most commonly occurs after:
Reimaging a device
Reinstalling the agent after a hostname change
Deploying cloned or templated systems
Devices sharing a machine ID (especially on Linux)
If Two Devices Share the Same Automox Identity
If multiple devices resolve to the same Automox identity, Automox treats them as a single device. To resolve this, one or more identifying attributes must change so the devices can be uniquely fingerprinted.
This often involves allowing the agent time to rescan after a rename or reinstall, or making a change that causes the device to generate a new fingerprint. See Automox UUID Generation Guide for more information (linked previously).
When to Contact Support
Contact Automox Support if:
The agent installs successfully but no fingerprint appears in
amagent.logThe fingerprint appears to belong to another device
Devices continue to merge or overwrite each other after identity changes
Providing the relevant amagent.log entries will help Support investigate more quickly.