Search the Community
Showing results for tags 'cloning'.
I keep getting false positives regarding "Potential computer cloning or hardware change detected" from certain I.T. staff computers (7.2). I'm assuming it's because the calculated hardware fingerprint is changing but without knowing how that's calculated I don't know what's causing it. Is it a safe assumption that all (excluding perhaps Displays and IP addresses?) information on the Details > Hardware section is used to calculate the hardware fingerprint? It should go without saying that the hardware on affected systems isn't changing nor are any systems cloned.
Hi Everyone I'm having a bit of a weird issue. I recently upgraded from Eset Remote Administrator to Eset security management ( btw, love the new interface ). While I was in the spirit of upgrading everything I decided to update my master deployment image with the latest Eset Endpoint security as well as upgrade from Eset agent V6.5 to V7 and distributing it to approximately 50 computers. Now here is where it went sideways. As always, I pushed a "reset cloned agent" task after everything successfully deployed and it's not working as expected. Only the master image resets, none of the others registered. This is only affecting computers that have been cloned. All the other computers in the company is working perfectly. This used to work previously. Is V7 different in this regard? Current Version Installed: Eset Security Management center server 7.0.471.0 (Apliance) Eset Management Agent 7.0.577.0 Eset Endpoint Security V7.1.2045.5 Windows 10 Pro 64Bit Please let me know should additional info be needed.