Hi CNYMetalGuy,
We often see this behavior if the machines have been cloned and the agent doesn’t have enough differentiating information to create a separate object for each device. This results in a single entry being used essentially by each device whenever they scan, resulting in the information of a single object changing (hostnames/IP information/hardware details). Some more detail here if that is the case:
https://help.automox.com/hc/en-us/articles/6212735367060-Linux-Devices-Share-a-UUID
To update, I’ve experienced this issue with a few of my linux servers. And still ongoing. I’ve tried the following:
Uninstall/reinstall amagent
Unregister and reregister
Stop service, delete and reset the UUID, and restart the service
Most of the time these steps fail to resolve the issue. They will not even show up in the devices. I do have several similarly built servers. Same specs but named different. This has only been an issue with my linux boxes (ubuntu and RHEL). Not an issue with any Win servers
Thanks
We experienced the same issue, the root cause was duplicate machine-id for our linux systems (because we use vm templates) and the fix in the article that Mark links to worked to resolve the issue for us