Devices in Automox with the same UUID
There are times when a new device is registered to Automox, but it doesn't appear in the console. Why is this? Nine times out of ten, the device doesn't appear because it is sharing an Automox UUID with another already registered device (see: Automox UUID Generation Guide).
If that's the case, then an identifying variable needs to be changed on the device so that Automox can "see" it as a unique device.
Steps to Resolution
The recommended steps to resolve this are as follows:
- Shut down the amagent service on the devices sharing a UUID
- Deregister the agent on the devices
- Remove/Uninstall the agent on the devices
- Make any necessary changes to separate the devices from each other. Please note these are the variables we use to identify devices:
const HARDWARE_ID_UUID = 'uuid'; // windows
const HARDWARE_ID_MACHINE_ID = 'machine-id'; // non-windows
const PROCESSOR_HASH = 'processor-hash';
const MEMORY_HASH = 'memory-hash';
const BIOS_HASH = 'bios-hash';
const SYSTEM_HASH = 'system-hash';
const HOSTNAME_INFO = "hostname-info";
const IP_ADDRESS_ID = 'ipaddress-info';
const MAC_ADDR_INFO = 'macaddr-info';
const DISK_INFO = 'disk-info';
const MINIMUM_MATCH_PERCENT = 40;For Linux devices, it is most common to change the machine-id of a device in order for it to be seen as a unique device. Similarly, for Windows devices it is the Windows based UUID.
Other common things to change include the hostname, IP address, MAC address, etc. These changes must be made while the device does not have the agent installed. You may need to restart the device as well after the changes have been made then you can move on to Step 5. - Reinstall the agent
The command lines for the above can be found here for your specific OS: Agent Command Line Guide
When the newly installed agent starts on these devices, they should now have unique Automox UUIDs.