katycomputersystems 1 Posted August 20, 2020 Share Posted August 20, 2020 I migrated to msp.eset.com when I go to the activated_units page, I find many of my endpoints seem to be using two licenses for the same product, it looks like this: Can someone explain what this means? Should I go through and deactivate the duplicates? Is there some automated way to clean this mess? Link to comment Share on other sites More sharing options...
katycomputersystems 1 Posted August 20, 2020 Author Share Posted August 20, 2020 Nearly all "Multiple Devices" represent the same machine with different versions of Endpoint Security. A few are clearly different machines, each with a different computer name, installed at different times etc. Very confusing.... Link to comment Share on other sites More sharing options...
katycomputersystems 1 Posted August 20, 2020 Author Share Posted August 20, 2020 More weirdness 46740 is a multiple, then it isn't: Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted August 21, 2020 ESET Staff Share Posted August 21, 2020 Hi John, I will send it to our engineers for investigation. The entries where you have the same device twice, is a known issue when the old version of Endpoint remains "registered" as activated. However, only one unit of a license is consumed in that case, due to the fact that license consumption is tight to a hardware fingerprint. It´s safe to remove the duplicates. The other issue (different names of the devices) is something that might need to be investigated. You can theoretically "reset" them in a way, that you deactivate all of them, and reactivate them from ESMC, ideally via a dynamic group set to trigger activation task automatically when any product reports it is not activated. (if they are connecting all-right). That might result in correction of the issue. If it reappears, then we will have to investigate it in more detail. Regards, Michal Link to comment Share on other sites More sharing options...
katycomputersystems 1 Posted August 21, 2020 Author Share Posted August 21, 2020 Thanks Michal, I deactivated pc47006, waited until it showed up as a problem in ESMC, then activated it in ESMC, same issue: At this point, I'll ignore the issue and see what if any impact it has on our clients. Link to comment Share on other sites More sharing options...
Recommended Posts